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

132 lines
3.8 KiB
YAML

id: https://nde.nl/ontology/hc/class/City
name: City
title: City
description: LinkML class definition for City
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/
# City - A city/town settlement entity
# Created: 2026-01-18
# Migration from city (string) slot per slot_fixes.yaml revision
# City is_a Settlement per established pattern
id: https://nde.nl/ontology/hc/class/City
name: city_class
title: City Class
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
gn: http://www.geonames.org/ontology#
wikidata: http://www.wikidata.org/entity/
crm: http://www.cidoc-crm.org/cidoc-crm/
imports:
- linkml:types
- ./Settlement
default_prefix: hc
classes:
City:
is_a: Settlement
class_uri: schema:City
description: |
A city or large town settlement.
**RELATIONSHIP TO SETTLEMENT**:
City is a subclass of Settlement representing urban areas that are
typically larger and more administratively significant than villages
or small towns.
**GeoNames Feature Codes**:
Cities typically correspond to GeoNames feature codes:
- PPL: Populated place (general)
- PPLA: Seat of first-order administrative division
- PPLA2: Seat of second-order administrative division
- PPLC: Capital of a political entity
- PPLS: Populated places (urban agglomerations)
**USAGE**:
Use City class when:
- The settlement is known to be a city (not village/hamlet)
- You need to express city-specific semantics
- Schema.org City alignment is important
Use Settlement class when:
- The settlement type is unknown or mixed
- You want the most general geographic entity
**EXAMPLES**:
```yaml
is_or_was_located_in:
- settlement_name: "Amsterdam"
geonames_id: 2759794
country: "NL"
```
exact_mappings:
- schema:City
close_mappings:
- gn:P.PPLA
- gn:P.PPLC
- wikidata:Q515
related_mappings:
- crm:E53_Place
# Inherits all slots from Settlement:
# - settlement_name
# - geonames_id
# - latitude
# - longitude
# - country
# - has_or_had_geographic_subdivision (subregion)
# - specificity_annotation
# - has_or_had_score
annotations:
specificity_score: 0.35
specificity_rationale: |
Slightly more specific than Settlement (0.30) as it indicates
urban status, but still broadly applicable across heritage contexts.
custodian_types: '["*"]'
custodian_types_rationale: |
All heritage custodians are located in cities or settlements.
custodian_types_primary: "*"
examples:
- value:
settlement_name: "Amsterdam"
geonames_id: 2759794
country: "NL"
has_or_had_geographic_subdivision:
subregion_code: "NL-NH"
description: Amsterdam - capital and largest city of the Netherlands
- value:
settlement_name: "Haarlem"
geonames_id: 2755420
country: "NL"
latitude: 52.3873
longitude: 4.6462
description: Haarlem - city in Noord-Holland province
- value:
settlement_name: "Tokyo"
geonames_id: 1850147
country: "JP"
description: Tokyo - capital of Japan
comments:
- City is_a Settlement following semantic hierarchy
- Inherits all Settlement slots including GeoNames ID
- Use for explicit urban classification
- Created per slot_fixes.yaml migration for city slot (2026-01-18)