Closed riccardoAlbertoni closed 1 year ago
Hello! Thanks for your review request, and it's nice to see the progress on DCAT.
It would be really helpful for us if the explainer could go into a bit of detail about the "more pressing use cases and requests among those left unaddressed in the previous standardization round" that version 3 is addressing. It would help us to understand if/how you've accomplished what you set out to do with DCAT 3.0.
We also try to join up work across working groups and W3C specs. We see that you've created new terms (such as dcat:first, dcat:prev and dcat:last) which could instead be covered by something like RDF lists — could you tell us why you made that choice? Are there any other opportunities to reuse existing work in DCAT 3.0?
DXWG replies are tracked by https://github.com/w3c/dxwg/issues/1530
DXWG replies are tracked by w3c/dxwg#1530
Hi @rhiaro, @danbri and @hadleybeeman, Can you live with the explanations supplied in w3c/dxwg#1530?
If there is nothing else to clarify, please let us know when we can consider the review from TAG concluded.
Thanks a lot.
Hi @riccardoAlbertoni, sorry for the delay in following up. We are satisfied with your responses, and are happy to conclude this review. Thanks!
Wotcher TAG!
I'm requesting a TAG review of Data Catalog Vocabulary (DCAT) - Version 3.
DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web.
DCAT enables a publisher to describe datasets and data services in a catalog using a standard model and vocabulary that facilitates the consumption and aggregation of metadata from multiple catalogs. This can increase the discoverability of datasets and data services. It also makes it possible to have a decentralized approach to publishing data catalogs and makes federated search for datasets across catalogs in multiple sites possible using the same query mechanism and structure. Aggregated DCAT metadata can serve as a manifest file as part of the digital preservation process.
Further details:
We'd prefer the TAG to provide feedback as:
☂️ open a single issue in our GitHub repo for the entire review