StefanoDavid (Talk | contribs) (Review has been created. Annotation 'assigned' has been removed.) |
OlafNoppens (Talk | contribs) |
||
Line 6: | Line 6: | ||
}} | }} | ||
{{Logical OP Description Template | {{Logical OP Description Template | ||
− | |Motivation= | + | |Motivation=The motivation of this pattern is to model ''negative property assertions'' (NPAs) in ontology languages such as OWL 1 [1] that do not provide a special constructor for expressing it. It is worth mentioning that not all knowledge base systems can be migrated to OWL 2 [2] for several reasons. On the other hand, NPAs modeled according to this pattern can be migrated to OWL 2 using the newly introduced constructor. |
+ | A negative property assertion as defined in the upcoming OWL 2 states that a given individual ''i'' is never connected to a given individual ''j'' by a given property expression ''P''. In other words, asserting that ''i'' is connected to ''j'' by ''P'' results in an inconsistent ontology. In this sense this assertion can be considered as a constraint that should not be violated. In contrast, considering an ontology where it cannot be inferred that ''i'' is connected to ''j'' by ''P'' does not necessarily mean that there cannot be such a connection - in fact, it is merely not modeled. | ||
− | + | ||
+ | [1] Patel-Schneider, P.F., Hayes, P., Horrocks, I.: OWL Web Ontology Language | ||
+ | Semantics and Abstract Syntax, W3C Recommendation 10 February 2004. | ||
+ | |||
+ | [2] Motik, B., Patel-Schneider, P.F., Parsia, B.: OWL 2 Structural Specification and Functional-Style Syntax. W3C Candidate Recommendation 11 June 2009, 2009. | ||
|Aim=Expressing NPAs in ontologies prior to OWL 2 as well as given an transformation rule when using OWL 2. | |Aim=Expressing NPAs in ontologies prior to OWL 2 as well as given an transformation rule when using OWL 2. | ||
|Solution=NegativeObjectPropertyAssertion(i1 prop i2) is equivalent to: | |Solution=NegativeObjectPropertyAssertion(i1 prop i2) is equivalent to: | ||
Line 21: | Line 26: | ||
{{Logical OP Example Template}} | {{Logical OP Example Template}} | ||
{{Logical OP Reference Template}} | {{Logical OP Reference Template}} | ||
− | + | [[Category:Review assigned]] | |
{{Scenarios about me}} | {{Scenarios about me}} | ||
{{Reviews about me}} | {{Reviews about me}} | ||
Line 27: | Line 32: | ||
|Event=WOP2009:Main | |Event=WOP2009:Main | ||
}} | }} | ||
− | |||
− | |||
− | |||
− | |||
− |
Name | NegativePropertyAssertions |
---|---|
Also known as | |
Author(s) | |
SubmittedBy | OlafNoppens |
Motivation | The motivation of this pattern is to model negative property assertions (NPAs) in ontology languages such as OWL 1 [1] that do not provide a special constructor for expressing it. It is worth mentioning that not all knowledge base systems can be migrated to OWL 2 [2] for several reasons. On the other hand, NPAs modeled according to this pattern can be migrated to OWL 2 using the newly introduced constructor.
A negative property assertion as defined in the upcoming OWL 2 states that a given individual i is never connected to a given individual j by a given property expression P. In other words, asserting that i is connected to j by P results in an inconsistent ontology. In this sense this assertion can be considered as a constraint that should not be violated. In contrast, considering an ontology where it cannot be inferred that i is connected to j by P does not necessarily mean that there cannot be such a connection - in fact, it is merely not modeled.
[2] Motik, B., Patel-Schneider, P.F., Parsia, B.: OWL 2 Structural Specification and Functional-Style Syntax. W3C Candidate Recommendation 11 June 2009, 2009. |
---|---|
Aim | Expressing NPAs in ontologies prior to OWL 2 as well as given an transformation rule when using OWL 2. |
Solution description | NegativeObjectPropertyAssertion(i1 prop i2) is equivalent to:
SubClassOf(ObjectOneOf(i1), ObjectComplementOf(ObjectSomeValuesFrom(prop, ObjectOneOf(i2))))) |
Elements | Individiual i1
Individual i2 ObjectProperty prop |
Implementation | |
Reusable component | |
Component type |
Problem example | |
---|---|
Pattern solution example | |
Consequences |
Origin | |
---|---|
Known use | |
Reference | |
Related ODP | |
Used in combination with | |
Test |
No scenario is added to this Content OP.
This revision (revision ID 5889) takes in account the reviews: none
Other info at evaluation tab
![]() |
Submission to event |
---|