glam/schemas/20251121/linkml/modules/classes/CustodianTimelineEvent.yaml
kempersc 626bd3a095 refactor(schemas): apply naming conventions to 261 class files
- Apply Rule 39: RiC-O style hasOrHad*/isOrWas* for temporal slots
- Apply Rule 43: Singular noun convention (keywords → keyword)
- Update slot references to match renamed slot files
- Maintain schema integrity across all class definitions
2026-01-10 15:36:33 +01:00

272 lines
10 KiB
YAML

id: https://nde.nl/ontology/hc/class/CustodianTimelineEvent
name: CustodianTimelineEvent
title: Custodian Timeline Event Class - Organizational Change Events
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
dcterms: http://purl.org/dc/terms/
prov: http://www.w3.org/ns/prov#
xsd: http://www.w3.org/2001/XMLSchema#
crm: http://www.cidoc-crm.org/cidoc-crm/
tooi: https://identifier.overheid.nl/tooi/def/ont/
imports:
- linkml:types
- ./SpecificityAnnotation
- ./TemplateSpecificityScores
- ../enums/OrganizationalChangeEventTypeEnum
- ../enums/DataTierEnum
- ../enums/DatePrecisionEnum
- ../enums/TimelineExtractionMethodEnum
- ../slots/approximate
- ../slots/has_archive_path
- ../slots/data_tier
- ../slots/date_precision
- ../slots/description
- ../slots/event_date
- ../slots/event_type
- ../slots/extraction_method
- ../slots/extraction_note
- ../slots/extraction_timestamp
- ../slots/observation_ref
- ../slots/source_url
- ../slots/specificity_annotation
- ../slots/template_specificity
default_prefix: hc
classes:
CustodianTimelineEvent:
class_uri: prov:Entity
description: |
An organizational change event for a heritage custodian.
**PURPOSE**
Captures organizational change events (founding, mergers, name changes, etc.)
as domain entities, independent of how they were discovered.
**SOURCE-AGNOSTIC DESIGN**
This class models WHAT happened, not HOW we know. For source-specific
provenance, use observation classes:
- `WebObservation` - For web-scraped data with XPath or API provenance
- `CustodianObservation` - For institutional source documents
The optional `observation_ref` slot links events to their source observations
when detailed provenance is needed.
**DATA QUALITY**
Use `data_tier` to indicate trustworthiness:
- TIER_4_INFERRED: Initial extraction (LLM-generated, unverified)
- TIER_3_CROWD_SOURCED: Verified against Wikipedia/Wikidata
- TIER_2_VERIFIED: Verified against institutional website
- TIER_1_AUTHORITATIVE: Verified against official registry
Use `extraction_notes` to capture source-specific details:
- API queries and responses
- XPath locations in archived HTML
- Wikidata property references
- Manual research notes
**EVENT TYPE MAPPING**
Events are classified using OrganizationalChangeEventTypeEnum:
- FOUNDING: Institution creation (opgericht, gesticht)
- MERGER: Multiple institutions combining (fusie, samenvoeging)
- DISSOLUTION: Institution closure (opgeheven, gesloten)
- RENAMING: Name change only (hernoemd, naamswijziging)
- TRANSFER: Physical relocation (verhuisd, verplaatst)
- EXPANSION: Absorbing other units (uitgebreid, geabsorbeerd)
- SPLIT: Division into multiple units (opgesplitst)
- SPIN_OFF: Parts becoming independent (afgesplitst)
- REDUCTION: Scope decrease (ingekrompen)
- REORGANIZATION: Complex restructuring (herstructurering)
**EXCLUDED EVENT TYPES**
Some patterns are NOT mapped to events:
- predecessor: This is a relationship, not an event
- friends_org: Separate organization (Vrienden van...)
- reopening: Not in OrganizationalChangeEventTypeEnum
**EXAMPLE USAGE**
```yaml
timeline_events:
- event_type: FOUNDING
event_date: "2005-04-30"
date_precision: day
approximate: false
description: >-
Het RHC Drents Archief werd opgericht op 30 april 2005.
Het is de voortzetting van het Rijksarchief in Drenthe (sinds 2000).
source_url:
- "https://nl.wikipedia.org/wiki/Drents_Archief"
- "https://bizzy.ai/nl/nl/52454037/regionaal-historisch-centrum-rhc-drents-archief"
extraction_method: api_response_regex
extraction_timestamp: "2025-12-16T10:00:00Z"
extraction_notes: >-
Query: "Regionaal Historisch Centrum (RHC) Drents Archief" Assen opgericht
Answer archived at: web/0002/linkup/linkup_founding_20251215T160438Z.json
archive_path: web/0002/linkup/linkup_founding_20251215T160438Z.json
data_tier: TIER_4_INFERRED
```
exact_mappings:
- prov:Entity
close_mappings:
- crm:E5_Event
- tooi:Wijzigingsgebeurtenis
- schema:Event
slots:
- approximate
- archive_path
- data_tier
- date_precision
- description
- event_date
- event_type
- extraction_method
- extraction_note
- extraction_timestamp
- observation_ref
- source_url
- specificity_annotation
- template_specificity
slot_usage:
event_type:
required: true
description: |
Type of organizational change event.
Must be a valid OrganizationalChangeEventTypeEnum value.
event_date:
required: false
description: |
Date of the event. Optional because some events may not have
a determinable date from the source.
date_precision:
required: true
description: |
Always required to indicate how to interpret event_date.
Use 'unknown' if date is mentioned but precision unclear.
is_approximate:
required: true
description: |
Always required. Default to false unless hedging language detected.
description:
required: true
description: |
Human-readable summary of the event.
Should describe what happened, not how it was discovered.
source_url:
required: false
description: |
URLs documenting the event. May be empty if no web sources available.
extraction_method:
required: true
range: TimelineExtractionMethodEnum
description: |
How the event was extracted. Required for transparency.
extraction_timestamp:
required: true
description: |
When extraction occurred. Required for temporal provenance.
extraction_note:
required: false
description: |
Optional notes for source-specific details (API queries, XPaths, etc.)
has_archive_path:
required: false
description: |
Path to archived source material. Recommended for audit trail.
data_tier:
required: true
description: |
Quality tier. Use TIER_4_INFERRED for unverified extractions.
observation_ref:
required: false
description: |
Optional link to source observation for detailed provenance.
specificity_annotation:
range: SpecificityAnnotation
inlined: true
template_specificity:
range: TemplateSpecificityScores
inlined: true
rules:
- preconditions:
slot_conditions:
event_date:
value_presence: PRESENT
postconditions:
slot_conditions:
date_precision:
value_presence: PRESENT
description: If event_date is provided, date_precision must be specified
comments:
- "Source-agnostic design - see Rule 37: Provenance Separation"
- Use observation_ref to link to detailed source provenance
- Use extraction_notes for source-specific details (API queries, XPaths)
- Event types constrained to OrganizationalChangeEventTypeEnum
- Use CIDOC-CRM TimeSpan for fuzzy dates if needed
see_also:
- schemas/20251121/linkml/modules/enums/OrganizationalChangeEventTypeEnum.yaml
- schemas/20251121/linkml/modules/classes/WebObservation.yaml
- schemas/20251121/linkml/modules/classes/CustodianObservation.yaml
- schemas/20251121/linkml/modules/classes/TimeSpan.yaml
- .opencode/PROVENANCE_SEPARATION_RULE.md
examples:
- value:
event_type: FOUNDING
event_date: "2005-04-30"
date_precision: day
approximate: false
description: Het RHC Drents Archief werd opgericht op 30 april 2005.
source_url:
- https://nl.wikipedia.org/wiki/Drents_Archief
extraction_method: api_response_regex
extraction_timestamp: "2025-12-16T10:00:00Z"
extraction_notes: "Query: \"Drents Archief\" Assen opgericht OR gesticht API: Linkup. Archived at: web/0002/linkup/linkup_founding_20251215T160438Z.json"
archive_path: web/0002/linkup/linkup_founding_20251215T160438Z.json
data_tier: TIER_4_INFERRED
description: Founding event extracted from API response
- value:
event_type: MERGER
event_date: "2005"
date_precision: year
approximate: false
description: In 2005 ging het Gemeentearchief Assen op in het Drents Archief.
source_url:
- https://nl.wikipedia.org/wiki/Drents_Archief
extraction_method: api_response_regex
extraction_timestamp: "2025-12-16T10:05:00Z"
data_tier: TIER_4_INFERRED
description: Merger event with year-only precision
- value:
event_type: FOUNDING
event_date: "1810"
date_precision: year
approximate: false
description: The Rijksmuseum was founded in 1810 as the Royal Museum.
source_url:
- https://www.wikidata.org/wiki/Q190804
extraction_method: wikidata_sparql
extraction_timestamp: "2025-12-20T14:30:00Z"
extraction_notes: Wikidata P571 (inception date) query
data_tier: TIER_3_CROWD_SOURCED
description: Founding event from Wikidata
- value:
event_type: TRANSFER
event_date: "1885"
date_precision: year
approximate: false
description: The Rijksmuseum moved to its current building designed by Cuypers.
source_url:
- https://www.rijksmuseum.nl/en/about-us/what-we-do/history
extraction_method: web_scrape_xpath
extraction_timestamp: "2025-12-20T15:00:00Z"
extraction_notes: "XPath: /html/body/main/section[2]/div/p[3]"
archive_path: web/0001/rijksmuseum.nl/about-us/rendered.html
data_tier: TIER_2_VERIFIED
description: Relocation event from institutional website