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

Re: [dxwg] Create generic properties such as "hasExpression" or "documentedIn" instead of hasResource/(hasRole | hasArtifact) (#747)

From: kcoyle via GitHub <sysbot+gh@w3.org>
Date: Wed, 13 Feb 2019 21:57:45 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-463391484-1550095064-sysbot+gh@w3.org>
Antoine, I'm not wedded to any particular solution, but I'm not sure why extending by subproperties is harder than SKOS B/N. They seem to be similar structurally when declaring across namespaces. Is it as easy to retrieve on SKOS B/N relationships as it is to retrieve of sub-/sup- in SPARQL?  

What I'd like to see is a discussion of USE before we make any decisions - some use cases that actually show use of the roles would be very helpful. I'm assuming that some use would come through the content negotiation, but what use is desired for general searching? We have a requirement that profiles be discoverable, and if we define profiles as not singular things but clusters of resources with different roles, what does that discoverability look like? I'm positing what to me is a likely situation ("find me profiles for bibliographic data that are based on BIBFRAME and have a ShEx validation file", "find me a bibliographic profile, and get me everything that is documentation for that profile"), but I would love to see a bunch of scenarios so we have something concrete on which to make decisions.

-- 
GitHub Notification of comment by kcoyle
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/747#issuecomment-463391484 using your GitHub account
Received on Wednesday, 13 February 2019 21:57:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:13 UTC