glam/schemas/20251121/linkml/modules/classes/PublicationEvent.yaml
2026-02-08 19:22:13 +01:00

110 lines
3.1 KiB
YAML

id: https://nde.nl/ontology/hc/class/PublicationEvent
name: publication_event_class
title: Publication Event Class
description: 'Event representing the publication of content, following CIDOC-CRM event modeling.
CREATED 2026-01-17 per Rule 53/56: Provides structured publication event
representation instead of simple datetime. Enables rich temporal modeling
including fuzzy date boundaries.
Supports:
- Social media posts with publication timestamps
- Document publications with date ranges
- Historical publications with uncertain dates
'
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
crm: http://www.cidoc-crm.org/cidoc-crm/
schema: http://schema.org/
prov: http://www.w3.org/ns/prov#
dcterms: http://purl.org/dc/terms/
imports:
- linkml:types
- ../slots/20260202_matang/identified_by
- ../slots/20260202_matang/has_label
- ../slots/20260202_matang/has_score
- ../slots/20260202_matang/temporal_extent
default_prefix: hc
classes:
PublicationEvent:
class_uri: crm:E7_Activity
description: 'Event of content being published, following CIDOC-CRM activity pattern.
MIGRATED from published_at datetime slot per Rule 53/56 (2026-01-17).
**Why Event Wrapper?**
- Enables fuzzy temporal boundaries (uncertainty in publication dates)
- Supports multiple publication events (republications, versions)
- Links to agents/locations involved in publication
- Follows ontology best practices (CIDOC-CRM activity modeling)
**USE CASES**:
- Social media posts: Precise publication timestamp
- Historical documents: "Published sometime in 1892"
- Archival records: "Published between 1800-1805"
**FOR PRECISE TIMESTAMPS**:
Set all four TimeSpan boundaries to the same instant.
'
exact_mappings:
- crm:E7_Activity
- prov:Activity
close_mappings:
- schema:PublishAction
related_mappings:
- dcterms:created
slots:
- temporal_extent
- has_label
- identified_by
- has_score
slot_usage:
temporal_extent:
range: TimeSpan
inlined: true
required: true
has_label:
required: false
comments:
- 'Precise date: Set begin_of_the_begin == end_of_the_begin == begin_of_the_end == end_of_the_end'
- 'Uncertain date: Use fuzzy boundaries (e.g., begin_of_the_begin: 1892-01-01, end_of_the_end: 1892-12-31)'
examples:
- value:
temporal_extent:
begin_of_the_begin: '2025-07-30T18:05:15Z'
end_of_the_begin: '2025-07-30T18:05:15Z'
begin_of_the_end: '2025-07-30T18:05:15Z'
end_of_the_end: '2025-07-30T18:05:15Z'
- value:
temporal_extent:
begin_of_the_begin: '1892-01-01T00:00:00Z'
end_of_the_begin: '1892-06-30T00:00:00Z'
begin_of_the_end: '1892-06-30T00:00:00Z'
end_of_the_end: '1892-12-31T00:00:00Z'
has_label: First Edition
annotations:
specificity_score: 0.1
specificity_rationale: Generic utility class/slot created during migration
custodian_types: "['*']"