kempersc/glam
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
glam/schemas/20251121/linkml/modules/classes/FeaturePlace.yaml
kempersc dfa667c90f Fix LinkML schema for valid RDF generation with proper slot_uri 
Summary:
- Create 46 missing slot definition files with proper slot_uri values
- Add slot imports to main schema (01_custodian_name_modular.yaml)
- Fix YAML examples sections in 116+ class and slot files
- Fix PersonObservation.yaml examples section (nested objects → string literals)

Technical changes:
- All slots now have explicit slot_uri mapping to base ontologies (RiC-O, Schema.org, SKOS)
- Eliminates malformed URIs like 'custodian/:slot_name' in generated RDF
- gen-owl now produces valid Turtle with 153,166 triples

New slot files (46):
- RiC-O slots: rico_note, rico_organizational_principle, rico_has_or_had_holder, etc.
- Scope slots: scope_includes, scope_excludes, archive_scope
- Organization slots: organization_type, governance_authority, area_served
- Platform slots: platform_type_category, portal_type_category
- Social media slots: social_media_platform_category, post_type_*
- Type hierarchy slots: broader_type, narrower_types, custodian_type_broader
- Wikidata slots: wikidata_equivalent, wikidata_mapping

Generated output:
- schemas/20251121/rdf/01_custodian_name_modular_20260107_134534_clean.owl.ttl (6.9MB)
- Validated with rdflib: 153,166 triples, no malformed URIs
2026-01-07 13:48:03 +01:00

336 lines
12 KiB
YAML
Raw Blame History

id: https://nde.nl/ontology/hc/class/feature-place
name: feature_place_class
title: FeaturePlace Class
imports:
- linkml:types
- ./Custodian
- ./CustodianObservation
- ./ReconstructionActivity
- ../enums/FeatureTypeEnum
- ../enums/PlaceSpecificityEnum
- ./ReconstructedEntity
- ../slots/was_derived_from
- ../slots/was_generated_by
- ../slots/valid_from
- ../slots/valid_to
- ../slots/class_metadata_slots
slots:
feature_type:
range: FeatureTypeEnum
feature_name:
range: string
feature_language:
range: string
feature_description:
range: string
feature_note:
range: string
classifies_place:
range: uriorcurie
classes:
FeaturePlace:
is_a: ReconstructedEntity
class_uri: crm:E27_Site
description: |
Physical feature type classification for nominal place references.
CRITICAL: This is NOT a separate place - it CLASSIFIES the CustodianPlace.
**Relationship to CustodianPlace**:
CustodianPlace provides a NOMINAL REFERENCE to where a custodian is located:
- "Rijksmuseum" (building name as place reference)
- "het herenhuis in de Schilderswijk" (mansion in a neighborhood)
- "de kerk op het Damrak" (church on a street)
FeaturePlace provides the FEATURE TYPE of that same place:
- "Rijksmuseum" → FeaturePlace: MUSEUM (building type)
- "het herenhuis" → FeaturePlace: MANSION (building type)
- "de kerk" → FeaturePlace: PARISH_CHURCH (building type)
**Key Distinction**:
| CustodianPlace | FeaturePlace |
|----------------|--------------|
| WHERE (nominal reference) | WHAT TYPE (classification) |
| "Rijksmuseum" as place name | MUSEUM building type |
| "het herenhuis in Schilderswijk" | MANSION building type |
| Emic reference | Typological classification |
| crm:E53_Place | crm:E27_Site |
**Example Integration**:
```yaml
CustodianPlace:
place_name: "Rijksmuseum"
place_language: "nl"
place_specificity: BUILDING
has_feature_type: # ← Link to FeaturePlace
feature_type: MUSEUM
feature_name: "Rijksmuseum building"
feature_description: "Monumental museum building designed by P.J.H. Cuypers (1885)"
```
**Use Cases**:
- Classify building types (mansion, church, castle, palace)
- Identify monument types (memorial, sculpture, statue)
- Categorize landscape features (park, cemetery, garden)
- Specify infrastructure types (bridge, canal, fortification)
**Institution Type**: Corresponds to 'F' (FEATURES) in GLAMORCUBESFIXPHDNT taxonomy
**Generated by ReconstructionActivity**:
FeaturePlace is generated when physical feature types are identified for
nominal place references (e.g., classifying "the building" as a MANSION).
exact_mappings:
- crm:E27_Site
- schema:LandmarksOrHistoricalBuildings
close_mappings:
- crm:E53_Place
- schema:Place
- schema:TouristAttraction
related_mappings:
- prov:Entity
- dcterms:Location
- geo:Feature
slots:
- classifies_place
- custodian_types
- custodian_types_rationale
- feature_description
- feature_language
- feature_name
- feature_note
- feature_type
- specificity_annotation
- template_specificity
- valid_from
- valid_to
- was_derived_from
- was_generated_by
slot_usage:
feature_type:
description: |
Type of physical heritage feature (REQUIRED).
Specifies what kind of physical feature this is:
- MANSION: Historic mansion or large dwelling
- MONUMENT: Memorial or commemorative structure
- CHURCH: Religious building
- CASTLE: Fortified building
- CEMETERY: Burial ground
- PARK: Heritage park or garden
- etc. (298 types total)
range: FeatureTypeEnum
required: true
examples:
- value: MANSION
description: Historic mansion building
- value: PARISH_CHURCH
description: Historic church building
- value: CEMETERY
description: Historic burial ground
feature_name:
slot_uri: crm:P87_is_identified_by
description: |
Name/label of the physical feature type classification (OPTIONAL).
CIDOC-CRM: P87_is_identified_by links E1_CRM_Entity to E41_Appellation.
Usually derived from the CustodianPlace.place_name or describes the type.
Can be omitted if only feature_type classification is needed.
range: string
required: false
examples:
- value: Rijksmuseum building
description: Museum building type name
- value: Manor house in Schilderswijk
description: Mansion building type name
- value: Parish church structure
description: Church building type name
feature_language:
slot_uri: dcterms:language
description: |
Language of feature name.
Dublin Core: language for linguistic context.
range: string
required: false
examples:
- value: nl
description: Dutch feature name
- value: en
description: English feature name
feature_description:
slot_uri: dcterms:description
description: |
Description of the physical feature characteristics.
Dublin Core: description for textual descriptions.
Include:
- Architectural style/period
- Physical characteristics
- Heritage significance
- Construction details
range: string
required: false
examples:
- value: Neo-Gothic museum building designed by P.J.H. Cuypers, opened 1885
description: Museum building characteristics
- value: 17th-century canal mansion with ornate gable facade
description: Mansion architectural features
classifies_place:
slot_uri: dcterms:type
description: |
Link to the CustodianPlace that this feature type classifies (REQUIRED).
Dublin Core: type for classification relationship.
This links the feature type classification back to the nominal place reference.
Example: FeaturePlace(MUSEUM) classifies_place → CustodianPlace("Rijksmuseum")
range: CustodianPlace
required: true
examples:
- value: https://nde.nl/ontology/hc/place/rijksmuseum-location
description: Classifies 'Rijksmuseum' place as MUSEUM building type
feature_note:
slot_uri: skos:note
description: |
Contextual notes about the feature type classification.
SKOS: note for editorial annotations.
Use for:
- Classification rationale
- Architectural period
- Conservation status
- Heritage designation
range: string
required: false
examples:
- value: Classified as museum building based on current function
description: Classification reasoning
- value: 'Rijksmonument #12345, Neo-Gothic style'
description: Heritage and architectural notes
was_derived_from:
slot_uri: prov:wasDerivedFrom
description: |
CustodianObservation(s) from which this feature type was identified (REQUIRED).
PROV-O: wasDerivedFrom establishes observation→feature type derivation.
Feature type classification can be derived from:
- Architectural surveys describing building type
- Heritage registers classifying monuments
- Historical documents mentioning "mansion", "church", etc.
range: CustodianObservation
multivalued: true
required: true
was_generated_by:
slot_uri: prov:wasGeneratedBy
description: |
ReconstructionActivity that classified this feature type (optional).
If present: Classification created through formal reconstruction process
If null: Feature type extracted directly without reconstruction activity
PROV-O: wasGeneratedBy links Entity (FeaturePlace) to generating Activity.
range: ReconstructionActivity
required: false
valid_from:
slot_uri: schema:validFrom
description: |
Start of validity period for this feature type classification.
Schema.org: validFrom for temporal validity.
Use when:
- Feature type changed (mansion converted to museum building)
- Classification updated based on new evidence
range: date
required: false
examples:
- value: '1885-01-01'
description: Building completed, classified as museum from this date
- value: '1650-01-01'
description: Mansion construction date
valid_to:
slot_uri: schema:validThrough
description: |
End of validity period for this feature type classification.
Schema.org: validThrough for temporal validity.
Use when:
- Feature demolished/destroyed
- Building repurposed (mansion → office building)
- Classification no longer valid
range: date
required: false
examples:
- value: '1950-12-31'
description: Building demolished
- value: '2020-06-30'
description: Museum closed, building repurposed
custodian_types:
equals_expression: '["hc:FeatureCustodianType"]'
custodian_types_rationale:
equals_string: FeaturePlace represents physical heritage features (monuments,
statues) - maps to FeatureCustodianType type
specificity_annotation:
range: SpecificityAnnotation
inlined: true
template_specificity:
range: TemplateSpecificityScores
inlined: true
comments:
- 'Represents FEATURE TYPE CLASSIFICATION: typological classification of nominal
place references'
- 298 specific feature types from Wikidata heritage/place taxonomy
- 'CRITICAL: Classifies CustodianPlace, does NOT replace it'
- 'Example: CustodianPlace(''Rijksmuseum'') has FeaturePlace(MUSEUM)'
- Adds typological layer to nominal place references
- Maps to CIDOC-CRM E27_Site and Schema.org LandmarksOrHistoricalBuildings
- Institution Type F (FEATURES) when a physical feature IS the heritage custodian
itself
see_also:
- http://www.cidoc-crm.org/html/cidoc_crm_v7.1.3.html#E27
- https://schema.org/LandmarksOrHistoricalBuildings
- https://schema.org/Place
examples:
- value:
feature_type: MUSEUM
feature_name: Rijksmuseum building
feature_language: nl
feature_description: Neo-Gothic museum building designed by P.J.H. Cuypers,
opened 1885
feature_note: Rijksmonument, national heritage building
classifies_place: https://nde.nl/ontology/hc/place/rijksmuseum-ams
was_derived_from:
- https://w3id.org/heritage/observation/heritage-register-entry
was_generated_by: https://w3id.org/heritage/activity/feature-classification-2025
valid_from: '1885-07-13'
description: Museum building type classification for 'Rijksmuseum' place reference
- value:
feature_type: MANSION
feature_name: Canal mansion
feature_language: en
feature_description: 17th-century patrician mansion with ornate gable facade
feature_note: Classified as mansion based on architectural survey
classifies_place: https://nde.nl/ontology/hc/place/herenhuis-schilderswijk
was_derived_from:
- https://w3id.org/heritage/observation/notarial-deed-1850
valid_from: '1650-01-01'
description: Mansion type classification for 'het herenhuis in de Schilderswijk'
place reference
- value:
feature_type: PARISH_CHURCH
feature_name: Medieval parish church
feature_language: en
feature_description: Gothic church building with 14th-century tower
classifies_place: https://nde.nl/ontology/hc/place/oude-kerk-ams
was_derived_from:
- https://w3id.org/heritage/observation/church-archive-catalog
valid_from: '1306-01-01'
description: Church building type classification for 'Oude Kerk' place reference
Reference in a new issue View git blame Copy permalink