glam/schemas/20251121/linkml/modules/classes/SecurityLevel.yaml
kempersc 1f04a26b12 feat: Introduce MeasureUnitEnum for standardized measurement units
- Added MeasureUnitEnum.yaml to define standard measurement units for area, length, and related quantities, compliant with ISO 80000-1, QUDT, and UCUM.
- Included units such as square meters, hectares, acres, meters, kilometers, and their conversions.

feat: Create applies_or_applied_to_call slot for funding requirements

- Introduced applies_or_applied_to_call.yaml to track funding calls related to requirements, following RiC-O naming conventions.

chore: Archive annual_participants slot and migrate to has_or_had_annual_participant_count

- Archived annual_participants_archived_20260115.yaml, replaced with has_or_had_annual_participant_count for better temporal naming.

chore: Archive applies_to_call slot and migrate to applies_or_applied_to_call

- Archived applies_to_call_archived_20260115.yaml, replaced with applies_or_applied_to_call for improved naming consistency.

chore: Archive area_hectares slot and migrate to has_area_in_hectare

- Archived area_hectares_archived_20260115.yaml, replaced with has_area_in_hectare for standardized area measurement.

chore: Archive arrangement_notes slot and migrate to has_arrangement_note

- Archived arrangement_notes_archived_20260115.yaml, replaced with has_arrangement_note for better naming alignment.

chore: Archive available_caption_languages slot and migrate to has_available_caption_language

- Archived available_caption_languages_archived_20260115.yaml, replaced with has_available_caption_language for improved naming.

chore: Archive beneficiary_group slot and migrate to has_or_had_beneficiary

- Archived beneficiary_group_archived_20260115.yaml, replaced with has_or_had_beneficiary for compliance with naming conventions.

chore: Archive branch_head slot and migrate to has_or_had_head

- Archived branch_head_archived_20260114.yaml, replaced with has_or_had_head for better semantic alignment.

chore: Archive budget_currency slot

- Archived budget_currency_archived_20260114.yaml for future migration.

chore: Archive building_floor_area_sqm slot and migrate to has_or_had_area

- Archived building_floor_area_sqm_archived_20260115.yaml, replaced with has_or_had_area for standardized area measurement.

chore: Archive has_area_in_hectare slot and migrate to has_or_had_area

- Archived has_area_in_hectare_archived_20260115.yaml, replaced with has_or_had_area for compliance with generic predicates.

feat: Introduce has_or_had_area slot for area measurements

- Added has_or_had_area.yaml as the authoritative slot for area measurements, compliant with Rule 53.

feat: Introduce has_or_had_beneficiary slot for beneficiary tracking

- Added has_or_had_beneficiary.yaml to identify beneficiaries of organizational programs, following RiC-O naming conventions.

feat: Introduce has_or_had_currency slot for monetary values

- Added has_or_had_currency.yaml to track currency associated with monetary amounts, compliant with ISO 4217.

feat: Introduce has_or_had_head slot for organizational heads

- Added has_or_had_head.yaml to link organizational units with their heads, following W3C ORG standards.
2026-01-14 20:18:38 +01:00

65 lines
1.5 KiB
YAML

# SecurityLevel - Security classification class
#
# Created per slot_fixes.yaml migration for: warehouse_security_level
# Creation date: 2026-01-14
id: https://nde.nl/ontology/hc/class/SecurityLevel
name: SecurityLevel
title: Security Level
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
skos: http://www.w3.org/2004/02/skos/core#
default_prefix: hc
imports:
- linkml:types
- ../slots/has_or_had_code
classes:
SecurityLevel:
class_uri: skos:Concept
description: |
A security classification or level.
**USAGE**:
Used for:
- Warehouse security levels
- Document classifications
- Access control tiers
slots:
- has_or_had_code
attributes:
level_name:
range: string
description: Human-readable security level name
examples:
- value: "High Security"
level_rank:
range: integer
description: Numeric rank (higher = more secure)
access_requirements:
range: string
multivalued: true
description: Requirements for access at this level
exact_mappings:
- skos:Concept
annotations:
specificity_score: "0.50"
specificity_rationale: "Moderately specific - security relevant to storage facilities."
examples:
- value:
has_or_had_code: "HIGH"
level_name: "High Security"
level_rank: 3
description: High security level