fc405445c6
- 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`.
90 lines
No EOL
2.7 KiB
YAML
90 lines
No EOL
2.7 KiB
YAML
id: https://nde.nl/ontology/hc/class/DatePrecision
|
|
name: date_precision_class
|
|
title: DatePrecision Class
|
|
description: >-
|
|
Represents the precision level of a date value.
|
|
|
|
Used to indicate how specific date information is, from full day
|
|
precision to century-level approximations.
|
|
|
|
prefixes:
|
|
linkml: https://w3id.org/linkml/
|
|
hc: https://nde.nl/ontology/hc/
|
|
crm: http://www.cidoc-crm.org/cidoc-crm/
|
|
time: http://www.w3.org/2006/time#
|
|
|
|
imports:
|
|
- linkml:types
|
|
- ../slots/has_or_had_code
|
|
- ../slots/has_or_had_description
|
|
- ../slots/has_or_had_label
|
|
default_prefix: hc
|
|
|
|
classes:
|
|
DatePrecision:
|
|
class_uri: hc:DatePrecision
|
|
description: >-
|
|
Date precision level classification.
|
|
|
|
**Standard Precision Levels**:
|
|
|
|
| Level | Short Code | Format | Example |
|
|
|-------|------------|--------|---------|
|
|
| Day | DAY | YYYY-MM-DD | 2005-04-30 |
|
|
| Month | MONTH | YYYY-MM | 2005-04 |
|
|
| Year | YEAR | YYYY | 2005 |
|
|
| Decade | DECADE | YYYY0s | 2000s |
|
|
| Century | CENTURY | YYth century | 21st century |
|
|
| Unknown | UNKNOWN | - | Date mentioned but precision unclear |
|
|
|
|
**CIDOC-CRM Alignment**: Related to time dimension concepts in CRM.
|
|
|
|
**OWL Time Alignment**: Related to time:TemporalUnit for precision levels.
|
|
close_mappings:
|
|
- time:TemporalUnit
|
|
- crm:E52_Time-Span
|
|
slots:
|
|
- has_or_had_label
|
|
- has_or_had_code
|
|
- has_or_had_description
|
|
slot_usage:
|
|
has_or_had_label:
|
|
range: string
|
|
required: true
|
|
examples:
|
|
- value: "Day"
|
|
- value: "Year"
|
|
has_or_had_code:
|
|
range: string
|
|
required: true
|
|
pattern: "^[A-Z]+$"
|
|
examples:
|
|
- value: "DAY"
|
|
- value: "YEAR"
|
|
- value: "UNKNOWN"
|
|
has_or_had_description:
|
|
range: string
|
|
required: false
|
|
examples:
|
|
- value: "Full date with day precision (YYYY-MM-DD format)"
|
|
annotations:
|
|
specificity_score: 0.40
|
|
specificity_rationale: >-
|
|
Date precision is moderately specific - used primarily in
|
|
temporal data contexts.
|
|
custodian_types: '["*"]'
|
|
custodian_types_rationale: >-
|
|
Date precision applies universally to all custodian types.
|
|
examples:
|
|
- value:
|
|
has_or_had_label: "Day"
|
|
has_or_had_code: "DAY"
|
|
has_or_had_description: "Full date with day precision (YYYY-MM-DD)"
|
|
- value:
|
|
has_or_had_label: "Year"
|
|
has_or_had_code: "YEAR"
|
|
has_or_had_description: "Year-only precision (YYYY format)"
|
|
- value:
|
|
has_or_had_label: "Unknown"
|
|
has_or_had_code: "UNKNOWN"
|
|
has_or_had_description: "Date mentioned but precision cannot be determined" |