Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comments on "inheritance" #795

Open
kcoyle opened this issue Mar 6, 2019 · 3 comments
Open

Comments on "inheritance" #795

kcoyle opened this issue Mar 6, 2019 · 3 comments

Comments

@kcoyle
Copy link
Contributor

kcoyle commented Mar 6, 2019

From the ShEx community:

We were unsure what to make of "inheritance", as we are not aware of any generalized notion of inheritance that would make sense across implementation technologies. It would be helpful to motivate this with a testable use case, e.g., a server implementation which responds to Accept-Profile by calculating the "best" response for processing a Profile Ontology description. A test of inheritance would include the notion that inheriting imposes further constraints, and that the entity being inherited from may in turn inherit from something else. ShEx shape inheritance has this behavior.

https://lists.w3.org/Archives/Public/public-dxwg-comments/2019Feb/0001.html

@kcoyle kcoyle added profile-guidance profiles-vocabulary For discussion of profile description vocabulary feedback Issues stemming from external feedback to the WG labels Mar 6, 2019
@rob-metalinkage
Copy link
Contributor

This is implicit in the definition, and the improved wording for the defintions and usage notes will help, but it needs to brought out more explicitly since the notion seems so hard to grasp - transitive inheritance via isProfileOf is the key machine readable axiom. This is to be addressed via #732

@kcoyle
Copy link
Contributor Author

kcoyle commented Mar 13, 2019

@rob-metalinkage You probably will need to explain what you mean by "transitive inheritance" as that may not be in everyone's vocabulary. We've also talked in many other issues about defining explicitly what inheritance means in terms of axioms. Nick did an example at one point, but if we expect it to be actionable then some precise algorithms are going to be needed.

@nicholascar
Copy link
Contributor

"transitive inheritance" is now demonstrated in the PROF ED in examples and also in a long note after the prof:isTransitiveProfileOf property.

The axiom dct:conformsTo owl:propertyChainAxiom ( prof:isProfileOf dct:conformsTo ) also now present in the ontology defines the entailments that can be made with prof:isProfileOf and, since no equivalent axiom is declared for prof:isTransitiveProfileOf, it is clear how the usage of the properties differs.

Regarding the sentence:

It would be helpful to motivate this with a testable use case, e.g., a server implementation which responds to Accept-Profile by calculating the "best" response for processing a Profile Ontology description.

This is a matter for ConnegP and notes on "best" responses, or at least how responses from hierarchies are calculated, are given in the ED of that document.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feedback Issues stemming from external feedback to the WG prof-due-for-closing profile-guidance profiles-vocabulary For discussion of profile description vocabulary profneg-due-for-closing
Development

No branches or pull requests

4 participants