Submissions:Disjoint Classes

From Odp

Jump to: navigation, search

This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

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


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
 <entity1><Class rdf:about="O1:Top"/></entity1>
 <entity2><Class rdf:about="O2:Top"/></entity2>


Known use
Related to Submissions:DisjointAttributes, Submissions:DisjointInstances


Scenarios about Disjoint Classes

No scenario is added to this Content OP.


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.


Add a reference

Personal tools
Quality Committee
Content OP publishers