Submissions:Class correspondence defined by relation domain
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) add a new scenario for Class correspondence defined by relation domain In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 8790 |
Graphical representation
Diagram
General information
| Name | Class correspondence defined by relation domain |
|---|---|
| Also known as | Subclass correspondence defined by relation domain |
| Author(s) | Francois Scharffe |
| SubmittedBy | FrancoisScharffe |
Description
| Domain (if applicable) | General |
|---|---|
| Alignment problem addressed | A class in one ontology is equivalent to the subclass of a class in a second ontology of exactly those instances which are in the domain of a specified relation. |
| Alignment solution | This pattern establishes a correspondence between a class and relation in one ontology and a class in another |
| Alignment workflow | |
| Reusable component |
Example
| Problem example | |
|---|---|
| Solution example | <Cell>
<entity1>
<Class rdf:about="o1:Parent"/>
</entity1>
<entity2>
<Class>
<and>
<Class rdf:about="o2:Animal">
</and>
<and>
<AttributeOccurenceCondition>
<onAttribute>
<Relation rdf:about="o2:children"/>
</onAttribute>
<AttributeOccurenceCondition>
</and>
</Class>
</entity2>
<relation>subsumption</relation>
</Cell>
|
| Consequences |
Reference
| Origin | |
|---|---|
| Known use | |
| Reference | |
| Related to | Submissions:Class by Attribute Occurence Correspondence |
| Test |
Scenarios
Scenarios about Class correspondence defined by relation domain
No scenario is added to this Content OP.
Reviews
Reviews about Class correspondence defined by relation domain
There is no review about this proposal. This revision (revision ID 8790) takes in account the reviews: none
Other info at evaluation tab
Modeling issues
Modeling issues about Class correspondence defined by relation domain
There is no Modeling issue related to this proposal.
References
