glam/schemas/20251121/linkml/modules/classes/DataSensitivityLevel.yaml
kempersc ca4a54181e Refactor schema files to improve clarity and maintainability
- Updated WorldCatIdentifier.yaml to remove unnecessary description and ensure consistent formatting.
- Enhanced WorldHeritageSite.yaml by breaking long description into multiple lines for better readability and removed unused attributes.
- Simplified WritingSystem.yaml by removing redundant attributes and ensuring consistent formatting.
- Cleaned up XPathScore.yaml by removing unnecessary attributes and ensuring consistent formatting.
- Improved YoutubeChannel.yaml by breaking long description into multiple lines for better readability.
- Enhanced YoutubeEnrichment.yaml by breaking long description into multiple lines for better readability.
- Updated YoutubeVideo.yaml to break long description into multiple lines and removed legacy field name.
- Refined has_or_had_affiliation.yaml by removing unnecessary comments and ensuring clarity.
- Cleaned up is_or_was_retrieved_at.yaml by removing unnecessary comments and ensuring clarity.
- Added rules for generic slots and avoiding rough edits in schema files to maintain structural integrity.
- Introduced changes_or_changed_through.yaml to define a new slot for linking entities to change events.
2026-01-31 00:46:23 +01:00

101 lines
No EOL
3.8 KiB
YAML

id: https://nde.nl/ontology/hc/class/DataSensitivityLevel
name: data_sensitivity_level_class
title: DataSensitivityLevel Class
description: >-
Data sensitivity classification level for records and information assets.
Used to categorize the confidentiality requirements and access restrictions
for administrative records, documents, and data systems.
Based on common information classification schemes including:
- ISO 27001 information security standards
- GDPR special category data requirements
- Dutch government classification (Rijksoverheid)
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
dcterms: http://purl.org/dc/terms/
schema: http://schema.org/
imports:
- linkml:types
- ../slots/has_or_had_code
- ../slots/has_or_had_description
- ../slots/has_or_had_label
default_prefix: hc
classes:
DataSensitivityLevel:
class_uri: hc:DataSensitivityLevel
description: >-
Data sensitivity classification level.
**Standard Classification Levels**:
| Level | Short Code | Description | Access |
|-------|------------|-------------|--------|
| Public | PUBLIC | No restrictions on disclosure | Anyone |
| Internal | INTERNAL | For internal use only | Staff only |
| Confidential | CONFIDENTIAL | Need-to-know basis | Authorized staff |
| Strictly Confidential | STRICTLY_CONFIDENTIAL | Highly restricted | Named individuals |
| Personal Data | PERSONAL_DATA | Contains PII (GDPR Article 6) | Data subjects + authorized |
| Special Category | SPECIAL_CATEGORY | Sensitive personal data (GDPR Article 9) | Strictly controlled |
**GDPR Alignment**:
- PERSONAL_DATA: Covers GDPR Article 6 personal data
- SPECIAL_CATEGORY: Covers GDPR Article 9 special categories (health, religion,
ethnicity, political opinions, trade union membership, genetic/biometric data,
sexual orientation)
**Dublin Core**: Maps to dcterms:accessRights for access classification.
exact_mappings:
- dcterms:accessRights
close_mappings:
- schema:accessMode
slots:
- has_or_had_label
- has_or_had_code
- has_or_had_description
slot_usage:
has_or_had_label:
range: string
required: true
examples:
- value: "Public"
- value: "Strictly Confidential"
has_or_had_code:
range: string
required: true
pattern: "^[A-Z][A-Z0-9_]*$"
examples:
- value: "PUBLIC"
- value: "CONFIDENTIAL"
- value: "SPECIAL_CATEGORY"
has_or_had_description:
range: string
required: false
examples:
- value: "Contains employee health records - requires explicit consent and strict access controls"
annotations:
specificity_score: 0.45
specificity_rationale: >-
Data sensitivity levels are moderately specific - used primarily in
records management and information governance contexts.
custodian_types: '["A", "O", "R"]'
custodian_types_rationale: >-
Most relevant for Archives (A), Official institutions (O), and
Research centers (R) that manage sensitive records.
examples:
- value:
has_or_had_label: "Confidential"
has_or_had_code: "CONFIDENTIAL"
has_or_had_description: "Need-to-know basis - restricted to authorized personnel"
- value:
has_or_had_label: "Special Category Data"
has_or_had_code: "SPECIAL_CATEGORY"
has_or_had_description: "GDPR Article 9 sensitive personal data - health records, religious affiliation"
- value:
has_or_had_label: "Personnel Data"
has_or_had_code: "PERSONAL_DATA"
has_or_had_description: "Contains employee personal information subject to GDPR"