glam/frontend/public/schemas/20251121/linkml/modules/classes/ProfileData.yaml
kempersc ec113e8811 Add new classes and slots for archival and educational metadata
- Introduced EADIdentifier, EBook, EcclesiasticalProvince, Edition, Editor, Education, EmailAddress, and Size classes to enhance archival description capabilities.
- Added slots for digital presence types, digital surrogates, digitization status, and dimensions to support comprehensive metadata management.
- Migrated existing slots such as ead_id, edition_number, and dimension to new structured formats.
- Established relationships between works and their editions, sizes, and editors to improve data interconnectivity.
- Enhanced ontology alignment with Schema.org and BIBFRAME standards for better interoperability.
2026-01-26 09:00:29 +01:00

113 lines
3.7 KiB
YAML

# ProfileData - Core profile information for a person
# Extracted from custodian_source.yaml per Rule 38 (modular schema files)
# Extraction date: 2026-01-08
id: https://nde.nl/ontology/hc/classes/ProfileData
name: ProfileData
title: ProfileData
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
prov: http://www.w3.org/ns/prov#
xsd: http://www.w3.org/2001/XMLSchema#
pico: https://w3id.org/pico/
foaf: http://xmlns.com/foaf/0.1/
imports:
- linkml:types
- ./CareerEntry
- ./CertificationEntry
- ./CurrentPosition
- ./Education
- ./HeritageExperienceEntry
- ./MediaAppearanceEntry
- ./PublicationEntry
default_range: string
classes:
ProfileData:
description: >-
Core profile information for a person, containing extracted biographical data
such as name, career history, education, skills, and professional summary.
This represents observed/extracted data ABOUT a person from a source document
(e.g., LinkedIn profile), not the person entity itself.
Ontology mapping rationale:
- class_uri is pico:PersonObservation because this represents observed biographical
data extracted from a source, following the PiCo pattern of separating observations
from person reconstructions
- close_mappings includes foaf:PersonalProfileDocument as this is essentially
profile document content (though not RDF-specific)
- related_mappings includes schema:Person because the data describes a person,
and prov:Entity because the profile data participates in provenance chains
class_uri: pico:PersonObservation
close_mappings:
- foaf:PersonalProfileDocument
related_mappings:
- schema:Person
- prov:Entity
attributes:
full_name:
range: string
description: Person's full name
headline:
range: string
description: Professional headline/title
location:
range: string
description: Location
about:
range: string
description: Professional summary
current_position:
range: CurrentPosition
description: Current job position
skill:
range: string
multivalued: true
inlined_as_list: true
description: Professional skills
has_or_had_language:
range: string
multivalued: true
inlined_as_list: true
description: Languages known
specifies_or_specified:
range: Education
multivalued: true
inlined_as_list: true
description: >-
Educational background.
MIGRATED from education per Rule 53 (2026-01-25).
certifications:
range: CertificationEntry
multivalued: true
inlined_as_list: true
description: Professional certifications
career_history:
range: CareerEntry
multivalued: true
inlined_as_list: true
description: Complete career history
heritage_relevant_experience:
range: HeritageExperienceEntry
multivalued: true
inlined_as_list: true
description: Heritage sector experience
publications:
range: PublicationEntry
multivalued: true
inlined_as_list: true
description: Academic/professional publications
media_appearances:
range: MediaAppearanceEntry
multivalued: true
inlined_as_list: true
description: Media appearances
professional_summary:
range: string
description: Professional summary