Closed andrea-perego closed 2 years ago
@dr-shorthair , the URIs from the CSIRO registry, starting with http://registry.it.csiro.au/, seem to be broken.
Should we replace them with other ones?
Indeed. registry.it.csiro.au was decommissioned about 6 months ago. Some of the content has been rehoused in https://vocabs.ardc.edu.au/ We could add more there if it would be useful for DCAT.
However, for DataCite and Re3Data it would be best to source them direct, of possible.
Indeed. registry.it.csiro.au was decommissioned about 6 months ago. Some of the content has been rehoused in https://vocabs.ardc.edu.au/ We could add more there if it would be useful for DCAT.
However, for DataCite and Re3Data it would be best to source them direct, of possible.
Thanks, @dr-shorthair . About DataCite and Re3data, as far as I know they have no HTML and/or RDF representation but only an XML schema + PDF. So, we don't have URIs to be used.
I checked the occurrences of URIs starting with http://registry.it.csiro.au/ , and I tried to find the corresponding ones from https://vocabs.ardc.edu.au/ . The result is the following:
Could you please indicate which URIs should be used for the missing ones? Also, it seems that some of the URIs use http://
(ISO 19115-1) and other ones https://
(DataCite). Which ones should be used?
BTW, strange that the URI of the DataCite resource type code list is
https://linked.data.gov.au/def/resource-types
Looking at those used for ISO 19115-1, I would have expected something like
@agbeltran , @davebrowning , @dr-shorthair , @pwin , @riccardoAlbertoni ,
I suggest we review and merge this PR. I'll create a separate issue for the URIs from http://registry.it.csiro.au/
Lack of stable normative ISO concepts with canonical URI dereferencing behaviours is a major barrier when they form an important part of the legal and/or organisational interoperability layer(s).
Is an antipattern to cite these sort of workarounds unfortunately. Whilst I have been exploring some concepts around proxy patterns not in a situation where it could help here, its more of a local implementation choice supported by the PROF vocab,
This PR includes proposed revisions to address https://github.com/w3c/dxwg/issues/1349 , plus editorial fixes.
Preview:
https://raw.githack.com/w3c/dxwg/dcat-issue-1349/dcat/index.html
Diff:
https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fw3c.github.io%2Fdxwg%2Fdcat%2F&doc2=https%3A%2F%2Fraw.githack.com%2Fw3c%2Fdxwg%2Fdcat-issue-1349%2Fdcat%2Findex.html
Summary of changes to the specification:
dcat:Catalog
in §5.1 DCAT scope to make it explicit that the scope of a catalog is not limited to datasets and data services - commit https://github.com/w3c/dxwg/pull/1510/commits/1f50cb076dd6f53a6b3ec7f742536263067218f3dcterms:source
(object property) - commit https://github.com/w3c/dxwg/pull/1510/commits/ae3056defaa8a979df56a867acc3f5f23b9044d3Other changes:
config.js
- commit https://github.com/w3c/dxwg/pull/1510/commits/250ae80995219d9c94b49f829d3dc70f151b3a54README.md
- commit https://github.com/w3c/dxwg/pull/1510/commits/4a6ff3725fa60d7b3cd62d9320a43bd0d33e5574To do: