| Line 18: | Line 18: | ||
}} | }} | ||
{{Alignment OP Example Template | {{Alignment OP Example Template | ||
| − | |Solution=<Cell> | + | |Solution=Example solution in the ontology alignment language: |
| − | + | <Cell> | |
| − | + | <entity1><Class rdf:about="O1:Mammal"/></entity1> | |
| − | + | <entity2><Class rdf:about="O2:Vertebrate"/></entity2> | |
| − | </Cell> | + | <relation>subsumedBy</relation> |
| + | </Cell> | ||
}} | }} | ||
{{Alignment OP References Template | {{Alignment OP References Template | ||
|
Last modified date is: 2010-01-27 |
| Name | Class subsumption |
|---|---|
| Also known as | |
| Author(s) | FrancoisScharffe |
| SubmittedBy | FrancoisScharffe |
| Domain (if applicable) | general |
|---|---|
| Alignment problem addressed | A class in one ontology is a subclass of a class in a second ontology but there is
no functional description of the exact mapping. There is no way of expressing additional properties of the subclass. |
| Alignment solution | This pattern establishes a unidirectional correspondence from a more specific class
in one ontology to a broader class in another ontology. The relation is broadened to allow class expressions in addition to merely class names. |
| Alignment workflow | |
| Reusable component |
| Problem example | |
|---|---|
| Solution example | Example solution in the ontology alignment language:
<Cell> <entity1><Class rdf:about="O1:Mammal"/></entity1> <entity2><Class rdf:about="O2:Vertebrate"/></entity2> <relation>subsumedBy</relation> </Cell> |
| Consequences |
| Origin | |
|---|---|
| Known use | |
| Reference | |
| Related to | Submissions:Class equivalence |
| Test |
No scenario is added to this Content OP.
This revision (revision ID 6178) takes in account the reviews: none
Other info at evaluation tab
'Ontology Design Patterns'
