-
Notifications
You must be signed in to change notification settings - Fork 34
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
Issue 563: Designate action:Action and core:Event disjoint #564
Conversation
In an OWL-only sense, the ontology portion of this patch could have been accomplished by adding one triple to `action:Action`. For the sake of symmetry and explicitness, `core:Event` also picked up the `owl:disjointWith` statement. To satisfy OWL syntactic requirements, a stub reference to `action:Action` is added, as was done for `types:Dictionary` for Issue 541 (discussed in PR 542). To enforce disjointedness with SHACL, a new independent shape is added, `action:Action-disjointWith-Event-shape`. A follow-on patch will regenerate Make-managed files. EDIT 2023-11-22: An initial version of this patch included an inlined anonymous `sh:NodeShape`. I now believe the scenario that shape mitigates (multi-import of a shapes graph leading to SHACL-scoped syntax errors) is unlikely, and I also saw that the noted rationale around `sh:not` was confused with another predicate (`sh:inversePath`). References: * #563 * #542 Signed-off-by: Alex Nelson <[email protected]>
References: * #563 Signed-off-by: Alex Nelson <[email protected]>
df58570
to
6669aab
Compare
Note: I just force-pushed this branch to revise an incorrect description in the first commit's message. |
This PR is ready for merge. |
Anyone in @ucoProject/maintainers-uco may feel free to merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still a question: why defining an Action as
action:Action
a owl:Class ;
rdfs:isDefinedBy <https://ontology.unifiedcyberontology.org/uco/types> ;
.
in core.ttl??
This is due to Section 5.8.1 of the OWL 2 syntax, specifically the statement "If a class with an IRI I occurs in some axiom in Ax, then I is declared in Ax as a class." Ax in UCO's |
This Pull Request resolves all requirements of Issue #563 .
Coordination
develop
unstable
branch (06e5d9d
)unstable
branch tracking UCO'sunstable
as submodule (b27a539
)