Data Provider Register ontology
Switch branches/tags
Nothing to show
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


This Data Provider Register ontology is loosely a registry-based version of the Data Provider Node ontology.

It's purpose is to provide a single, Linked Data, entry point from which an organisation's various catalogues of web content can be found in defined ways. It is DCAT Ontology and PROV Ontology-centric in design given that it focusses on datasets catalogued online, their distributions and agents.

It specifies a top-level Registry Ontology register, the Data Provider Register, which is composed of subregisters for dcat:Dataset, prov:Agent and dcat:Distribution class object. The DPR register must at least define a dcat:Dataset register.

The DPR register's subregisters may not actually function via Linked Data principles but must indicate if they do or not. This is to allow the definition of DPR instances that contain legacy 'registers', things like dataset catalogues.

Example Instances

Minimal Example Diagram: This diagram shows the most minimal legal set of classes that much be defined for an instance of the DPR:

Geoscience Australia: dpr_ga.ttl is an RDF document containng an absolute minimal implementation of the DPR-O for the organisation Geoscience Australia. It has the DPR register defined with the compulsory subregister for dcat:Dataset objects given. In this instance, the dcat:dataset subregister cannot function as a Linked Data register as it is a legacy dataset catalogue; a GeoNetworks system. shows the contents of dpr_ga.ttl in diagram form.

Nicholas Car