glam/schemas/20251121/linkml/modules/classes/Component.yaml
kempersc fc405445c6 Refactor and update schema definitions
- Removed obsolete slots: `has_or_had_custodian_observation`, `provider`, and `specificity_annotation`.
- Updated `has_or_had_score` slot to use `SpecificityScore` class and modified its description and examples.
- Added new slots: `end_seconds`, `end_time`, `has_archive_path`, `has_or_had_custodian_name`, `protocol_name`, and `protocol_version`.
- Introduced a script `check_annotation_types.py` to validate the presence and structure of `custodian_types` in YAML files.
- Added a script `update_specificity.py` to automate updates related to `SpecificityAnnotation` to `SpecificityScore`.
2026-02-01 19:55:38 +01:00

101 lines
No EOL
2.7 KiB
YAML

id: https://nde.nl/ontology/hc/class/Component
name: component_class
title: Component Class
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
dcterms: http://purl.org/dc/terms/
imports:
- linkml:types
- ../metadata
- ../slots/has_or_had_description
- ../slots/has_or_had_label
- ../slots/has_or_had_type
default_prefix: hc
classes:
Component:
class_uri: schema:ItemList
description: |
A component or part of a larger entity.
**MIGRATION NOTE** (2026-01-22):
Created per slot_fixes.yaml migration from `component_type` string
to structured Component class per Rule 53.
**Purpose**:
Provides base class for components/parts including:
- Type classification via ComponentType hierarchy
- Value/label for the component
- Additional metadata
**Ontological Alignment**:
- **Primary** (`class_uri`): `schema:ItemList` - Schema.org (component as list item)
- **Close**: `dcterms:hasPart` - Dublin Core part relationship
**Use Cases**:
- Address components (street, city, country)
- System components
- Document components
**Pattern**:
```yaml
has_or_had_component:
- has_or_had_type: StreetNumber
has_or_had_label: "1"
long_name: "1"
short_name: "1"
```
slots:
- has_or_had_type
- has_or_had_label
- has_or_had_description
slot_usage:
has_or_had_type:
range: ComponentType
multivalued: true
required: false
examples:
- value: StreetNumber
- value: Route
- value: Locality
has_or_had_label:
range: string
required: false
examples:
- value: "1"
- value: "Museumstraat"
exact_mappings:
- schema:ItemList
close_mappings:
- dcterms:hasPart
annotations:
custodian_types: '["*"]'
custodian_types_rationale: Components applicable across all heritage domains.
custodian_types_primary: M
specificity_score: 0.30
specificity_rationale: >-
Broadly applicable - component modeling fundamental to many domains.
# migration_info: (Flattened)
migration_source_slot: component_type
migration_date: "2026-01-22"
migration_rule: "Rule 53"
comments:
- "Base class for component/part entities"
- "Type classification via ComponentType hierarchy"
- "Created 2026-01-22 from component_type migration (Rule 53)"
examples:
- value:
has_or_had_type: StreetNumber
has_or_had_label: "1"
- value:
has_or_had_type: Locality
has_or_had_label: "Amsterdam"