| Line 1: | Line 1: | ||
{{Alignment_OP_Proposal_toolbar}} | {{Alignment_OP_Proposal_toolbar}} | ||
{{Include Image | {{Include Image | ||
| − | |ImageName=class-equivalence. | + | |ImageName=class-equivalence.png |
}} | }} | ||
{{Alignment OP General Template | {{Alignment OP General Template | ||
|
Last modified date is: 2009-11-20 |
| Name | Class equivalence |
|---|---|
| Also known as | Equivalent classes |
| Author(s) | François Scharffe |
| SubmittedBy | FrancoisScharffe |
| 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 | Exemple in the ontology alignment language:
<Cell> <entity1><Class rdf:about="O1:Human"/></entity1> <entity2><Class rdf:about="O2:Person"/></entity2> <relation>equivalence</relation> </Cell> |
| Consequences | The equivalent classed are related by an equivalence correspondence. |
| Origin | |
|---|---|
| Known use | This is a very common correspondence. |
| Reference | |
| Related to | |
| Test |
No scenario is added to this Content OP.
This revision (revision ID 6045) takes in account the reviews: none
Other info at evaluation tab
'Ontology Design Patterns'
