# Hypernym - Generic class for broader/parent concepts in hierarchies
# Created per slot_fixes.yaml migration for: collection_broader_type
# Creation date: 2026-01-19
#
# Rule compliance:
# - Rule 0b: Type/Types naming - Hypernym is the base type class
# - Rule 38: Slot centralization with semantic URIs
# - Rule 39: RiC-O temporal naming conventions
# - Rule 53: Generic reusable slots

id: https://nde.nl/ontology/hc/classes/Hypernym
name: Hypernym
title: Hypernym

prefixes:
  linkml: https://w3id.org/linkml/
  hc: https://nde.nl/ontology/hc/
  skos: http://www.w3.org/2004/02/skos/core#
  rdfs: http://www.w3.org/2000/01/rdf-schema#
  owl: http://www.w3.org/2002/07/owl#

imports:
  - linkml:types
  - ../slots/has_or_had_identifier
  - ../slots/has_or_had_label
  - ../slots/has_or_had_description

default_range: string
default_prefix: hc

classes:
  Hypernym:
    description: >-
      A broader/parent concept in a classification hierarchy.
      
      **SEMANTIC DEFINITION**:
      A hypernym (also superordinate or umbrella term) is a concept whose 
      semantic field is more inclusive than that of another concept. 
      For example, "vehicle" is a hypernym of "car", "truck", and "bicycle".
      
      **SKOS ALIGNMENT**:
      In SKOS vocabulary, hypernym relationships are expressed via:
      - `skos:broader` - links a concept to its hypernym
      - `skos:narrower` - inverse, links hypernym to hyponyms
      - `skos:broaderTransitive` - transitive closure of broader
      
      **HERITAGE DOMAIN USAGE**:
      - Collection types: "Archives" is hypernym of "Municipal Archives"
      - Institution types: "Museum" is hypernym of "Art Museum"
      - Subject classification: "Art" is hypernym of "Painting"
      
      **RELATED CONCEPTS**:
      - **Hyponym**: The inverse - a more specific concept (child)
      - **Meronym**: Part-of relationship (different from is-a)
      - **Holonym**: Whole-of relationship (inverse of meronym)
      
      **ONTOLOGY MAPPING**:
      - class_uri: skos:Concept (as hypernym IS a concept)
      - exact_mappings: skos:broader target concept
      
    class_uri: skos:Concept
    
    exact_mappings:
      - skos:Concept
    
    close_mappings:
      - rdfs:Class
      - owl:Class
    
    slots:
      - has_or_had_identifier
      - has_or_had_label
      - has_or_had_description
    
    attributes:
      hypernym_uri:
        range: uriorcurie
        description: >-
          URI reference to the broader/parent concept.
          This is the primary identifier for the hypernym in linked data.
        examples:
          - value: "hc:collection-type/archives"
            description: URI for Archives as hypernym
          - value: "rico:Fonds"
            description: RiC-O Fonds as hypernym
      
      hypernym_scheme:
        range: string
        description: >-
          The vocabulary or ontology scheme this hypernym belongs to.
        examples:
          - value: "SKOS"
          - value: "RiC-O"
          - value: "CIDOC-CRM"
    
    annotations:
      custodian_types: '["*"]'
      custodian_types_rationale: >-
        Hypernym relationships apply to all classification hierarchies
        across all custodian types.
      custodian_types_primary: "*"
      specificity_score: 0.25
      specificity_rationale: >-
        Low specificity - fundamental concept for any hierarchical classification.
    
    examples:
      - value: |
          Hypernym:
            hypernym_uri: "rico:Fonds"
            has_or_had_label:
              - label_text: "Fonds"
                label_language: "en"
            has_or_had_description:
              - description_text: "Provenance-based archival unit"
        description: RiC-O Fonds as hypernym for archival record sets.
      
      - value: |
          Hypernym:
            hypernym_uri: "hc:collection-type/museum-collection"
            has_or_had_label:
              - label_text: "Museum Collection"
            has_or_had_description:
              - description_text: "Physical heritage objects held by museums"
        description: Museum Collection as hypernym for specific collection types.
    
    comments:
      - Created from slot_fixes.yaml migration (2026-01-19)
      - Replaces collection_broader_type slot range with structured class
      - SKOS-aligned for vocabulary interoperability
      - Use with has_or_had_hypernym slot