glam/schemas/20251121/linkml/modules/classes/LanguageProficiency.yaml
kempersc 4319f38c05 Add archived slots for audience size, audience type, and capacity metrics
- Created new YAML files for audience size and audience type slots, defining their properties and annotations.
- Added archived capacity slots including cubic meters, linear meters, item count, and descriptions, with appropriate URIs and ranges.
- Introduced a template specificity slot for context-aware RAG filtering.
- Consolidated capacity-related slots into a unified structure, including has_or_had_capacity, capacity_type, and capacity_value, with detailed descriptions and examples.
2026-01-17 18:53:23 +01:00

96 lines
3.5 KiB
YAML

id: https://nde.nl/ontology/hc/class/LanguageProficiency
name: language_proficiency_class
title: Language Proficiency Class
version: 1.0.0
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
dct: http://purl.org/dc/terms/
imports:
- linkml:types
- ../metadata
- ../slots/specificity_annotation
- ../slots/has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
- ../slots/language_raw
- ../slots/language_name
- ../slots/language_code
- ../slots/proficiency_level
- ../enums/LanguageProficiencyEnum
- ./SpecificityAnnotation
- ./TemplateSpecificityScore # was: TemplateSpecificityScores - migrated per Rule 53 (2026-01-17)
- ./TemplateSpecificityType
- ./TemplateSpecificityTypes
- ../slots/language_code
- ../slots/language_name
- ../slots/language_raw
- ../slots/proficiency_level
- ../slots/specificity_annotation
- ../slots/has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
- ../slots/language_code
- ../slots/language_name
- ../slots/language_raw
- ../slots/proficiency_level
- ../slots/specificity_annotation
- ../slots/has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
default_range: string
default_prefix: hc
classes:
LanguageProficiency:
class_uri: schema:knowsLanguage
description: "A language skill with proficiency level.\n\nModels language abilities as extracted from LinkedIn profiles,\n\
with both raw string and parsed components.\n\n**Schema.org Alignment**:\n- Represents schema:knowsLanguage relation\n\
- Language is schema:Language\n\n**Use Cases**:\n- LinkedIn profile language sections\n- Multilingual staff identification\n\
- Heritage institution language capabilities\n\n**Example JSON Values**:\n```json\n[\n \"English - Native or bilingual\"\
,\n \"Dutch - Native or bilingual\",\n \"French - Professional working proficiency\"\n]\n```\n\n**LinkedIn Proficiency\
\ Levels**:\n- Native or bilingual proficiency\n- Full professional proficiency \n- Professional working proficiency\n\
- Limited working proficiency\n- Elementary proficiency\n"
exact_mappings:
- schema:knowsLanguage
close_mappings:
- dct:language
slots:
- language_code
- language_name
- language_raw
- proficiency_level
- specificity_annotation
- has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
slot_usage:
language_raw:
range: string
examples:
- value: English - Native or bilingual
description: Native English speaker
- value: Dutch - Professional working proficiency
description: Professional Dutch
language_name:
range: string
examples:
- value: English
- value: Dutch
- value: French
language_code:
range: string
pattern: ^[a-z]{2}$
examples:
- value: en
description: English
- value: nl
description: Dutch
- value: fr
description: French
proficiency_level:
range: LanguageProficiencyEnum
examples:
- value: NATIVE_BILINGUAL
description: Native or bilingual proficiency
comments:
- Inlined in LinkedInProfile.languages[] as multivalued list
- Preserves raw LinkedIn format for provenance
- ISO 639-1 codes enable language-based filtering
see_also:
- https://schema.org/knowsLanguage
- https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes