Revision as of 09:15, 20 November 2009

Warning!

This is an old revision. Go to current revision

Last modified date is: 2009-11-20

General information

Domain (if applicable)
Alignment problem addressed	Two classes in two ontologies have the same intension.
Alignment solution	The pattern relates the two classes by specifying them as being equivalent.
Alignment workflow
Reusable component

Problem example

Solution example

<Cell>

<entity1><Class rdf:about="O1:Human"/></entity1>
<entity2><Class rdf:about="O2:Person"/></entity2>
<relation>equivalence</relation>

</Cell>

Consequences

Origin
Known use	This is a very common correspondence.
Reference
Related to
Test

Scenarios about Class equivalence

No scenario is added to this Content OP.

Reviews about Class equivalence

There is no review about this proposal.

Some subquery has no valid condition.

This revision (revision ID 6046) takes in account the reviews: none

@@ Line 1: / Line 1: @@
 {{Alignment_OP_Proposal_toolbar}}
 {{Include Image
-|ImageName=class-equivalence.png
+|ImageName=class-equivalence.pdf
 }}
 {{Alignment OP General Template
@@ Line 15: / Line 15: @@
 {{Alignment OP Example Template
 |Scenario=Human vs Person
-|Solution=Exemple in the ontology alignment language:
+|Solution=<Cell>
- <Cell>
+ <entity1><Class rdf:about="O1:Human"/></entity1>
-  <entity1><Class rdf:about="O1:Human"/></entity1>
+ <entity2><Class rdf:about="O2:Person"/></entity2>
-  <entity2><Class rdf:about="O2:Person"/></entity2>
+ <relation>equivalence</relation>
-  <relation>equivalence</relation>
+</Cell>
- </Cell>
 |Consequences=The equivalent classed are related by an equivalence correspondence.
 }}