DisjointDataProperties
From OWL Test Cases
The syntactic element DisjointDataProperties belongs to the functional style serialization of OWL 2.
Tests using this feature
This section lists test that are using this feature (refresh view)info.pngQuery results are cached with wiki pages for some time, even if the data changes. This link purges a page's cache to get the most recent results.
There are 4 approved test cases that currently use this feature:| author | description | |
|---|---|---|
| Consistent-dataproperty-disjointness | Birte Glimm | The datatype properties dp1 and dp2 are disjoint, but the individual a can have 10 as a filler for dp1 and 18 as filler for dp2, which satisfies the disjointness. |
| Inconsistent-disjoint-dataproperties | Birte Glimm | The data properties dp1 and dp2 are disjoint, but the individual a must have 10 as dp1 filler and 10 as dp2 filler (since 10 is the only integer satisfying >= 10 and <= 10), which causes the inconsistency. |
| New-Feature-DisjointDataProperties-001 | Mike Smith | Demonstrates use of a disjoint data properties axiom to create a trivial inconsistency based on the example in the Structural Specification and Functional-Style Syntax document. |
| New-Feature-DisjointDataProperties-002 | Mike Smith | Demonstrates use of a ternary disjoint data properties axiom to infer different individuals. Adapted from test New-Feature-DisjointDataProperties-001. |
| author | description | |
|---|---|---|
| Inconsistent-pattern-disjointness | Birte Glimm | The data properties dp1 and dp2 are disjoint. The strings ab and ac are dp1 fillers for the individual a and can, thus, not be used as dp2 fillers for a. The pattern a(b|c), however, admits only ab and ac as values, which makes the ontology inconsistent. |
No newly submitted test cases currently use this feature.
