glam/schemas/20251121/linkml/modules/classes/Location.yaml
kempersc 1516d509cf Add metadata to LinkML class definitions and update prefixes
- Added `id`, `name`, `title`, and `description` fields to multiple LinkML class YAML files.
- Standardized prefixes across all class definitions.
- Introduced a new script `fix_linkml_metadata.py` to automate the addition of metadata to class files.
- Updated existing class files to ensure compliance with the new metadata structure.
2026-01-29 17:40:47 +01:00

112 lines
3.2 KiB
YAML

id: https://nde.nl/ontology/hc/class/Location
name: Location
title: Location
description: LinkML class definition for Location
prefixes:
linkml: https://w3id.org/linkml/
schema: http://schema.org/
skos: http://www.w3.org/2004/02/skos/core#
rico: https://www.ica.org/standards/RiC/ontology#
wd: http://www.wikidata.org/entity/
# Location class
# Generic geographic location representation
#
# Generation date: 2026-01-15
# Rule compliance: 0 (LinkML single source of truth), 38 (slot centralization)
#
# Generic location class for use by TransferEvent and other location-referencing entities
id: https://nde.nl/ontology/hc/class/Location
name: location_class
title: Location Class
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
locn: http://www.w3.org/ns/locn#
wgs84: http://www.w3.org/2003/01/geo/wgs84_pos#
default_prefix: hc
imports:
- linkml:types
- ../metadata
- ../slots/location_name
- ../slots/latitude
- ../slots/longitude
- ../slots/specificity_annotation
- ../slots/has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
- ./SpecificityAnnotation
- ./TemplateSpecificityScore # was: TemplateSpecificityScores - migrated per Rule 53 (2026-01-17)
- ./TemplateSpecificityType
- ./TemplateSpecificityTypes
classes:
Location:
class_uri: schema:Place
description: |
Generic geographic location representation.
**Purpose**:
Location provides a reusable class for representing geographic
locations with name and optional coordinates.
**Ontological Alignment**:
- **Primary**: `schema:Place` - Schema.org Place
- **Exact**: `locn:Location` - LOCN (W3C Location) location
- **Related**: `wgs84:Point` - WGS84 geo point (for coordinates)
**Use Cases**:
- Transfer event locations (origin/destination)
- Institution physical locations
- Collection storage locations
exact_mappings:
- locn:Location
related_mappings:
- wgs84:Point
slots:
- location_name
- latitude
- longitude
- specificity_annotation
- has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
slot_usage:
location_name:
description: |
Human-readable name of the location.
range: string
required: true
latitude:
description: |
WGS84 latitude coordinate.
range: float
required: false
longitude:
description: |
WGS84 longitude coordinate.
range: float
required: false
annotations:
custodian_types: '["*"]'
custodian_types_rationale: Locations apply to all heritage custodian types.
custodian_types_primary: null
specificity_score: 0.2
specificity_rationale: Generic location class applicable across all contexts.
examples:
- value: |
location_name: "Rijksmuseum Amsterdam"
latitude: 52.3600
longitude: 4.8852
description: "Location with coordinates"
- value: |
location_name: "Noord-Hollands Archief, Haarlem"
description: "Location with name only"