Version

auto-generated from model/.php via pre-commit hook*

Version

A Databus Version is one specific version of a Databus artifact (artifacts = version-independent, abstract datasets).

Please note that the fuzzy word dataset is disambiguated on the Databus, as it could mean:

  1. artifact (see here): the abstract concept of a dataset (e.g. the DBpedia Label dataset, https://databus.dbpedia.org/dbpedia/generic/labels/).

  2. version (this page, see below): a specific version of a dataset (e.g. DBpedia Label dataset of Sep 1st, 2022, https://databus.dbpedia.org/dbpedia/generic/labels/2022.09.01).

  3. distribution (see here): the bag of files of a specific version (e.g. the download location: https://downloads.dbpedia.org/repo/dbpedia/generic/labels/2022.09.01/)

Example (JSON-LD):

{	
	"@id": "https://databus.dbpedia.org/janni/onto_dep_projectx/dbpedia-ontology/2021-12-06",
	"@type": "databus:Version",
}

Spec (OWL, SHACL, JSON-LD Context)

databus:Version  a owl:Class ;
    rdfs:label "Version"@en ;
    rdfs:comment "Dataset Version"@en ; 
    rdfs:subClassOf dcat:Dataset , dataid:Dataset ;
    rdfs:isDefinedBy <https://dataid.dbpedia.org/databus#> .

1. General Metadata

title

A name given to the resource.

Example (JSON-LD):

Spec (OWL, SHACL, JSON-LD Context)

abstract

TODO autogenerated from the first 200 chars of description.

Example (JSON-LD):

Spec (OWL, SHACL, JSON-LD Context)

description

Markdown allowed. The first 200 chars will be used as an abstract.

Example (JSON-LD):

Spec (OWL, SHACL, JSON-LD Context)

publisher

The agent, person or organisation responsible for publishing this Databus version's metadata (not the files itself)

Example (JSON-LD):

Spec (OWL, SHACL, JSON-LD Context)

2. Legal, Provenance & Attribution

Three main features are included in the model:

  • Automation of licensing. To describe datasets a license URIs is required. In most cases these URIs provide a human-only HTML description. License URIs from our affiliate project DALICC are machine-actionable and machines can compare licenses and check for compatibility and obligations in an automated manner.

  • Provenance chains. Once datasets are registered with any Databus, provenance relations can be added to the graph and link to the source data the current version was Derived From. Combined with licenses, this enables to track back input sources and dependencies and transitively accumulate all licensing information.

  • Attribution. Most dataset metadata originally comes from unstructured, non-machine readable places such as HTML Websites. This attribution information needs to be captured initially on the Databus, whenever data metadata is first lifted into the Databus model.

Note: Entered metadata is signed with the users private key or on behalt of the user by the Databus to avoid tempering with this information (see proof). This is an extra measure to secure against falsification of the legal implications of the metadata.

license

  • Usage of DALICC License URIs is highly recommended (library).

  • License is set at the databus:Version node, but is always valid for all distributions, which is also reflected by signing the tractate.

  • context.jsonld contains "@context":{"@base": null }, to prevent creating local IRIs.

Example (JSON-LD):

Spec (OWL, SHACL, JSON-LD Context)

wasDerivedFrom

Imports the Provenance Ontology. Linking should be done between Dataset versions.

Example (JSON-LD):

Spec (OWL, SHACL, JSON-LD Context)

attribution

Capturing information about attribution serves these purposes:

  • enable citations in academic context

  • fulfill license obligations such as CC-BY. Note that most open licenses only grant you the specified freedoms, if you properly fulfill the obligations such as attribution.

The field attribution is:

  • optional (can be omitted)

  • multi-valued (can have more than one entry, e.g. one for attributing the paper, one for attributing the publishing organisation)

  • multi-type (can have variety of different formats, which are listed below)

Publication Link

??

Bibtex

Markdown

title, attribution, license

© Copyright

© Intergovernmental Panel on Climate Change 2014

Example (JSON-LD):

Spec (OWL, SHACL, JSON-LD Context)

3. Structural Metadata

group, artifact, version, hasVersion are the main properties used to structure all entries on the Databus for querying and retrieval. The most basic query here is to retrieve the latest version for each artifact in some group or to check, whether there is a new version available for one artifact.

group

Example (JSON-LD):

Spec (OWL, SHACL, JSON-LD Context)

artifact

autogenerated... Example (JSON-LD):

Spec (OWL, SHACL, JSON-LD Context)

hasVersion

Note: see section versioning above.

Example (JSON-LD):

Spec (OWL, SHACL, JSON-LD Context)

distribution

Example (JSON-LD):

Spec (OWL, SHACL, JSON-LD Context)

4. Other Metadata

issued

Date of formal issuance of the resource using xsd:dateTime.

Example (JSON-LD):

Spec (OWL, SHACL, JSON-LD Context)

modified

Note: dct:modified is always set by the Databus on post.

Example (JSON-LD):

Spec (OWL, SHACL, JSON-LD Context)

Example (JSON-LD):

Spec (OWL, SHACL, JSON-LD Context)

PreviousArtifactNextDistribution

Last updated