Submissions:Class subsumption
From Odp
| If you are a member of quality committee please visit the
If you are author of this proposal or you want to contribute to this pattern's review, you can: specify if this revision takes in account any of the review(s) In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 8960 |
Graphical representation
Diagram
General information
| Name | Class subsumption |
|---|---|
| Also known as | |
| Author(s) | FrancoisScharffe |
| SubmittedBy | FrancoisScharffe |
Description
| 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 |
Example
| 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 |
Reference
| Origin | |
|---|---|
| Known use | |
| Reference | |
| Related to | Submissions:Class equivalence |
| Test |
Scenarios
No scenario is added to this Content OP.
Reviews
There is no review about this proposal. This revision (revision ID 8960) takes in account the reviews: none
Other info at evaluation tab
Modeling issues
There is no Modeling issue related to this proposal.
References
