- Removed obsolete slots: `has_or_had_custodian_observation`, `provider`, and `specificity_annotation`. - Updated `has_or_had_score` slot to use `SpecificityScore` class and modified its description and examples. - Added new slots: `end_seconds`, `end_time`, `has_archive_path`, `has_or_had_custodian_name`, `protocol_name`, and `protocol_version`. - Introduced a script `check_annotation_types.py` to validate the presence and structure of `custodian_types` in YAML files. - Added a script `update_specificity.py` to automate updates related to `SpecificityAnnotation` to `SpecificityScore`.
62 lines
2.4 KiB
YAML
62 lines
2.4 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/has_or_had_description
|
|
- ../slots/has_or_had_identifier
|
|
- ../slots/has_or_had_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_or_had_type.'
|
|
slots:
|
|
- has_or_had_identifier
|
|
- has_or_had_label
|
|
- has_or_had_description
|
|
slot_usage:
|
|
has_or_had_label:
|
|
required: true
|
|
examples:
|
|
- value: CRITICAL
|
|
- value: HIGH
|
|
- value: MEDIUM
|
|
- value: LOW
|
|
has_or_had_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_or_had_label: CRITICAL
|
|
has_or_had_description: Financial system - required for operations, payroll cannot be processed without
|
|
- value:
|
|
has_or_had_label: HIGH
|
|
has_or_had_description: Director's correspondence - important for decision continuity
|
|
- value:
|
|
has_or_had_label: MEDIUM
|
|
has_or_had_description: Historical project files - reference only, operational workarounds exist
|
|
- value:
|
|
has_or_had_label: LOW
|
|
has_or_had_description: Promotional materials archive - minimal impact on operations
|
|
annotations:
|
|
specificity_score: 0.1
|
|
specificity_rationale: Generic utility class/slot created during migration
|
|
custodian_types: "['*']"
|