Re: [dxwg] Revision to the versioning section (#1295)

Thank Andrea, for preparing this PR.  I agree on the line of extending the DCAT support taking into account  PAV's equivalent terms and I like the way the versioning is presented.

I report some observations that have crossed my mind reading the draft. I hope they might help the discussion in the next DCAT call.
- I think that the ability to determine the latest/current version is a very fundamental use case when people look for data (what is the latest (official or draft) version released?). Considered this, I wonder if we need to bind more explicitly the semantics of `dcat:currentVersion` and `dcat:lastVersion` to the `dct:replaces` and `dcat:previousVersion` chains. For example, saying " `dcat:lastVersion` is the head of the `dcat:previousVersion` property chain and dcat:currentVersion is the 'head' of the `dct:replaces` chain". That might provide an agreed way to work out the latest version and current version, which might help maintain the metadata consistent and updated. 
- Is `owl:versionInfo` a sub-property of `dcat:version`? Is `owl:priorVersion`  sub-property of `owl:priorVersion`? Or do we want to keep DCAT versioning and OWL versioning as two distinct alternative approaches?  
- Should we align the DCAT versioning with DCAT provenance?  PAV aligns with DCT, and PROV (see [SPRINT on Versioning ](https://github.com/w3c/dxwg/wiki/Material-for-a-SPRINT-on-Versioning) for a summary). If we state the `owl:equivalentProperty` to PAV's terms, that will induce these alignments for the DCAT's, but that is quite an indirect way to have DCAT versioning align with DCT and PROV for versioning. In case we want to keep the alignments provided by PAV for DCT and PROV, I suggest restating them explicitly in DCAT. This could be also the occasion to double-check that these alignments hold and fit well in DCAT. Whether these alignments will be normative or not is another issue that we might need to debate.

-- 
GitHub Notification of comment by riccardoAlbertoni
Please view or discuss this issue at https://github.com/w3c/dxwg/pull/1295#issuecomment-780489178 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 17 February 2021 11:21:06 UTC