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

Remove OWL cardinality restrictions #216

Closed
dr-shorthair opened this issue Mar 21, 2024 · 3 comments
Closed

Remove OWL cardinality restrictions #216

dr-shorthair opened this issue Mar 21, 2024 · 3 comments
Assignees
Labels
OWL issues around consistency, entailments etc SHACL

Comments

@dr-shorthair
Copy link
Collaborator

  1. take the Ontology outside DL
  2. raises various problems ...
    SAREF-SOSA alignment and first approx doc, closes #125 #206 (comment)
    107 Add SystemKind class and its subclasses #209 (comment)

probably more.

Mostly I added them where I though they made sense, but cardinalities are probably better managed at the application level using SHACL, rather in the Ontology layer where they affect reasoning and can cause difficult-to-control inconsistencies.

@dr-shorthair dr-shorthair added OWL issues around consistency, entailments etc SHACL labels Mar 21, 2024
@ldesousa
Copy link
Contributor

I would like to follow on the comment by @rgcmme. Constraints modelled alone at application level (e.g. with SHACL) would inevitably lead to misinterpretations of the ontology.

An example I am currently dealing with is the relation between Observation and Procedure. Can/should an observation refer to more than one procedure? In OMS the restriction is set by the class diagram itself, wheres in SOSA/SSN the sosa:usedProcedure object property has no cardinality indication. Therefore a SOSA observation with two different procedures is valid, whereas it is not so in OMS/STA.

I don't have the experience with reasoning to sense the troubles cardinalities could imply. Therefore I admit those difficulties to eventually prevent their specification, but in that case I would prefer to have them absent altogether.

@oldskeptic
Copy link
Contributor

I would suggest leaving cardinality restrictions in SOSA. They are unlikely to break things on the reasoner side and if that's the SOSA design, that's what the ontology should say.

OWL and SHACL tend to draw different people but this level of restriction isn't problematic IMHO.

@dr-shorthair
Copy link
Collaborator Author

I have found it necessary to remind people that OWL cardinality restrictions are not validation constraints.
The OWA still seems to be a step too far for some smart users.

AFAICT the one that really matters crossing over from OWA to CWA is where cardinality=1 - that means that if there is more than one, then either they are identical or there is an inconsistency.

But I will close this issue now as no-one else wants to deprecate cardinalities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OWL issues around consistency, entailments etc SHACL
Projects
None yet
Development

No branches or pull requests

6 participants