Submissions:Disjoint Classes Revision as of 20:00, 5 March 2010 by MichaelUschold (Talk | contribs) (diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Warning!

This is an old revision. Go to current revision

This pattern has been certified.

Related submission, with evaluation history, can be found here

Last modified date is: 2010-03-05

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.

Some subquery has no valid condition.

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.

Some subquery has no valid condition.

References

Add a reference