glam/schemas/20251121/linkml/modules/classes/BusinessCriticality.yaml
kempersc 90842851c2 Add slot definitions for 'updated_at' and 'written_in' with multilingual support and ontology alignment
- Created 'updated_at.yaml' to record the last modified date and time of entities, including multilingual descriptions and structured aliases.
- Created 'written_in.yaml' to specify the language in which content is composed, covering both natural and programming languages, with detailed comments and close ontology mappings.
2026-02-07 11:22:05 +01:00

62 lines
2.3 KiB
YAML

id: https://nde.nl/ontology/hc/class/BusinessCriticality
name: business_criticality_class
title: BusinessCriticality Class
description: 'Business criticality level classification for continuity planning.
Provides structured classification for operational impact assessment: - **CRITICAL**: Institution cannot function without (hours) - **HIGH**: Significant impact if unavailable (days) - **MEDIUM**: Important but workarounds exist (weeks) - **LOW**: Minimal operational impact
Drives backup and disaster recovery priorities.
Created per slot_fixes.yaml revision for business_criticality migration (Rule 53/56/57).'
version: 1.0.0
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
rico: https://www.ica.org/standards/RiC/ontology#
imports:
- linkml:types
- ../slots/20260202_matang/has_description
- ../slots/20260202_matang/identified_by
- ../slots/20260202_matang/has_label
default_prefix: hc
classes:
BusinessCriticality:
class_uri: hc:BusinessCriticality
description: 'Business criticality level for continuity planning.
Structured class replacing string-valued business_criticality slot. Enables type classification via has_type.'
slots:
- identified_by
- has_label
- has_description
slot_usage:
has_label:
required: true
examples:
- value: CRITICAL
- value: HIGH
- value: MEDIUM
- value: LOW
has_description:
required: false
examples:
- value: Financial system required for daily operations, payroll processing
- value: Historical project files, reference only, no operational dependency
examples:
- value:
has_label: CRITICAL
has_description: Financial system - required for operations, payroll cannot be processed without
- value:
has_label: HIGH
has_description: Director's correspondence - important for decision continuity
- value:
has_label: MEDIUM
has_description: Historical project files - reference only, operational workarounds exist
- value:
has_label: LOW
has_description: Promotional materials archive - minimal impact on operations
annotations:
specificity_score: 0.1
specificity_rationale: Generic utility class/slot created during migration
custodian_types: "['*']"