fix: correct hallucinated RiC-O terms and add locn ontology

RiC-O hallucinated terms fixed:
- FindingAidType.yaml: rico:FindingAidType → rico:DocumentaryFormType
- has_acquisition_method.yaml: rico:hasOrHadActivityType → prov:wasGeneratedBy
- has_activity_type.yaml: rico:hasOrHadActivityType → dcterms:type
- has_arrangement.yaml: rico:hasOrHadArrangement → dcterms:description
- has_or_had_finding_aid.yaml: rico:isDescribedBy → rico:isOrWasDescribedBy

The following terms do NOT exist in RiC-O 1.1:
- rico:FindingAidType (use rico:DocumentaryFormType)
- rico:hasOrHadActivityType (no equivalent)
- rico:hasOrHadArrangement (no equivalent)
- rico:isDescribedBy (correct form: rico:isOrWasDescribedBy)

Added LOCN ontology support:
- Copied locn.ttl to frontend/public/ontology/
- Added LOCN to ONTOLOGY_FILES in ontology-loader.ts
- Added locn prefix to OntologyTermPopup.tsx
- LOCN (http://www.w3.org/ns/locn#) is W3C Location Core Vocabulary
  for addresses and geometry (used by locn:Address)
This commit is contained in:
kempersc 2026-01-13 16:42:32 +01:00
parent 73b3b21017
commit 21ed120ac2
14 changed files with 396 additions and 49 deletions

View file

@ -0,0 +1,320 @@
@prefix cc: <http://creativecommons.org/ns#> .
@prefix dcat: <http://www.w3.org/ns/dcat#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix geo: <http://www.w3.org/2003/01/geo/wgs84_pos#> .
@prefix gsp: <http://www.opengis.net/ont/geosparql#> .
@prefix locn: <http://www.w3.org/ns/locn#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix rec: <http://www.w3.org/2001/02pd/rec54#> .
@prefix schema: <http://schema.org/> .
@prefix sf: <http://www.opengis.net/ont/sf#> .
@prefix sioc: <http://rdfs.org/sioc/ns#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix vann: <http://purl.org/vocab/vann/> .
@prefix voaf: <http://purl.org/vocommons/voaf#> .
@prefix vs: <http://www.w3.org/2003/06/sw-vocab-status/ns#> .
@prefix wdsr: <http://www.w3.org/2007/05/powder-s#> .
@prefix xml: <http://www.w3.org/XML/1998/namespace> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
locn:Address a rdfs:Class ;
rdfs:label "Address"@en ;
dcterms:identifier "locn:Address"^^xsd:string ;
rdfs:comment "An \"address representation\" as conceptually defined by the INSPIRE Address Representation data type. The locn:addressId property may be used to link this locn:Address to other representations."@en ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
vs:term_status "testing"@en ;
wdsr:describedby <https://joinup.ec.europa.eu/node/55858> .
locn:Geometry a rdfs:Class ;
rdfs:label "Geometry"@en ;
dcterms:identifier "locn:Geometry"^^xsd:string ;
vann:usageNote "This class defines the notion of \"geometry\" at the conceptual level, and it shall be encoded by using different formats (see usage note of the locn:geometry property)."@en ;
rdfs:comment "The locn:Geometry class provides the means to identify a location as a point, line, polygon, etc. expressed using coordinates in some coordinate reference system."@en ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
vs:term_status "unstable"@en .
rdfs:seeAlso rdfs:label "geographic identifier"@en ;
dcterms:identifier "rdfs:seeAlso"^^xsd:string ;
vann:usageNote "Used in the ISA Programme Location Core Vocabulary to provide a URI that identifies the location. This should be expressed using the rdfs:seeAlso property unless the identifier is already the subject of the description. Examples include URIs from GeoNames.org and DBpedia such as http://dbpedia.org/resource/ISO_3166-2:XX where XX is the ISO 3166 two character code for a country."@en ;
rdfs:comment "rdfs:seeAlso fully represents the ISA Programme Location Core Vocabulary concept of a geographic identifier."@en ;
rdfs:isDefinedBy rdfs: ;
vs:term_status "unstable"@en .
locn:address a rdf:Property ;
rdfs:label "address"@en ;
dcterms:identifier "locn:address"^^xsd:string ;
rdfs:comment "The locn:address property relationship associates any resource with the locn:Address class "@en ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
rdfs:range locn:Address ;
vs:term_status "testing"@en .
locn:addressArea a rdf:Property ;
rdfs:label "address area"@en ;
dcterms:identifier "locn:addressArea"^^xsd:string ;
rdfs:comment "The name or names of a geographic area or locality that groups a number of addressable objects for addressing purposes, without being an administrative unit. This would typically be part of a city, a neighbourhood or village. The domain of locn:addressArea is locn:Address."@en ;
rdfs:domain locn:Address ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
rdfs:range rdfs:Literal ;
vs:term_status "testing"@en .
locn:addressId a rdf:Property ;
rdfs:label "address ID"@en ;
dcterms:identifier "locn:addressId"^^xsd:string ;
rdfs:comment "The concept of adding a globally unique identifier for each instance of an address is a crucial part of the INSPIRE data spec. The domain of locn:addressId is locn:Address."@en ;
rdfs:domain locn:Address ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
rdfs:range rdfs:Literal ;
vs:term_status "unstable"@en .
locn:adminUnitL1 a rdf:Property ;
rdfs:label "admin unit level 1"@en ;
dcterms:identifier "locn:adminUnitL1"^^xsd:string ;
vann:usageNote "Best practice is to use the ISO 3166-1 code but if this is inappropriate for the context, country names should be provided in a consistent manner to reduce ambiguity. For example, either write 'United Kingdom' or 'UK' consistently throughout the data set and avoid mixing the two."@en ;
rdfs:comment "The uppermost administrative unit for the address, almost always a country. The domain of locn:adminUnitL1 is locn:Address and the range is a literal, conceptually defined by the INSPIRE Geographical Name data type."@en ;
rdfs:domain locn:Address ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
vs:term_status "testing"@en .
locn:adminUnitL2 a rdf:Property ;
rdfs:label "admin unit level 2"@en ;
dcterms:identifier "locn:adminUnitL2"^^xsd:string ;
rdfs:comment "The region of the address, usually a county, state or other such area that typically encompasses several localities. The domain of locn:adminUnitL2 is locn:Address and the range is a literal, conceptually defined by the INSPIRE Geographical Name data type."@en ;
rdfs:domain locn:Address ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
vs:term_status "testing"@en .
locn:fullAddress a rdf:Property ;
rdfs:label "full address"@en ;
dcterms:identifier "locn:fullAddress"^^xsd:string ;
rdfs:comment "The complete address written as a string, with or without formatting. The domain of locn:fullAddress is locn:Address."@en ;
rdfs:domain locn:Address ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
rdfs:range rdfs:Literal ;
vs:term_status "testing"@en .
locn:geographicName a rdf:Property ;
rdfs:label "geographic name"@en ;
dcterms:identifier "locn:geographicName"^^xsd:string ;
rdfs:comment """
A geographic name is a proper noun applied to a spatial object. Taking the example used in the relevant INSPIRE data specification (page 18), the following are all valid geographic names for the Greek capital:
- Αθήνα (the Greek endonym written in the Greek script)
- Athína (the standard Romanisation of the endonym)
- Athens (the English language exonym)
For INSPIRE-conformant data, provide the metadata for the geographic name using a skos:Concept as a datatype.
"""@en ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
vs:term_status "testing"@en ;
wdsr:describedby <https://joinup.ec.europa.eu/node/55858> .
locn:geometry a rdf:Property ;
rdfs:label "geometry"@en ;
dcterms:identifier "locn:geometry"^^xsd:string ;
vann:example """
The following are examples of equivalent statements using different geometry encodings. In the examples, prefix gsp is used for namespace URI http://www.opengis.net/ont/geosparql#, whereas prefix sf is used for namespace URI http://www.opengis.net/ont/sf#.
- WKT (GeoSPARQL)
:Resource locn:geometry
"<http://www.opengis.net/def/crs/OGC/1.3/CRS84> Point(-0.001475 51.477811)"^^gsp:wktLiteral .
- GML
:Resource locn:geometry
"<gml:Point srsName='http://www.opengis.net/def/crs/OGC/1.3/CRS84'>
<gml:coordinates>-0.001475, 51.477811</gml:coordinates></gml:Point>"^^gsp:gmlLiteral .
- RDF+WKT (GeoSPARQL)
:Resource locn:geometry
[ a sf:Point; gsp:asWKT "<http://www.opengis.net/def/crs/OGC/1.3/CRS84> Point(-0.001475 51.477811)"^^gsp:wktLiteral ] .
- RDF+GML (GeoSPARQL)
:Resource locn:geometry
[ a sf:Point; gsp:asGML
"<gml:Point srsName='http://www.opengis.net/def/crs/OGC/1.3/CRS84'>
<gml:coordinates>-0.001475, 51.477811</gml:coordinates></gml:Point>"^^gsp:gmlLiteral ] .
- RDF (WGS84 lat/long)
:Resource locn:geometry [ a geo:Point; geo:lat "51.477811"; geo:long "-0.001475" ] .
- RDF (schema.org)
:Resource locn:geometry [ a schema:GeoCoordinates; schema:latitude "51.477811"; schema:longitude "-0.001475" ] .
- geo URI
:Resource locn:geometry <geo:51.477811,-0.001475;u=0;crs=wgs84> .
- GeoHash URI
:Resource locn:geometry <http://geohash.org/gcpuzgnzvxkp> .
"""@en ;
vann:usageNote """
Depending on how a geometry is encoded, the range of this property may be one of the following:
- a literal (e.g., WKT - string literal -, GML, KML - XML literal)
- a geometry class, as those defined in the OGC's GeoSPARQL specification, in the W3C's Basic Geo (WGS84 lat/long) vocabulary, and at schema.org;
- geocoded URIs, as geo or GeoHash URIs, treated as URI references.
For interoperability reasons, it is recommended using one of the following:
- Any geometry:
- WKT, GML, and RDF+WKT/GML, as per the GeoSPARQL specification.
- KML (Keyhole Markup Language) - note that KML supports the following geometries only: point, line string, linear ring, and polygon.
- RDF as per the schema.org vocabulary (see classes schema:GeoCoordinates and schema:GeoShape).
- Points: one of the above, or:
- RDF as per the W3C Basic Geo (WGS84 lat/long) vocabulary.
- GeoHash URIs.
- geo URIs.
"""@en ;
rdfs:comment "Associates any resource with the corresponding geometry."@en ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
rdfs:range locn:Geometry ;
vs:term_status "testing"@en ;
wdsr:describedby <https://joinup.ec.europa.eu/node/55858> .
locn:location a rdf:Property ;
rdfs:label "location"@en ;
dcterms:identifier "locn:location"^^xsd:string ;
rdfs:comment "The location property links any resource to the Location Class. Asserting the location relationship implies only that the domain has some connection to a Location in time or space. It does not imply that the resource is necessarily at that location at the time when the assertion is made."@en ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
rdfs:range dcterms:Location ;
vs:term_status "testing"@en .
locn:locatorDesignator a rdf:Property ;
rdfs:label "locator designator"@en ;
dcterms:identifier "locn:locatorDesignator"^^xsd:string ;
rdfs:comment """A number or a sequence of characters that uniquely identifies the locator within the relevant scope(s). The full identification of the locator could include one or more locator designators.
"""@en ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
vs:term_status "testing"@en .
locn:locatorName a rdf:Property ;
rdfs:label "locator name"@en ;
dcterms:identifier "locn:locatorName"^^xsd:string ;
rdfs:comment """Proper noun(s) applied to the real world entity identified by the locator. The locator name could be the name of the property or complex, of the building or part of the building, or it could be the name of a room inside a building.
"""@en ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
vs:term_status "testing"@en .
locn:poBox a rdf:Property ;
rdfs:label "PO box"@en ;
dcterms:identifier "locn:poBox"^^xsd:string ;
rdfs:comment "The Post Office Box number. The domain of locn:poBox is locn:Address."@en ;
rdfs:domain locn:Address ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
rdfs:range rdfs:Literal ;
vs:term_status "testing"@en .
locn:postCode a rdf:Property ;
rdfs:label "post code"@en ;
dcterms:identifier "locn:postCode"^^xsd:string ;
rdfs:comment "The post code (a.k.a postal code, zip code etc.). Post codes are common elements in many countries' postal address systems. The domain of locn:postCode is locn:Address."@en ;
rdfs:domain locn:Address ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
rdfs:range rdfs:Literal ;
vs:term_status "testing"@en .
locn:postName a rdf:Property ;
rdfs:label "post name"@en ;
dcterms:identifier "locn:postName"^^xsd:string ;
rdfs:comment "The key postal division of the address, usually the city. (INSPIRE's definition is \"One or more names created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.\"). The domain of locn:postName is locn:Address."@en ;
rdfs:domain locn:Address ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
rdfs:range rdfs:Literal ;
vs:term_status "testing"@en .
locn:thoroughfare a rdf:Property ;
rdfs:label "thoroughfare"@en ;
dcterms:identifier "locn:thoroughfare"^^xsd:string ;
rdfs:comment "An address component that represents the name of a passage or way through from one location to another. A thoroughfare is not necessarily a road, it might be a waterway or some other feature. The domain of locn:thoroughfare is locn:Address."@en ;
rdfs:domain locn:Address ;
rdfs:isDefinedBy <http://www.w3.org/ns/locn> ;
rdfs:range rdfs:Literal ;
vs:term_status "testing"@en .
dcterms:Location rdfs:label "Location"@en ;
dcterms:identifier "dcterms:Location"^^xsd:string ;
vann:usageNote "This is the key class for the ISA Programme Location Core Vocabulary and represents any location, irrespective of size or other restriction."@en ;
rdfs:comment "dcterms:Location class fully represents the ISA Programme Location Core Vocabulary class of Location."@en ;
rdfs:isDefinedBy dcterms: ;
vs:term_status "testing"@en .
<http://www.w3.org/ns/locn.html> rdfs:label "HTML version of the ISA Programme Location Core Vocabulary"@en ;
dcat:mediaType "text/html"^^dcterms:IMT .
<http://www.w3.org/ns/locn.rdf> rdfs:label "RDF/XML version of the ISA Programme Location Core Vocabulary"@en ;
dcterms:format <http://www.w3.org/ns/formats/data/RDF_XML> ;
dcat:mediaType "application/rdf+xml"^^dcterms:IMT .
<http://www.w3.org/ns/locn.ttl> rdfs:label "Turtle version of the ISA Programme Location Core Vocabulary"@en ;
dcterms:format <http://www.w3.org/ns/formats/data/Turtle> ;
dcat:mediaType "text/turtle"^^dcterms:IMT .
<https://joinup.ec.europa.eu/category/licence/isa-open-metadata-licence-v11> cc:attributionName "European Commission"@en ;
cc:attributionURL <http://ec.europa.eu/> ;
dcterms:title "ISA Open Metadata Licence v1.1" .
<https://joinup.ec.europa.eu/node/43160> dcterms:title "Process and Methodology for Developing Core Vocabularies" .
<locn.svg> rdfs:label "Class and property diagram of the LOCN vocabulary" .
<https://joinup.ec.europa.eu/node/55858> dcterms:title "Core Vocabularies Specification" .
<http://www.w3.org/ns/locn> a voaf:Vocabulary,
owl:Ontology ;
rdfs:label "ISA Programme Location Core Vocabulary"@en ;
cc:attributionName "European Commission"@en ;
cc:attributionURL <http://ec.europa.eu/> ;
dcterms:abstract "The ISA Programme Location Core Vocabulary provides a minimum set of classes and properties for describing any place in terms of its name, address or geometry. The vocabulary is specifically designed to aid the publication of data that is interoperable with EU INSPIRE Directive. It is closely integrated with the Business and Person Core Vocabularies of the EU ISA Programme, now available in W3C space as, respectively, the Registered Organization vocabulary and ISA Person Core Vocabulary."@en ;
dcterms:conformsTo <https://joinup.ec.europa.eu/node/43160> ;
dcterms:hasFormat <http://www.w3.org/ns/locn.html>,
<http://www.w3.org/ns/locn.rdf>,
<http://www.w3.org/ns/locn.ttl> ;
dcterms:issued "2013-11-25"^^xsd:date ;
dcterms:license <https://joinup.ec.europa.eu/category/licence/isa-open-metadata-licence-v11> ;
dcterms:mediator [ foaf:homepage <http://www.w3.org/community/locadd/> ;
foaf:mbox <mailto:public-locadd@w3.org> ;
foaf:name "Locations and Addresses Community Group" ] ;
dcterms:modified "2015-03-23"^^xsd:date ;
dcterms:rights "Copyright © European Union, 2012-2015."@en ;
dcterms:title "ISA Programme Location Core Vocabulary"@en ;
vann:changes """
2015-03-23: Updates in the namespace document and in the RDF/XML and Turtle schemas:
- Fixed copyright notice.
- Added class and property diagram.
- Updated GeoSPARQL (a) namespace URIs and (b) datatype names in the examples of property locn:geometry, based on version 1.0 of the GeoSPARQL specification, and added a note in the examples.
- prefix ogc (http://www.opengis.net/rdf#) replaced with gsp (http://www.opengis.net/ont/geosparql#) and sf (http://www.opengis.net/ont/sf#)
- ogc:WKTLiteral gsp:wktLiteral
- ogc:GMLLiteral gsp:gmlLiteral
- Added namespace declarations for all namespace prefixes used in LOCN namespace document, even though they are not used in class/property definitions.
- Corrected the endonym of the Greek capital written in the Greek script in the definition of class locn:geographicName (Aθnνa Αθήνα).
- Fixed links and typos, minor revisions made to the textual descriptions.
2013-12-21: (PhilA) Update in RDF/XML and Turtle schemas:
- Updated voaf namespace.
- Corrected links to different distributions of the schema.
- Removed xml:base and used http://www/w3/org/ns/locn as the schema URI cf. original which used the namespace URI (with the final # character).
2013-11-25: Changes since final draft version released by the EU ISA Programme Core Vocabularies Working Group (Location Task Force)
- Revised usage note of class locn:Geometry. The text describing its recommended usage has been moved to usage note of property locn:geometry.
- Dropped domain/range restriction for locn:geographicName.
- Dropped domain/range restriction for locn:locatorDesignator. Free text definition updated accordingly.
- Dropped domain/range restriction for locn:locatorName. Free text definition updated accordingly.
- Corrected free text definition of property locn:geometry (its domain is "any resource", and not a "location").
- Revised usage note of property locn:geometry to include text about recommended usage, formerly included in the usage note of class locn:Geometry.
- Revised usage note and examples of property locn:geometry to include support to geocoded URIs (e.g., geo URIs, GeoHash URIs).
- Added term status. All terms have been set to "testing", with the exception of class locn:Geometry and properties rdfs:seeAlso (geographic identifier) and locn:addressId.
- Renamed subject in Turtle examples (ex:a :Resource).
- Fixed links and typos, minor revisions made to the textual descriptions.
"""@en ;
vann:preferredNamespacePrefix "locn"^^xsd:string ;
vann:preferredNamespaceUri "http://www.w3.org/ns/locn#"^^xsd:anyURI ;
voaf:classNumber "3"^^xsd:nonNegativeInteger ;
voaf:propertyNumber "16"^^xsd:nonNegativeInteger ;
voaf:reliesOn dcterms:,
rdfs: ;
rdfs:comment "This is a new version of the final draft published by the European Commission in May 2012, revised according to the results of the ISA Core Location Pilot (see Section Change History for the list of changes). It is currently under the control of the Locations and Addresses Community Group, but is not under active development or review. Comments and queries should be sent to that group via public-locadd@w3.org. Terms defined here may be deprecated by that or future groups but will not disappear or their definition change."@en ;
rec:editor [ schema:affiliation [ foaf:homepage <https://ec.europa.eu/jrc/> ;
foaf:name "European Commission - Joint Research Centre (JRC)"@en ] ;
foaf:name "Michael Lutz" ],
[ schema:affiliation [ foaf:homepage <http://www.w3.org/> ;
foaf:name "W3C/ERCIM" ] ;
rdfs:seeAlso <http://philarcher.org/foaf.rdf#me> ;
foaf:homepage <http://philarcher.org/> ;
foaf:name "Phil Archer" ],
[ schema:affiliation [ foaf:homepage <https://ec.europa.eu/jrc/> ;
foaf:name "European Commission - Joint Research Centre (JRC)"@en ] ;
rdfs:seeAlso <http://andrea-perego.name/foaf/#me> ;
foaf:homepage <http://about.me/andrea.perego> ;
foaf:name "Andrea Perego" ] ;
owl:versionInfo "First version in w3.org/ns space"@en ;
wdsr:describedby <https://joinup.ec.europa.eu/node/55858> ;
foaf:depiction <locn.svg> ;
foaf:maker [ foaf:homepage <https://joinup.ec.europa.eu/node/42444> ;
foaf:name "EU ISA Programme Core Vocabularies Working Group (Location Task Force)" ] .

View file

@ -37,14 +37,13 @@ imports:
- ./TemplateSpecificityScores
classes:
FindingAidType:
class_uri: rico:FindingAidType
class_uri: rico:DocumentaryFormType
abstract: true
description: "Abstract base class for finding aid type classification.\n\nA finding aid is a descriptive tool that establishes\
\ intellectual and physical\ncontrol over records by describing them and facilitating access. Finding aids\nrange from\
\ simple lists to elaborate guides with narrative descriptions.\n\n1. **RiC-O (Records in Contexts)**:\n - `rico:FindingAid`\
\ - \"A finding aid is a set of descriptions that\n identifies, locates, summarizes, and indexes materials in a\n\
\ record-holding organization.\"\n - Properties: rico:hasRecordSetType, rico:hasExtent\n\n2. **CIDOC-CRM**:\n\
\ - crm:E31_Document - Conceptual object serving as finding aid\n - crm:E33_Linguistic_Object - Textual description\n\
\ simple lists to elaborate guides with narrative descriptions.\n\n1. **RiC-O (Records in Contexts)**:\n - Finding aids\
\ in RiC-O are Records with `rico:DocumentaryFormType` = `FindingAid`\n - Uses `rico:hasDocumentaryFormType` to classify\
\ finding aids\n - Vocabulary value: `rico-voc:FindingAid`\n\n2. **CIDOC-CRM**:\n - crm:E31_Document - Conceptual object serving as finding aid\n - crm:E33_Linguistic_Object - Textual description\n\
\n3. **BIBFRAME**:\n - bf:Work - Intellectual content of finding aid\n - bf:Instance - Specific manifestation (print,\
\ online)\n\n4. **Schema.org**:\n - schema:CreativeWork - Published finding aid\n - schema:Dataset - Structured\
\ finding aid data\n\n**FINDING AID TYPE HIERARCHY**:\n\n```\nFindingAidType (abstract root)\n │\n ├── Inventory (Q65769447)\n\
@ -68,9 +67,9 @@ classes:
\ library holdings\"\n ```\n\n3. **Museum Guide**:\n ```yaml\n finding_aid_type: RepositoryGuide\n wikidata_id:\
\ Q117649202\n description: \"Overview guide to museum collections\"\n ```\n"
exact_mappings:
- rico:FindingAidType
- skos:Concept
- rico:DocumentaryFormType
close_mappings:
- skos:Concept
- bf:Work
- schema:CreativeWork
- crm:E31_Document

View file

@ -15,6 +15,8 @@ slots:
description: 'How the collection was acquired by current custodian.
PROV-O: wasGeneratedBy links entities to the activity that produced them.
CIDOC-CRM: P24i_changed_ownership_through for acquisition event.
@ -34,16 +36,16 @@ slots:
'
range: string
slot_uri: rico:hasOrHadActivityType
slot_uri: prov:wasGeneratedBy
exact_mappings:
- rico:hasOrHadActivityType
- prov:wasGeneratedBy
close_mappings:
- schema:acquiredFrom
related_mappings:
- prov:wasGeneratedBy
annotations:
custodian_types: '["*"]'
custodian_types_rationale: Applicable to all heritage custodian types.
custodian_types_primary: M
specificity_score: 0.5
specificity_rationale: Moderately specific slot.
ontology_note: "RiC-O does not define 'hasOrHadActivityType'. Using prov:wasGeneratedBy\
\ to model the provenance of acquisition."

View file

@ -15,6 +15,8 @@ slots:
description: 'Classification of this curation activity from CurationActivityTypeEnum.
Dublin Core: dcterms:type for general resource type classification.
CIDOC-CRM: P2_has_type for activity classification.
@ -24,15 +26,16 @@ slots:
'
range: string
slot_uri: rico:hasOrHadActivityType
slot_uri: dcterms:type
exact_mappings:
- rico:hasOrHadActivityType
- dcterms:type
close_mappings:
- schema:additionalType
- dcterms:type
annotations:
custodian_types: '["*"]'
custodian_types_rationale: Applicable to all heritage custodian types.
custodian_types_primary: M
specificity_score: 0.5
specificity_rationale: Moderately specific slot.
ontology_note: "RiC-O does not define 'hasOrHadActivityType'. Using dcterms:type\
\ for general type classification."

View file

@ -11,10 +11,12 @@ imports:
default_prefix: hc
slots:
has_arrangement:
description: 'Intellectual has_arrangement or classification system.
description: 'Intellectual arrangement or classification system.
RiC-O: hasArrangement for organizational structure.
Dublin Core: dcterms:description for descriptive information about organization.
EAD: <arrangement> element describes intellectual or physical arrangement.
Describes how the collection is organized:
@ -29,14 +31,15 @@ slots:
'
range: string
slot_uri: rico:hasOrHadArrangement
slot_uri: dcterms:description
exact_mappings:
- rico:hasOrHadArrangement
close_mappings:
- dcterms:description
annotations:
custodian_types: '["A"]'
custodian_types_rationale: Applicable to all heritage custodian types.
custodian_types_primary: M
custodian_types_rationale: Primarily applicable to archives.
custodian_types_primary: A
specificity_score: 0.9
specificity_rationale: Moderately specific slot.
specificity_rationale: Highly specific to archival arrangement.
ontology_note: "RiC-O does not define 'hasOrHadArrangement'. Using dcterms:description\
\ as arrangement is descriptive text about organization. Consider creating\
\ a project-specific predicate hc:hasArrangement if more precision is needed."

View file

@ -6,8 +6,8 @@ prefixes:
rico: https://www.ica.org/standards/RiC/ontology#
slots:
has_or_had_finding_aid:
slot_uri: rico:isDescribedBy
description: "Finding aids describing this collection.\n\nRiC-O: isDescribedBy links RecordSet to its descriptive tools.\n\
slot_uri: rico:isOrWasDescribedBy
description: "Finding aids describing this collection.\n\nRiC-O: isOrWasDescribedBy links RecordSet to its descriptive tools.\n\
\n**Replaces the previous simple `finding_aid_url` slot.**\n\nCollections may have multiple finding aids of different\
\ types:\n- Archival inventory (detailed item/folder listing)\n- Repository guide (overview description)\n- Online catalog\
\ (searchable database)\n- Published bibliography\n\nEach FindingAid object includes:\n- `finding_aid_type_ref` → FindingAidType\
@ -22,6 +22,8 @@ slots:
examples:
- value: https://nde.nl/ontology/hc/finding-aid/voc-inventory
description: VOC collection inventory
exact_mappings:
- rico:isOrWasDescribedBy
close_mappings:
- rico:hasInstantiation
related_mappings:

View file

@ -59,6 +59,7 @@ const STANDARD_PREFIXES: Record<string, string> = {
'geo': 'http://www.w3.org/2003/01/geo/wgs84_pos#',
'time': 'http://www.w3.org/2006/time#',
'vcard': 'http://www.w3.org/2006/vcard/ns#',
'locn': 'http://www.w3.org/ns/locn#',
// Wikidata
'wd': 'http://www.wikidata.org/entity/',

View file

@ -441,6 +441,14 @@ export const ONTOLOGY_FILES: OntologyFile[] = [
description: 'Contact information (addresses, phones, emails)',
namespaces: ['http://www.w3.org/2006/vcard/ns#']
},
{
name: 'LOCN',
path: 'locn.ttl',
format: 'ttl',
category: 'utility',
description: 'W3C Location Core Vocabulary - addresses and geometry',
namespaces: ['http://www.w3.org/ns/locn#']
},
{
name: 'PAV',
path: 'pav.rdf',

View file

@ -1,5 +1,5 @@
{
"generated": "2026-01-13T14:57:26.896Z",
"generated": "2026-01-13T15:42:33.105Z",
"schemaRoot": "/schemas/20251121/linkml",
"totalFiles": 2886,
"categoryCounts": {

View file

@ -37,14 +37,13 @@ imports:
- ./TemplateSpecificityScores
classes:
FindingAidType:
class_uri: rico:FindingAidType
class_uri: rico:DocumentaryFormType
abstract: true
description: "Abstract base class for finding aid type classification.\n\nA finding aid is a descriptive tool that establishes\
\ intellectual and physical\ncontrol over records by describing them and facilitating access. Finding aids\nrange from\
\ simple lists to elaborate guides with narrative descriptions.\n\n1. **RiC-O (Records in Contexts)**:\n - `rico:FindingAid`\
\ - \"A finding aid is a set of descriptions that\n identifies, locates, summarizes, and indexes materials in a\n\
\ record-holding organization.\"\n - Properties: rico:hasRecordSetType, rico:hasExtent\n\n2. **CIDOC-CRM**:\n\
\ - crm:E31_Document - Conceptual object serving as finding aid\n - crm:E33_Linguistic_Object - Textual description\n\
\ simple lists to elaborate guides with narrative descriptions.\n\n1. **RiC-O (Records in Contexts)**:\n - Finding aids\
\ in RiC-O are Records with `rico:DocumentaryFormType` = `FindingAid`\n - Uses `rico:hasDocumentaryFormType` to classify\
\ finding aids\n - Vocabulary value: `rico-voc:FindingAid`\n\n2. **CIDOC-CRM**:\n - crm:E31_Document - Conceptual object serving as finding aid\n - crm:E33_Linguistic_Object - Textual description\n\
\n3. **BIBFRAME**:\n - bf:Work - Intellectual content of finding aid\n - bf:Instance - Specific manifestation (print,\
\ online)\n\n4. **Schema.org**:\n - schema:CreativeWork - Published finding aid\n - schema:Dataset - Structured\
\ finding aid data\n\n**FINDING AID TYPE HIERARCHY**:\n\n```\nFindingAidType (abstract root)\n │\n ├── Inventory (Q65769447)\n\
@ -68,9 +67,9 @@ classes:
\ library holdings\"\n ```\n\n3. **Museum Guide**:\n ```yaml\n finding_aid_type: RepositoryGuide\n wikidata_id:\
\ Q117649202\n description: \"Overview guide to museum collections\"\n ```\n"
exact_mappings:
- rico:FindingAidType
- skos:Concept
- rico:DocumentaryFormType
close_mappings:
- skos:Concept
- bf:Work
- schema:CreativeWork
- crm:E31_Document

View file

@ -15,6 +15,8 @@ slots:
description: 'How the collection was acquired by current custodian.
PROV-O: wasGeneratedBy links entities to the activity that produced them.
CIDOC-CRM: P24i_changed_ownership_through for acquisition event.
@ -34,16 +36,16 @@ slots:
'
range: string
slot_uri: rico:hasOrHadActivityType
slot_uri: prov:wasGeneratedBy
exact_mappings:
- rico:hasOrHadActivityType
- prov:wasGeneratedBy
close_mappings:
- schema:acquiredFrom
related_mappings:
- prov:wasGeneratedBy
annotations:
custodian_types: '["*"]'
custodian_types_rationale: Applicable to all heritage custodian types.
custodian_types_primary: M
specificity_score: 0.5
specificity_rationale: Moderately specific slot.
ontology_note: "RiC-O does not define 'hasOrHadActivityType'. Using prov:wasGeneratedBy\
\ to model the provenance of acquisition."

View file

@ -15,6 +15,8 @@ slots:
description: 'Classification of this curation activity from CurationActivityTypeEnum.
Dublin Core: dcterms:type for general resource type classification.
CIDOC-CRM: P2_has_type for activity classification.
@ -24,15 +26,16 @@ slots:
'
range: string
slot_uri: rico:hasOrHadActivityType
slot_uri: dcterms:type
exact_mappings:
- rico:hasOrHadActivityType
- dcterms:type
close_mappings:
- schema:additionalType
- dcterms:type
annotations:
custodian_types: '["*"]'
custodian_types_rationale: Applicable to all heritage custodian types.
custodian_types_primary: M
specificity_score: 0.5
specificity_rationale: Moderately specific slot.
ontology_note: "RiC-O does not define 'hasOrHadActivityType'. Using dcterms:type\
\ for general type classification."

View file

@ -11,10 +11,12 @@ imports:
default_prefix: hc
slots:
has_arrangement:
description: 'Intellectual has_arrangement or classification system.
description: 'Intellectual arrangement or classification system.
RiC-O: hasArrangement for organizational structure.
Dublin Core: dcterms:description for descriptive information about organization.
EAD: <arrangement> element describes intellectual or physical arrangement.
Describes how the collection is organized:
@ -29,14 +31,15 @@ slots:
'
range: string
slot_uri: rico:hasOrHadArrangement
slot_uri: dcterms:description
exact_mappings:
- rico:hasOrHadArrangement
close_mappings:
- dcterms:description
annotations:
custodian_types: '["A"]'
custodian_types_rationale: Applicable to all heritage custodian types.
custodian_types_primary: M
custodian_types_rationale: Primarily applicable to archives.
custodian_types_primary: A
specificity_score: 0.9
specificity_rationale: Moderately specific slot.
specificity_rationale: Highly specific to archival arrangement.
ontology_note: "RiC-O does not define 'hasOrHadArrangement'. Using dcterms:description\
\ as arrangement is descriptive text about organization. Consider creating\
\ a project-specific predicate hc:hasArrangement if more precision is needed."

View file

@ -6,8 +6,8 @@ prefixes:
rico: https://www.ica.org/standards/RiC/ontology#
slots:
has_or_had_finding_aid:
slot_uri: rico:isDescribedBy
description: "Finding aids describing this collection.\n\nRiC-O: isDescribedBy links RecordSet to its descriptive tools.\n\
slot_uri: rico:isOrWasDescribedBy
description: "Finding aids describing this collection.\n\nRiC-O: isOrWasDescribedBy links RecordSet to its descriptive tools.\n\
\n**Replaces the previous simple `finding_aid_url` slot.**\n\nCollections may have multiple finding aids of different\
\ types:\n- Archival inventory (detailed item/folder listing)\n- Repository guide (overview description)\n- Online catalog\
\ (searchable database)\n- Published bibliography\n\nEach FindingAid object includes:\n- `finding_aid_type_ref` → FindingAidType\
@ -22,6 +22,8 @@ slots:
examples:
- value: https://nde.nl/ontology/hc/finding-aid/voc-inventory
description: VOC collection inventory
exact_mappings:
- rico:isOrWasDescribedBy
close_mappings:
- rico:hasInstantiation
related_mappings: