- From: aisaac via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 Sep 2019 15:27:18 +0000
- To: public-dxwg-wg@w3.org
The proposal to change ResourceDescriptor to ProfileDistribution is tempting, but... I have done a long study of this and related stuff as part of trying to align our different conceptualization (for this issue and #529): https://docs.google.com/document/d/1uUl8ztXMctnsYTkTH_jV1bA27kqezdHtFRYva18Wsy0/ The relevant part here is "Profile "resource descriptors"/descriptions/specifications/expressions and their encodings/artifacts" especially in "ResourceDescriptor + hasResource" Since then, the wording of the various PROF elements may have change, but I believe the PROF pattern is still the same. And in that pattern, there is still an issue with aligning to dcat:Distribution, as has been noted here before. Essentially, if dcat:Distributions are serialization and address-specific, then they fit rather the "artefact" level in PROF. And I certainly DON'T want that one can say that the objects of the prof:hasArtefact statements are (DCAT) distributions of a (DCAT) distribution!!! This is why in the end I prefered `ProfileSpecification` and (even more) `ProfileExpression` as alternatives to `ResourceDescriptor` (and around the Lyon F2F we have also hinted `ProfileComponents` and `ProfileManifestations`) There is however something that I may have misunderstood about DCAT's Distributions: maybe they are not location-specific? I.e. if a `dcat:Distribution` can have several `dcat:accessURL` or `dcat:downloadURL` then the distributions are a bit more conceptual than what I originally thought, and we can use ProfileDistribution for ResourceRole. But I'm still skeptical, as I read that DCAT's distributions are serialization specific. To me a same ResourceDescriptor in PROF can be available both as a JSON-LD and an RDF/XML artefact representing the same set of RDF statements, and I'm really not sure this fits with DCAT's view on Distribution. I.e. I understand a dcat:Distribution can be in JSON-LD or in RDF/XML but not both. -- GitHub Notification of comment by aisaac Please view or discuss this issue at https://github.com/w3c/dxwg/issues/573#issuecomment-531828530 using your GitHub account
Received on Monday, 16 September 2019 15:27:19 UTC