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

64 lines
1.5 KiB
YAML

id: https://nde.nl/ontology/hc/class/Restriction
name: Restriction
title: Restriction
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
dct: http://purl.org/dc/terms/
crm: http://www.cidoc-crm.org/cidoc-crm/
default_prefix: hc
imports:
- linkml:types
- ../slots/restriction_reason
- ../slots/restriction_type
- ../slots/temporal_extent
classes:
Restriction:
class_uri: dct:RightsStatement
description: 'An access or use restriction on a resource.
**USAGE**:
Used for:
- Embargo periods (years restricted) with temporal extent
- Access restrictions
- Use limitations
**TEMPORAL MODELING**:
The temporal_extent slot uses TimeSpan (CIDOC-CRM E52) to model
when the restriction applies, with fuzzy boundary support:
- begin_of_the_begin: Earliest start of restriction
- end_of_the_end: Latest end of restriction period
'
slots:
- temporal_extent
- restriction_type
- restriction_reason
slot_usage:
temporal_extent:
range: TimeSpan
exact_mappings:
- dct:RightsStatement
annotations:
specificity_score: '0.45'
specificity_rationale: Moderately specific - restrictions are common in heritage
domain.
custodian_types: '[''*'']'
examples:
- value:
restriction_type: EMBARGO
restriction_reason: Privacy protection
temporal_extent:
begin_of_the_begin: '2025-01-01T00:00:00Z'
end_of_the_end: '2050-01-01T00:00:00Z'