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

Re: [dxwg] prof:inheritedFrom needs more convincing case and/or example (#642)

From: kcoyle via GitHub <sysbot+gh@w3.org>
Date: Thu, 31 Jan 2019 03:02:28 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-459197021-1548903747-sysbot+gh@w3.org>
"ex2:" doesn't clarify the meaning or functionality of this property for me. I'll name a few things, just to get a discussion started:

In this example, there are multiple profiles that each have only a single resource type: a SHACL file. Nothing is said about the case where:

profileX has the following resources:
- a PDF document
- a SHACL document in JSON-LD

profileY has the following resources:
- a Word document
- A ShEx document in ttl

And there is a triple that states:
     profileY prof:inheritedFrom profileX</pre>
  What is an application supposed to do with these?

  profileX has this resource:
- a SHACL document

profileY has this resource:
- another SHACL document
  profileY prof:inheritedFrom profileX</pre>

  There are now 2 SHACL files. 

- One may be entirely different from the other (AAA); 
- one may contain SHACL statements that are also in the other, but are the same; 
- one may contain SHACL statements that are also in the other but that give conflicting (or at least different) rules. 
What is the required action on the application processing these for each of these cases?

ProfileX has properties A, B, C, G (let's say in a SHACL document)
ProfileY has properties A, B, C, D (ditto)

What are the outcomes from these two statements:
ProfileX prof:inheritedFrom ProfileY .
ProfileY prof:inheritedFrom ProfileX .

*If* the answers to any of these are: You shouldn't do that! then there needs to be a description in the ontology that explains what is and is not "valid" when using prof:inheritedFrom.

GitHub Notification of comment by kcoyle
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/642#issuecomment-459197021 using your GitHub account
Received on Thursday, 31 January 2019 03:02:29 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 April 2019 13:45:06 UTC