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

182 lines
6.9 KiB
YAML

id: https://nde.nl/ontology/hc/class/ConflictStatus
name: conflict_status_class
title: Conflict Status Class
imports:
- linkml:types
- ../metadata
- ../enums/ConflictStatusEnum
- ./TimeSpan
- ../slots/description
- ../slots/status
- ../slots/specificity_annotation
- ../slots/template_specificity
- ./SpecificityAnnotation
- ./TemplateSpecificityScores
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#
classes:
ConflictStatus:
class_uri: hc:ConflictStatus
description: |
Represents the status of a heritage custodian affected by armed conflict,
natural disaster, or deliberate destruction.
**PURPOSE**:
Documents the current condition of heritage institutions impacted by external
forces beyond normal organizational dissolution. This is critical for:
- Tracking heritage destruction in conflict zones (Gaza, Syria, Ukraine, Iraq)
- Monitoring post-disaster recovery efforts
- Supporting cultural heritage protection advocacy
- Connecting with international monitoring organizations
**DISTINCTION FROM DISSOLUTION**:
- Normal dissolution (merger, closure) → Use `temporal_extent.end_of_the_end`
- Involuntary destruction (conflict, disaster) → Use `conflict_status` + `time_of_destruction`
**RELATIONSHIP TO time_of_destruction**:
- `conflict_status`: Summary status object with description and sources
- `time_of_destruction`: Detailed TimeSpan with fuzzy temporal bounds
**DATA FLOW**:
1. Source documents (reports, news) → `conflict_status` extraction
2. `conflict_status.destruction_date` → `time_of_destruction.begin_of_the_end`
3. Frontend displays both in CustodianTimeline component
**EXAMPLE - Gaza Institution**:
```yaml
conflict_status:
status: destroyed
destruction_date: "2023-12-08"
reported_date: "2024-01-15"
description: "Library destroyed by Israeli airstrike during Gaza conflict."
is_rebuilding: false
sources:
- "Librarians and Archivists with Palestine - Gaza Report 2024"
```
**FRONTEND DISPLAY**:
- CustodianTimeline.tsx shows "💥 Vernietigd" or "💥 Vernietigd (herbouwend)"
- InstitutionInfoPanel.tsx passes destruction data to timeline
- Color: Dark red for destroyed+defunct, orange for rebuilding
**CIDOC-CRM ALIGNMENT**:
Models the result of crm:E6_Destruction or crm:E11_Modification events.
The causing event is documented in OrganizationalChangeEvent.
mixins: []
attributes:
status:
slot_uri: hc:conflictStatusValue
range: ConflictStatusEnum
required: true
description: |
The current status of the institution regarding conflict/disaster impact.
Uses ConflictStatusEnum values: DESTROYED, DAMAGED, THREATENED, etc.
examples:
- value: destroyed
description: Institution completely destroyed
- value: damaged
description: Institution significantly damaged but recoverable
destruction_date:
slot_uri: crm:P4_has_time-span
range: date
description: |
Date when destruction/damage occurred.
For single events, use exact date.
For gradual destruction, use start of period.
**Note**: For fuzzy temporal bounds, use `time_of_destruction` (TimeSpan).
**Renamed**: Was 'date', renamed to 'destruction_date' to avoid collision
with built-in 'date' type.
examples:
- value: '2023-12-08'
description: Exact date of airstrike
- value: '2023-10-07'
description: Start of siege period
aliases:
- date
reported_date:
slot_uri: prov:generatedAtTime
range: date
description: |
Date when the destruction/damage was reported or documented.
May differ from `destruction_date` when reports are delayed.
Important for provenance tracking.
examples:
- value: '2024-01-15'
description: Date when LAP Gaza Report was published
description:
slot_uri: schema:description
range: string
description: |
Human-readable description of the destruction/damage event.
Should include:
- Type of damage (destroyed, damaged, looted)
- Cause (airstrike, fire, looting, natural disaster)
- Impact on collections (if known)
examples:
- value: Library destroyed by Israeli airstrike during Gaza conflict. All
collections lost.
is_rebuilding:
slot_uri: hc:isRebuilding
range: boolean
description: |
Whether the institution is currently being rebuilt or restored.
When true, shows "💥 Vernietigd (herbouwend)" in timeline.
When false or absent, shows "💥 Vernietigd" in timeline.
examples:
- value: true
description: Institution being rebuilt after destruction
- value: false
description: No rebuilding efforts underway
has_or_had_documentation_source:
slot_uri: prov:hadPrimarySource
range: string
multivalued: true
description: |
List of sources documenting the destruction/damage.
Include report names, news articles, official statements.
These are displayed in the frontend for transparency.
examples:
- value: Librarians and Archivists with Palestine - Gaza Report 2024
- value: UNESCO Damaged Cultural Heritage in Gaza assessment
- value: Palestinian Ministry of Culture damage report
exact_mappings:
- crm:E6_Destruction
related_mappings:
- crm:E11_Modification
- prov:Activity
comments:
- Used for Gaza 2023-2024 conflict documentation (30+ institutions)
- 'Frontend: CustodianTimeline.tsx displays destruction events'
- Populated from LAP Gaza Report 2024 and other verified sources
see_also:
- hc:time_of_destruction
- https://github.com/nde-lab/glam/blob/main/frontend/src/components/map/CustodianTimeline.tsx
- https://github.com/nde-lab/glam/blob/main/scripts/convert_palestinian_to_custodian.py
slots:
- specificity_annotation
- template_specificity
slot_usage:
specificity_annotation:
range: SpecificityAnnotation
inlined: true
template_specificity:
range: TemplateSpecificityScores
inlined: true
slots:
reported_date:
description: Date when destruction/damage was reported
range: date
is_rebuilding:
description: Whether institution is being rebuilt
range: boolean
has_or_had_documentation_source:
slot_uri: prov:hadPrimarySource
description: Sources documenting the destruction/damage
range: string
multivalued: true