Submissions:Disjoint Classes
From Odp
| If you are a member of quality committee please visit the
If you are author of this proposal or you want to contribute to this pattern's review, you can: specify if this revision takes in account any of the review(s) In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 8961 |
Graphical representation
Diagram (this article has no graphical representation)
General information
| Name | Disjoint Classes |
|---|---|
| Also known as | Class disjointness |
| Author(s) | Francois Scharffe |
| SubmittedBy | FrancoisScharffe |
Description
| Domain (if applicable) | General |
|---|---|
| Alignment problem addressed | Two classes have a different intension, and no intersection of their extension.
Specifying a disjoint correspondence may help a matcher in not proposing any correspondences between these classes. |
| Alignment solution | This pattern establishes correspondence stating that classes are disjoint. |
| Alignment workflow | |
| Reusable component |
Example
| Problem example | |
|---|---|
| Solution example | Example in EDOAL, the expressive and declarative ontology alignment language
<Cell> <entity1><Class rdf:about="O1:Top"/></entity1> <entity2><Class rdf:about="O2:Top"/></entity2> <relation>Disjoint</relation> </Cell> |
| Consequences |
Reference
| Origin | |
|---|---|
| Known use | |
| Reference | |
| Related to | Submissions:DisjointAttributes, Submissions:DisjointInstances |
| Test |
Scenarios
Scenarios about Disjoint Classes
No scenario is added to this Content OP.
Reviews
Reviews about Disjoint Classes
There is no review about this proposal. This revision (revision ID 8961) takes in account the reviews: none
Other info at evaluation tab
Modeling issues
Modeling issues about Disjoint Classes
There is no Modeling issue related to this proposal.
References
