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

91 lines
No EOL
4.2 KiB
YAML

id: https://nde.nl/ontology/hc/class/ApproximationStatus
name: approximation_status_class
title: ApproximationStatus Class
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
crm: http://www.cidoc-crm.org/cidoc-crm/
rico: https://www.ica.org/standards/RiC/ontology#
skos: http://www.w3.org/2004/02/skos/core#
imports:
- linkml:types
- ../metadata
- ../slots/has_or_had_description
- ../slots/has_or_had_label
- ../slots/has_or_had_level
- ../slots/has_or_had_score
- ../slots/specificity_annotation
- ./SpecificityAnnotation
- ./TemplateSpecificityScore
- ./TemplateSpecificityType
- ./TemplateSpecificityTypes
default_prefix: hc
classes:
ApproximationStatus:
class_uri: hc:ApproximationStatus
description: "Status indicating the level of approximation or uncertainty for a value.\n**PURPOSE**:\nApproximationStatus captures structured uncertainty information for values like dates, quantities, and measurements where precision varies. This replaces simple boolean \"approximate: true/false\" with richer modeling.\n**UNCERTAINTY LEVELS**:\n| Level | Label | Description | Example | |-------|-------|-------------|---------| | EXACT | Exact | Known with certainty | \"1880-03-15\" | | APPROXIMATE | Approximate | Close but not exact | \"circa 1880\" | | ESTIMATED | Estimated | Calculated/inferred | \"estimated 1875-1885\" | | UNCERTAIN | Uncertain | Significant doubt | \"possibly 19th century\" | | UNKNOWN | Unknown | Cannot be determined | \"date unknown\" |\n**CIDOC-CRM ALIGNMENT**:\nCIDOC-CRM models time-span precision through E52_Time-Span with fuzzy boundaries. ApproximationStatus provides a complementary vocabulary for expressing certainty levels.\n**USE CASES**:\n1. **Date Uncertainty**:\
\ Founding dates known only to decade 2. **Quantity Estimates**: Collection size approximations 3. **Location Precision**: Address known only to city level 4. **Historical Events**: Uncertain timing of organizational changes\n**EXAMPLE**:\n```yaml event_date: \"1880\" is_or_was_approximate:\n has_or_had_level: APPROXIMATE # was: approximation_level\n has_or_had_label: \"circa 1880\"\n has_or_had_description: \"Founding date known only to year from secondary sources\"\n```"
exact_mappings:
- crm:E52_Time-Span
close_mappings:
- rico:DateType
related_mappings:
- skos:note
slots:
- has_or_had_level
- has_or_had_label
- has_or_had_description
- specificity_annotation
- has_or_had_score
slot_usage:
has_or_had_level:
range: string
required: true
has_or_had_label:
range: string
required: false
examples:
- value: circa 1880
- value: approximately 10,000
has_or_had_description:
range: string
required: false
examples:
- value: Founding date derived from secondary sources, exact day unknown
comments:
- ApproximationStatus replaces simple boolean approximate field
- Provides structured uncertainty modeling for dates, quantities, etc.
- Aligned with CIDOC-CRM E52_Time-Span precision concepts
- Used by is_or_was_approximate slot
see_also:
- https://www.cidoc-crm.org/Entity/e52-time-span/version-7.1.3
examples:
- value:
has_or_had_level: EXACT
has_or_had_label: '1880-03-15'
- value:
has_or_had_level: APPROXIMATE
has_or_had_label: circa 1880
has_or_had_description: Founding date known only to year from newspaper accounts
- value:
has_or_had_level: ESTIMATED
has_or_had_label: estimated 1875-1885
has_or_had_description: Date range inferred from building construction records
- value:
has_or_had_level: UNKNOWN
has_or_had_label: date unknown
has_or_had_description: No founding records survive
annotations:
specificity_score: 0.3
specificity_rationale: Approximation status is broadly useful across contexts where uncertainty needs to be expressed.
custodian_types: "['*']"
enums:
ApproximationLevelEnum:
description: Levels of approximation/uncertainty for values.
permissible_values:
EXACT:
APPROXIMATE:
ESTIMATED:
UNCERTAIN:
UNKNOWN: