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

Re: [dxwg] Formally align PROF to DCAT (#808)

From: aisaac via GitHub <sysbot+gh@w3.org>
Date: Mon, 09 Sep 2019 08:06:02 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-529347594-1568016361-sysbot+gh@w3.org>
Actually I do have one comment about the alignment, as I'm looking at conformance discussions again...
The sentence that @kcoyle noted raises a big issue for me, as it seems that much more could be said to align with DCAT, rather than to differentiate from it, and this could be useful for all the discussions around PROF and conformance...

My starting point is that DCAT actually says quite a lot about conformance:
- https://www.w3.org/TR/vocab-dcat-2/#Property:resource_conforms_to
- https://www.w3.org/TR/vocab-dcat-2/#conformance
- https://www.w3.org/TR/vocab-dcat-2/#quality-conformance
The latter two are not acknowledge in the current PROF section on DCAT alignment (unless it was meant as an hyperlink for a "here" at the end of the section, that doesn't link to anything)

So the story should be imo:
1. DCAT expresses view on conformance of data with specifications, which follows DCMI's one (arguably vague but workable), and that PROF adheres to
2. In addition, PROF provides the mean to represent relations between specifications, which can be used to handle case of conformance across different levels of profiles (and let's not be more specific than this: we don't need to, for this section, so let's keep a minimal editorial commitment and refer to other sections where more details are given, on what happens on conformance and isProfileOf).
It shouldn't be the other way round, and not a way that minimizes the issue of conformance of instance data with specifications/standards, which is core to PROF too.

-- 
GitHub Notification of comment by aisaac
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/808#issuecomment-529347594 using your GitHub account
Received on Monday, 9 September 2019 08:06:03 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 October 2019 00:15:57 UTC