glam/schemas/20251121/linkml/modules/classes/Content.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

111 lines
No EOL
4 KiB
YAML

id: https://nde.nl/ontology/hc/class/Content
name: Content
title: Content Class
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
dcterms: http://purl.org/dc/terms/
crm: http://www.cidoc-crm.org/cidoc-crm/
rico: https://www.ica.org/standards/RiC/ontology#
skos: http://www.w3.org/2004/02/skos/core#
default_prefix: hc
imports:
- linkml:types
- ../metadata
- ../slots/has_or_had_description
- ../slots/has_or_had_label
- ../slots/has_or_had_type
- ../slots/temporal_extent
classes:
Content:
class_uri: rico:RecordSetType
description: |
The intellectual content described by or contained in heritage materials.
**Purpose**:
Captures what a collection, document, archive, or other heritage material is ABOUT,
including its temporal coverage, spatial coverage, and subject matter.
**Ontological Alignment**:
- **RiC-O**: `rico:RecordSetType` for archival content characterization
- **Dublin Core**: Maps to `dcterms:coverage` (temporal/spatial/topical)
- **CIDOC-CRM**: Relates to `E73_Information_Object` conceptual content
**Key Slots**:
| Slot | Purpose |
|------|---------|
| `temporal_extent` | Time period the content covers (via TimeSpan) |
| `has_or_had_label` | Content label/title |
| `has_or_had_description` | Detailed description of content |
**Distinction from temporal_extent**:
- `temporal_extent` on Content = what time period the CONTENT covers
- `temporal_extent` on Activity = how long the activity lasted
**Example**:
A collection of VOC trade records might have Content with:
- temporal_extent: 1602-1799 (the period covered by the records)
- has_or_had_label: "Dutch East India Company Trade Records"
- has_or_had_description: "Shipping manifests, correspondence, and financial records..."
**Migrated From**: temporal_coverage slot (2026-01-16) per Rule 53/56
**Updated 2026-01-23**: Added has_or_had_type for ContentType per F25 migration
slots:
- has_or_had_label
- has_or_had_description
- has_or_had_type
- temporal_extent
slot_usage:
has_or_had_type:
range: ContentType
required: false
examples:
- value:
has_or_had_code: RELIGIOUS
has_or_had_label: Religious Content
- value:
has_or_had_code: CARTOGRAPHIC
has_or_had_label: Cartographic Content
has_or_had_label:
examples:
- value: "Dutch Colonial Period Records"
- value: "Medieval Manuscript Collection"
has_or_had_description:
examples:
- value: "Administrative records, correspondence, and financial documents from the Dutch colonial administration in the East Indies."
temporal_extent:
range: TimeSpan
inlined: true
examples:
- value:
begin_of_the_begin: "1602-01-01"
end_of_the_end: "1799-12-31"
- value:
begin_of_the_begin: "1200-01-01"
end_of_the_end: "1500-12-31"
close_mappings:
- dcterms:coverage
- schema:about
annotations:
custodian_types: '["*"]'
custodian_types_rationale: Content characterization applicable to all heritage custodian types
specificity_score: 0.25
specificity_rationale: Broadly useful class for describing what heritage materials are about
examples:
- value:
has_or_had_label: "Dutch East India Company Records"
has_or_had_description: "Trade records, shipping manifests, and correspondence from VOC operations"
temporal_extent:
begin_of_the_begin: "1602-03-20"
end_of_the_end: "1799-12-31"
- value:
has_or_had_label: "Medieval Illuminated Manuscripts"
temporal_extent:
begin_of_the_begin: "0800-01-01"
end_of_the_end: "1450-12-31"