Skip to content
This repository was archived by the owner on Jul 16, 2024. It is now read-only.

Latest commit

 

History

History
62 lines (31 loc) · 4.03 KB

specification.md

File metadata and controls

62 lines (31 loc) · 4.03 KB

OGC LD API Specification

This document specifies the rules that RDF data must adhere to, to be valid according to this profile and thus fit for use with instances of the OGC LD API tool.

This document's persistent identifier is:

Role

This document is part of the larger OGCLDAPI Profile which contains multiple parts: this specification, validators and so on. The profile is online at:

This document does not profile rules that can be used to validate data. For resources fullfilling that role, see the list of resources in the profile (link above). The validator resources in this profile quote the written rules specificed here in their operations.

Requirements

The requirements specified by this specification are listed here. The correspond to machine-executable RDF validation tests supplied by this profile in the Shapes Constraint Language (SHACL).

This specification places requirements on three OWL classes from two well known ontologies:

DCAT is identified by the dcat prefix and GeoSPARQL by the geo prefix.

For dcat:Dataset

  • Requirement D-title**: Each Dataset MUST have one and only one English title which is an English text literal, indicated using the dcterms:title predicate

  • Requirement D-desc: Each Dataset MUST have one and only one English description which is an English text literal, indicated using the dcterms:description predicate

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

  • Requirement D-member: If a Dataset has a member, indicated by rdfs:member, that member MUST be of type geo:FeatureCollection

  • Requirement D-bb: A Dataset MAY indicate a Bounding Box geometry with a geo:boundingBox predicate

For geo:FeatureCollection

  • Requirement FC-title: Each Feature Collection MUST have one and only one English title which is an English text literal, indicated using the dcterms:title predicate

  • Requirement FC-desc: Each Feature Collection MUST have one and only one English description which is an English text literal, indicated using the dcterms:description predicate

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

  • Requirement FC-memberof: Each Feature Collection MUST indicate that it is a member of one and only one dcat:Dataset with use of the rdfs:member predicate (with the Dataset as the object and Feature Collection as the object).

  • Requirement FC-member: If a Feature Collection has a member(s), indicated by rdfs:member, that member MUST be of type geo:Feature

  • Requirement FC-bb: A Feature Collection MAY indicate a Bounding Box geometry with a geo:boundingBox predicate

For geo:Feature

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

  • Requirement F-memberof: Each Feature MUST indicate that it is a member of at least one geo:FeatureCollection with use of the rdfs:member predicate (with the Feature Collection as the object and Feature as the object).

  • Requirement F-geometry: Each Feature MUST indicate that it has at least one geo:Geometry with use of the geo:hasGeometry predicate