PR Request for Data Catalog Vocabulary (DCAT), Version 3 - VOCAB-DCAT-3
pchampin opened this issue · 3 comments
Document title, URLs, estimated publication date
Title: Data Catalog Vocabulary (DCAT) - Version 3
URL: https://w3c.github.io/dxwg/dcat/publication-snapshots/PR/Overview.html
Estimated publication date: 2024-06-06
Abstract
https://w3c.github.io/dxwg/dcat/publication-snapshots/PR/Overview.html#abstract
Status
https://w3c.github.io/dxwg/dcat/publication-snapshots/PR/Overview.html#sotd
Will new features be allowed to be incorporated in the Recommendation?
no
Link to group's decision to request transition
https://www.w3.org/2002/09/wbs/99375/dcat-3-to-pr/results
Changes
https://w3c.github.io/dxwg/dcat/publication-snapshots/PR/Overview.html#changes
Requirements satisfied
yes
Dependencies met (or not)
none
Wide Review
w3c/dxwg#1502
(see also a summary of the coordination with all groups listed in the charter)
Issues addressed
All pending issues were addressed: https://github.com/w3c/dxwg/issues?q=is%3Aissue+is%3Aopen+label%3Adcat+-label%3Afuture-work
The remaining open issues do not impact the recommendation itself:
- 1352 concerns (non-substantive) additions to the companion RDF files
- 1233 concerns the referencing of DCAT in specref
Formal Objections
none
Implementation
https://w3c.github.io/dxwg/dcat3-implementation-report/
Patent disclosures
We noticed you use https://pav-ontology.github.io/pav/, which hasn't changed for 9 years. It's not clear what is the stability of this URL . There is http://purl.org/pav/2.3/html but it isn't served properly. It would be nice if this can be looked into, but this is not blocking.
We noted some properties (dcat:previousVersion, dcat:hasCurrentVersion) were used by only one vocabulary but their usage seems straighforward.
Transition approved.
It would be nice if this can be looked into, but this is not blocking.
I looked into it. http://purl.org/pav/2.3/html redirects to https://cdn.jsdelivr.net/gh/pav-ontology/pav@2.3.1/pav.html, which in turns relies on github (I doubt that they persistently cache it). So in the end, the stability of all these URLs (including the currently used https://pav-ontology.github.io/pav/) depends on github continuing to serve them.
http://purl.org/pav/2.3/html would still be a better choice than the "evergreen" https://pav-ontology.github.io/pav/, but again, I suspect that JsDeliver serving HTML files as text/plain rather than text/html is a feature rather than a bug, because it guesses many other content types correctly.
I raised an issue but I'm not holding my breath for a response...
Closing, as the Proposed Recommendation has been published: pav-ontology/pav#11