3da90b940e
All checks were successful
Deploy Frontend / build-and-deploy (push) Successful in 2m4s
Session 2026-01-19: Completed remaining migrations per Rules 53/56/60. Major migrations: 1. claim_type → has_or_had_type + ClaimType/ClaimTypes (60+ concrete types in 11 categories) 2. circumstances_of_death → is_deceased + DeceasedStatus + CauseOfDeath 3. claims_count → has_or_had_quantity + Quantity (with based_on_claim for provenance) 4. classification_status → has_or_had_type + ClassificationStatusType Created files: - ClaimType.yaml, ClaimTypes.yaml (abstract base + 60+ concrete subclasses) - DeceasedStatus.yaml, CauseOfDeath.yaml, CauseOfDeathTypeEnum.yaml - ClassificationStatus.yaml, ClassificationStatusType.yaml, ClassificationStatusTypes.yaml - CITESAppendix.yaml, City.yaml, CertaintyLevel.yaml - is_deceased.yaml, is_or_was_caused_by.yaml, based_on_claim.yaml Archived slots: - claim_type, circumstances_of_death, claims_count, classification_status Added Rule 60 to AGENTS.md: No Migration Deferral - agents MUST execute all migrations. All 527 slot_fixes.yaml entries now complete (100%).
130 lines
4.3 KiB
YAML
130 lines
4.3 KiB
YAML
# 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
|