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

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

From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
Date: Wed, 06 Mar 2019 22:54:37 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-470310437-1551912876-sysbot+gh@w3.org>
@tombaker - yes thats what i am saying - we could introduce a prof:Artifact class.   constraints that apply to a set of things are on the class - SHACL which i'm more familiar allows you to declare a shape on an individual, but thats not relevant as we are talking about axiomitising constraints on cardinality of a property for the set of instances.

The issue here is more that DCAT has chosen a pattern where properties of a proxy for an artifact (i.e. a dcat:Distribution) are declared to relate to that artifact, and since cataloguing of profiles is an important use case we have followed that pattern. so the question is now we have something to lose by not following the DCAT approach, do we have anything significant to gain by adding an Artifact class - given as @kcoyle says earlier "The assumption would be that if the artifact needs to be described, that would take place elsewhere in the "universal graph"  - i.e. by not including an Artifact class we dont lose anything, but by having the explicit statement that the same properties of a ProfileResource that DCAT uses for a Distribution have the same meaning, we allow cataloguing using prof without further entailment. This why i am now leaning towards making Profile a subclass of dcat:Resource, not this abstract class exists, and ProfileResource a subclass of dcat:Distribution. (this is currently in a separate alignment ontology)

@kcoyle the answer to the question is yes - they are both valid and neither is preferred - having separate ProfileResource would allow you to attach comments and annotations specific to the role, otherwise they are the same - maybe more interesting is whether role can be missing at all.



-- 
GitHub Notification of comment by rob-metalinkage
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/769#issuecomment-470310437 using your GitHub account
Received on Wednesday, 6 March 2019 22:54:38 UTC

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