(initial submission) |
|||
| Line 1: | Line 1: | ||
{{Alignment_OP_Proposal_toolbar}} | {{Alignment_OP_Proposal_toolbar}} | ||
{{Include Image | {{Include Image | ||
| − | |ImageName=disjoint-classes.png | + | |ImageName=disjoint-classes-correspondences.png |
}} | }} | ||
{{Alignment OP General Template | {{Alignment OP General Template | ||
|
Last modified date is: 2010-02-01 |
| Name | Disjoint Classes |
|---|---|
| Also known as | Class disjointness |
| Author(s) | Francois Scharffe |
| SubmittedBy | FrancoisScharffe |
| 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 |
| 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 |
| Origin | |
|---|---|
| Known use | |
| Reference | |
| Related to | Submissions:DisjointAttributes, Submissions:DisjointInstances |
| Test |
No scenario is added to this Content OP.
This revision (revision ID 6224) takes in account the reviews: none
Other info at evaluation tab
'Ontology Design Patterns'
