Submissions:Class by attribute value

From Odp

(Difference between revisions)
Jump to: navigation, search
(initial submission)
m
Line 1: Line 1:
{{Alignment_OP_Proposal_toolbar}}
{{Alignment_OP_Proposal_toolbar}}
{{Include Image
{{Include Image
-
|ImageName=class-by-attribute-value.png  
+
|ImageName=class-by-attribute-value.png
}}
}}
{{Alignment OP General Template
{{Alignment OP General Template
Line 16: Line 16:
}}
}}
{{Alignment OP Example Template
{{Alignment OP Example Template
-
|Solution= <Cell>
+
|Solution=Example in EDOAL:
 +
<Cell>
   <entity1>
   <entity1>
   <Class>
   <Class>
Line 39: Line 40:
}}
}}
{{Alignment OP References Template
{{Alignment OP References Template
-
|RelatedTo=Class equivalence, Class subsumption,  
+
|RelatedTo=Class equivalence, Class subsumption,
}}
}}
{{Scenarios about me}}
{{Scenarios about me}}
{{Reviews about me}}
{{Reviews about me}}

Revision as of 16:44, 2 February 2010


This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal

Current revision ID: 6253

Image:class-by-attribute-value.png

General information

Name Class by attribute value
Also known as
Author(s) Francois Scharffe
SubmittedBy FrancoisScharffe


Description

Domain (if applicable)
Alignment problem addressed A class in one ontology is equivalent to the subclass of an ontology in a second

ontology of exactly those instances which have a specified property value.

Alignment solution This pattern establishes a mapping between a class/property/property-value combination in one ontology and a class in another. This pattern is agnostic as to whether the mapping is unidirectional or bidirectional direction of the mapping can be achieved through combination of the pattern with the equivalent classes or class subsumption correspondence patterns.
Alignment workflow The scope of a class in one ontology is narrower than the scope of a class

in the other ontology. Both scopes can be matched by restricting one class to those instances having a particular value for a certain property.

Reusable component


Example

Problem example
Solution example Example in EDOAL:
<Cell>
 <entity1>
  <Class>
   <and>
    <Class rdf:about="vin:Vin">
   </and>
   <and>
    <AttributeValueCondition>
     <onAttribute>
      <Property rdf:about="vin:terroir"/>
     </onAttribute>
     <comparator>xsd:Equal</comparator>
     <value>geo:Bordelais</value>
    </AttributeValueCondition>
   </and>
  </Class>
 </entity1>
 <entity2>
  <Class rdf:about="wine:BordeauxWine"/>
 </entity2>
</Cell>
Consequences


Reference

Origin
Known use
Reference
Related to Submissions:Class equivalence, Submissions:Class subsumption
Test


Scenarios

Scenarios about Class by attribute value

No scenario is added to this Content OP.

Reviews

Reviews about Class by attribute value

There is no review about this proposal. This revision (revision ID 6253) takes in account the reviews: none

Other info at evaluation tab

Personal tools
Quality Committee
Content OP publishers