| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Alignment_OP_Proposal_toolbar}} | {{Alignment_OP_Proposal_toolbar}} | ||
| − | {{ | + | {{Graphical representation header}} |
| + | {{Graphical representation | ||
|ImageName=class-subsumption.png | |ImageName=class-subsumption.png | ||
}} | }} | ||
| Line 31: | Line 32: | ||
{{Scenarios about me}} | {{Scenarios about me}} | ||
{{Reviews about me}} | {{Reviews about me}} | ||
| + | {{Modeling issues about me}} | ||
| + | {{My references}} | ||
|
Last modified date is: 2010-03-05 |
Diagram
| 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 8960) takes in account the reviews: none
Other info at evaluation tab
'Ontology Design Patterns'
