glam/schemas/20251121/linkml/modules/classes/TimeSpan.yaml
kempersc 2a75ddf7cc feat: Add ConflictType and ConflictTypes schemas for heritage conflict taxonomy
- Introduced abstract class ConflictType to define a taxonomy for various conflict types affecting heritage institutions.
- Added concrete subclasses in ConflictTypes.yaml, detailing specific conflict types such as ArmedConflict, NaturalDisaster, CivilUnrest, Terrorism, Looting, Neglect, Occupation, and Sanctions.
- Implemented Permission and PermissionType schemas to represent authorization requirements for accessing heritage materials, including subclasses like BishopsPermission and InstitutionalAffiliation.
- Created SocialNetworkMember class for representing members in social/professional networks, facilitating heritage sector network analysis.
- Established slots for canonical access rules, conflict status, and connection metadata, enhancing the data model for heritage custodians.
- Developed ConnectionDegree and ConnectionDegreeType classes to represent degrees of connection in social networks, with subclasses for first, second, and third-plus degrees.
- Added slots for birth dates in EDTF and ISO formats, improving the representation of heritage custodian entities.
2026-01-22 20:41:06 +01:00

119 lines
3.9 KiB
YAML

id: https://nde.nl/ontology/hc/class/TimeSpan
name: timespan_class
title: TimeSpan Class
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
crm: http://www.cidoc-crm.org/cidoc-crm/
time: http://www.w3.org/2006/time#
xsd: http://www.w3.org/2001/XMLSchema#
imports:
- linkml:types
- ../slots/begin_of_the_begin
- ../slots/begin_of_the_end
- ../slots/end_of_the_begin
- ../slots/end_of_the_end
- ../slots/specificity_annotation
- ../slots/has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
- ./SpecificityAnnotation
- ./TemplateSpecificityScore # was: TemplateSpecificityScores - migrated per Rule 53 (2026-01-17)
- ./TemplateSpecificityType
- ./TemplateSpecificityTypes
- ./Timestamp
# ADDED 2026-01-22: has_or_had_notation for EDTF string preservation per slot_fixes.yaml feedback
- ../slots/has_or_had_notation
default_range: string
classes:
TimeSpan:
class_uri: crm:E52_Time-Span
description: 'Represents temporal extent with fuzzy boundaries following CIDOC-CRM pattern.
E52_Time-Span models uncertainty in temporal bounds through four properties:
- P82a (begin_of_the_begin): Earliest possible start time
- P81a (end_of_the_begin): Latest possible start time
- P81b (begin_of_the_end): Earliest possible end time
- P82b (end_of_the_end): Latest possible end time
**Example**: "Founded sometime between 1800-1805, closed between 1950-1955"
- begin_of_the_begin: 1800-01-01 (earliest founding)
- end_of_the_begin: 1805-12-31 (latest founding)
- begin_of_the_end: 1950-01-01 (earliest closure)
- end_of_the_end: 1955-12-31 (latest closure)
**Use Cases**:
- Custodian founding/dissolution dates with uncertainty
- Historical event temporal bounds
- Archival record date ranges
**DO NOT USE FOR**: Database record metadata (use schema:dateCreated/dateModified)
'
exact_mappings:
- crm:E52_Time-Span
close_mappings:
- schema:DateTime
- time:Interval
related_mappings:
- prov:InstantaneousEvent
slots:
- begin_of_the_begin
- begin_of_the_end
- end_of_the_begin
- end_of_the_end
- specificity_annotation
- has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
# ADDED 2026-01-22: Preserves original EDTF notation (e.g., "197X", "1970~")
- has_or_had_notation
slot_usage:
has_or_had_notation:
range: string
required: false
description: >-
Original EDTF (Extended Date/Time Format) notation string.
Preserves the exact notation used to express temporal uncertainty.
**EDTF PATTERNS**:
| Pattern | Meaning | Example |
|---------|---------|---------|
| `YYYY-MM-DD` | Full date | `1970-08-15` |
| `YYYY-MM` | Year-month | `1970-08` |
| `YYYY` | Year only | `1970` |
| `YYYX` | Decade | `197X` (1970s) |
| `YYYY~` | Approximate | `1970~` (circa) |
| `YYYY?` | Uncertain | `1970?` |
| `XXXX` | Unknown | Requires provenance |
examples:
- value: "1970-08-15"
description: Full date known
- value: "197X"
description: Decade known (1970s)
- value: "1970~"
description: Approximate (circa 1970)
attributes:
notes:
range: string
description: Additional notes or remarks about the time span
comments:
- Handles temporal uncertainty common in heritage contexts
- 'Precise dates: Set begin_of_the_begin == end_of_the_begin (and same for end)'
- 'Unknown start: Set begin_of_the_begin to earliest plausible date'
- 'Unknown end: Leave end_of_the_end as null (ongoing/present)'
see_also:
- https://cidoc-crm.org/html/cidoc_crm_v7.1.3.html#E52
- https://www.w3.org/TR/owl-time/