Version release date [RVSDT]

[jpullmann]

Version release date [RVSDT]

It must be possible to assign a date to a version. The version identifier might refer to the release date.

Related requirements: Version definition [RVSDF] Version identifier [RVSID] 
Related use cases: Dataset Versioning Information [ID4] 

[andrea-perego]

If a dataset version is modelled as a dataset, then the version date can be specified with properties already supported in DCAT - (dct:created /) dct:issued / dct:modified.

[dr-shorthair]

There may also be some useful options coming from the proposed PROV-O alignment - see #76 and #94
Any prov:Entity (superclass of dcat:Dataset?) is the result of a prov:Activity which has a start and end time.
And PAV shows how to build a versioning system on top of PROV-O.

[nicholascar]

It's going to be a lot easier in catalogues to indicate properties of the dataset as an Entity, like prov:createdAtTime, than properties of the Activity that generated the Entity. We should make sure future DCAT has PROV-O property chain axioms for all the "normal" dct properties in addition to dct:created/prov:createdAtTime, like dct:modified. PROV-O has no sense of modified as a data property.

[nicholascar]

Re-represented as RDA Prov Patterns WG Use Case 43: http://patterns.promsns.org/usecase/43

[larsgsvensson]

We should make sure future DCAT has PROV-O property chain axioms for all the "normal" dct properties in addition to dct:created/prov:createdAtTime, like dct:modified

Is it really possible to create OWL property chain axioms where the chain ends with a data property? To my knowledge OWL property chain axioms can only chain object properties and the chaining of data properties has to be done with rules. What do the OWL experts say?

[dr-shorthair]

@larsgsvensson - yes, I think you are correct. Unfortunate, but true.