W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > March 2019

Re: [dxwg] Are PROF roles misplaced in resourceDescription? (#769)

From: kcoyle via GitHub <sysbot+gh@w3.org>
Date: Mon, 04 Mar 2019 15:11:27 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-469287460-1551712286-sysbot+gh@w3.org>
Rob, I think we are talking past each other, but am not sure I can fix that. Can you go back to the examples I gave [above](https://github.com/w3c/dxwg/issues/769#issuecomment-465613776) and answer the questions I asked there? They have to do with artifacts with multiple roles. That's followed by another example. That's a very practical question which might help. Again, I suggest working with examples.

Again, puzzling: " we dont have to resolve artefact URIs to find these properties in general." There is no need to resolve the URIs in the model I give any more than in the current one. It's just another node in a graph. It's the fairly minor difference between
![descriptor1](https://user-images.githubusercontent.com/1564129/53740997-47865a00-3e4a-11e9-829a-d38ff532681f.jpg)
and
![descriptor](https://user-images.githubusercontent.com/1564129/53741014-510fc200-3e4a-11e9-8759-9b31d1e22c9d.jpg)
It's a question of associating the information about the artifact (which is a file on the web) with the artifact. If there is no artifact, those properties would not exist. I also think that this illustrates the idea of the "record" (upper picture) with that of graphs (lower). Records act as proxies while graphs describe things and relationships. In the second diagram, the resource descriptor describes the content of the resource and its role (also title, etc.), while the artifact graph describes the physical artifact. The content and the artifact are different things and each has properties that describe it.

Also: "declare a new class of things "Artefact" " Classes are not required in RDF and are not required in the examples I gave. You can have a graph that is not defined by a class. Remember, in RDF properties define classes, not classes define properties. Although the DCAT diagrams show boxes with classes and properties, a large number of the properties are in reality not associated with the class (they have no domain declaration to that class). The only thing that will associate those properties to that "thing" is a validation language. In RDF classes are semantic rather than structural.

-- 
GitHub Notification of comment by kcoyle
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/769#issuecomment-469287460 using your GitHub account
Received on Monday, 4 March 2019 15:11:29 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 14 March 2019 16:33:09 UTC