Loc-I Data Profile - Specification

2.1 Dataset

D-title: Each Dataset MUST have one and only one English title which is an English text literal, indicated using the skos:prefLabel property

skos:prefLabel is to be used rather than rdfs:label or dcterms:title or other, similar, titling properties.

D-defn: Each Dataset MUST have one and only one English definition which is an English text literal, indicated using the skos:definition property

skos:definition is to be used rather than rdfs:comment or dcterms:description or other, similar, description properties.

D-id: Each Dataset MUST have one and only one identifier, an xsd:token, indicated using the dcterms:identifier property

This identifier MUST be unique among Loc-I Datasets. This uniqueness is not testable in SHACL

D-created: Each Dataset MUST have one and only one created date, an xsd:date, xsd:dateTime or xsd:dateTimeStamp value, indicated using the dcterms:created property

D-modified: Each Dataset MUST have one and only one modified date, an xsd:date, xsd:dateTime or xsd:dateTimeStamp value, indicated using the dcterms:modified property

D-creator: Each Dataset MUST indicate one or more creator agents with the dcterms:publisher property, typed as an sdo:Person, sdo:Organization or sdo:GovernmentOrganization

D-publisher: Each Dataset MUST indicate at least one publisher agent with the dcterms:publisher property, typed as an sdo:Organization or sdo:GovernmentOrganization, that is registered by the AGLDWG within their Organisations register

D-pbundle: Each Dataset MUST indicate that it is within a prof:Bundle by an instance of one being indicated with the prov:asInBundle property

D-derived: If a Dataset is derived from anotehr Dataset, it SHOULD indicate that that other dataset, a general DCAT Dataset instnace, with a prov:wasDerivedFrom property

2.2 Feature Collection

Loc-I matches the OGC API^ref specification's method of arranging multiple Feature instances within a Dataset by grouping them into FeatureCollection. FeatureCollection instances are not spatial object themselves but are administrative (managed) collection (of Feature instances). They just require basic metadata, no spatial properties.

FC-title: Each Feature Collection MUST have one and only one English title which is an English text literal, indicated using the skos:prefLabel property

FC-defn: Each Feature Collection MUST have one and only one English definition which is an English text literal, indicated using the skos:definition property

FC-id: Each Feature Collection MUST have one and only one identifier, an xsd:token, indicated using the dcterms:identifier property. Note: this identifier must be unique within the Dataset it is part of. This uniqueness is not testable in SHACL.

FC-part: Each Feature Collection MUST indicate that it is part of one and only one dcat:Dataset with use of the dcterms:isPartOf property

2.3 Feature

Features are the code things within Loc-I data. The are the spatial objects we care about and to which properties of interest are attached. Loc-I requirements for Feature isntances are that they have geometries - without which they can't be used as spatial objects - and are part of FeatureCollection instances. Each Feature instance must have an ID that is unique within a FeatureCollection so it can be used by systems taht cannot handle IRIs, such as OGC APIs, to refer to individuals.

F-part: Each Feature MUST indicate that it is part of at least geo:FeatureCollection with use of the dcterms:isPartOf property

FC-id: Each Feature MUST have one and only one identifier, an xsd:token, indicated using the dcterms:identifier property. Note: this identifier must be unique within a Feature Collection. This uniqueness is not testable in SHACL

FC-geometry: Each Feature Collection MUST have at least one geometry indicated using the geo:hasGeometry property

2.4 Linkset

Loc-I Dataset instances may be joined by Linkset instances. A Linkset is a specialised form of a Dataset specifically created to join other Dataset instances and, as a result, has some mandatory properties to ensure joining is correctly specified.

Note that because Linkset instances are also Dataset instances, all the Dataset rule apply to Linkset instances in addition to thiese specialised requirements.

L-m: Each Linkset MUST indicate at least one rdf:Statement by an inverse linking from that instance to the Linkset via the dcterms:isPartOf property

L-st: Each Linkset MUST indicate one an only one subjects target Dataset with the property void:subjectsTarget

L-ot: Each Linkset MUST indicate one an only one objects target Dataset with the property void:objectsTarget

2.5 Statement

The graph elements within Linkset instances that indicate Feature-level links between Dataset instances are Statement instances which are specialised forms of the standard rdf:Statement class.

LS-subject: Each Statement MUST indicate one an only one subject with the propertyrdf:subject

LS-predicate: Each Statement MUST indicate one an only one predicate with the propertyrdf:predicate

LS-object: Each Statement MUST indicate one an only one object with the propertyrdf:object

L-part: Each Statement MUST indicate that it is part of one and only onevoid:Linkset with use of thedcterms:isPartOf property

LS-method: Each Statement MUST indicate that it was generated by one and only one method (aprov:Plan) with use of theloci:hadGenerationMethod property

2.6 Bundle

Provenance for Loc-I datasets must be recorded using PROV-O, the Provenance Ontology^ref. The provenance statements are collected in prov:Bundle objects. EAch Bundle instance must include certain elements that allow users to understand how the Dataset that the Bundle is for was produced.

B-mainactivity: Each Bundle MUST contain at least one prov:Activity indicated by a dcterms:hasPart property which must, in turn, indicate at least one prov:Entity by use of prov:generated