This is a profile, that is a multi-part standard that constrains the use of other standards.
Formally, by 'profile', what is meant here is "A specification that constrains, extends, combines, or provides guidance or explanation about the usage of other specifications." (from PROF) and, here the 'other specifications' are DCAT2, VoID etc. or, more correctly, intermediate profiles of them.
This profile presents a specification of constraints on the use of classes from the DCAT2, GeoSPARQL, PROV-O, VoID and RDF ontologies, namely dcat:Dataset, geo:FeatureCollection, geo:Feature, prov:Bundle, void:Linkset & rdf:Statement. These constraints are designed to ensure that use of these classes results in data that allows for Location Index (Loc-I)-style use of that data. In short: the classes ust have certain properties associating them with one another and providing elements needed by APIs.
Alonsgide the specification, this profile provides a series of validator resources (Shapes Constraint Language (SHACL) files) which can be used to validate that instances data is valid according to the specification.
This profile is formulated according to the Profiles Vocabulary (PROF) and the persistent URI for this profile, see next, provides access to the PROF formal definition in both HTML & RDF.
This profile's persistent URI:
This profile's normative rules are presented in a Specification document that identifies and states the various constraints that this profile places on a classes such as DCAT's Dataset. This Specification document is an HTML web page that can be read here:
RDF data can be validated against this profile's rules, as identified and defined in Specification document, by use of a series of SHACL validators, which are files within this repository's validators/ folder.
These validators have their own URIs too: see their listing in the profile declaration at https://linked.data.gov.au/def/loci-dp.
Tools such as pySHACL and the online SHACL Playground can be used with these validators to apply them to data.
Examples of valid and invalid data for each DCAT, VoID etc. class as needed by Loc-I systems are also presented as formal parts of this profile. See the examples/ folder in this repository.
There are several ways to use the resources in this profile.
- Read the specification to understand the requirements of data
- the Specification document in this profile is online at https://linked.data.gov.au/def/loci-dp/spec (and also the file in this repository specification.html)
- it states the normative requirements of Loc-I data, per class, in English
- Validate data
- the 6 validators for this profile - one per Loc-I Ontology main class - are presented as SHACL files in this repository. Use a tool like pySHACL to apply a validator to instance data and check its validity
The contents of this repository are licensed using the CC BY 4.0 licence. See the LICENSE file for the deed.
Note Citation below for attribution.
This profile is implemented by SURROUND Australia to allow for data validation within the Loc-I Project which is managed by CSIRO and Geoscience Australia .
To cite this profile, please use the following (formulated in BibTex):
@software{loci-dataset-profile,
author = {{SURROUND Australia Pty Ltd}},
publisher = {{Geoscience Australia}},
title = {{Loc-I Data Profile}},
version = {1.0},
date = {2021},
publisher = {{SURROUND Australia Pty Ltd}},
url = {https://linked.data.gov.au/def/loci-dp}
}
publisher:
SURROUND Australia Pty. Ltd.
https://surroundaustralia.com
creator:
Dr Nicholas J. Car
Data Systems Architect
SURROUND Australia Pty. Ltd.
[email protected]
https://orcid.org/0000-0002-8742-7730