Submissions:Class by path attribute value - Revision history

FrancoisScharffe at 12:56, 3 March 2010

2010-03-03T12:56:59Z

FrancoisScharffe at 12:55, 3 March 2010

2010-03-03T12:55:24Z

FrancoisScharffe at 12:54, 3 March 2010

2010-03-03T12:54:59Z

FrancoisScharffe: New page: {{Alignment_OP_Proposal_toolbar}} {{Graphical representation |ImageName=Class-by-path-attribute-value.png }} {{Alignment OP General Template |Name=Class by path attribute value |SubmittedB...

2010-03-03T12:54:00Z

New page: {{Alignment_OP_Proposal_toolbar}} {{Graphical representation |ImageName=Class-by-path-attribute-value.png }} {{Alignment OP General Template |Name=Class by path attribute value |SubmittedB...

New page

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation
|ImageName=Class-by-path-attribute-value.png
}}
{{Alignment OP General Template
|Name=Class by path attribute value
|SubmittedBy=FrancoisScharffe
|Author=Francois Scharffe
}}
{{Alignment OP Description Template
|Domain=General
|Problem=A class in one ontology is aligned to a class in another ontology and the criteria
for membership in the class are specified by an attribute value at the end of a path.
|Solution=The two classes in two ontologies are provided along with a statement involving
either one class or both classes. This statement is a precondition for the correspondence. This pattern is agnostic to whether the correspondence is unidirectional or bidirectional. However, if the correspondence is bidirectional (equivalence relation), the same precondition applies for both directions.

}}
{{Alignment OP Example Template
|Solution=
<Cell>
<entity1>
<Class>
<and>
<Class rdf:about="o1 :Person"/>
<AttributeValueCondition>
<onAttribute>
<Property>
<first>
<Relation rdf:about="o1 :workplace"/>
</first>
<next>
<Property>
<first>
<Relation rdf:about="o1 :address"/>
</first>
<next>
<Property rdf:about="o1 :city"/></next>
</next>
</Property>
</next>
</Property>
</onAttribute>
<comparator rdf:resource="xsd:not-equal"/>
<value>
<Property>
<first>
<Relation rdf:about="o1 :address"/>
</first>
<next>
<Property rdf:about="o1 :city"/>
</next>
</Property>
</value>
</AttributeValueCondition>
</and>
</Class>
</entity1>
<entity2>
<Class rdf:about="o2 :Commuter">
</entity2>
</Cell>
}}
{{Alignment OP References Template}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}

@@ Line 17: / Line 17: @@
 }}
 {{Alignment OP Example Template
 |Solution=Example correspondence:

@@ Line 19: / Line 19: @@
 |Solution=Example correspondence:
-<Cell>
+ <Cell>
    <entity1>
     <Class>

@@ Line 1: / Line 1: @@
 {{Alignment_OP_Proposal_toolbar}}
 {{Graphical representation
 |ImageName=Class-by-path-attribute-value.png
@@ Line 14: / Line 15: @@
 |Solution=The two classes in two ontologies are provided along with a statement involving
 either one class or both classes. This statement is a precondition for the correspondence. This pattern is agnostic to whether the correspondence is unidirectional or bidirectional. However, if the correspondence is bidirectional (equivalence relation), the same precondition applies for both directions.
 }}
 {{Alignment OP Example Template
-|Solution=
+|Solution=Example correspondence:
- <Cell>
    <entity1>
     <Class>
@@ Line 66: / Line 67: @@
 {{Reviews about me}}
 {{Modeling issues about me}}