MariaPoveda (Talk | contribs) (New page: {{Logical_OP_Proposal_toolbar}} {{Graphical representation header}} {{Graphical representation |ImageName=Symmetric_n-ary_relationship_v1.jpg }} {{Logical OP General Template |Name=Symm...) |
(Review has been created. Annotation 'assigned' has been removed. Annotation 'waiting' has been removed.) |
||
(9 intermediate revisions by 3 users not shown) | |||
Line 6: | Line 6: | ||
{{Logical OP General Template | {{Logical OP General Template | ||
|Name=Symmetric n-ary relationship | |Name=Symmetric n-ary relationship | ||
− | |SubmittedBy=MariaPoveda, MariCarmenSuarezFigueroa, | + | |SubmittedBy=MariaPoveda, MariCarmenSuarezFigueroa, |
− | |Author=MariaPoveda, MariCarmenSuarezFigueroa, | + | |Author=MariaPoveda, MariCarmenSuarezFigueroa, |
}} | }} | ||
{{Logical OP Description Template | {{Logical OP Description Template | ||
− | |Motivation=The symmetric n-ary relationship pattern emerged from the need of modelling distances among two points. | + | |Motivation=The symmetric n-ary relationship pattern emerged from the need of modelling distances among two points. |
− | + | This problem is a clear case of an n-ary relationship where the relation between two points needs a further argument to represent the distance between such points. | |
− | + | ||
− | | | + | Once we have applied the n-ary pattern for this use case (http://www.w3.org/TR/swbp-n-aryRelations/#useCase1), we can realize that the origin and the destination of the n-ary relation belong to the same class. In addition, the value for the relationship is the same to represent the distance from A to B and vice-versa. Then, if we want to represent both distances we should instanciate the pattern twice, from A to B and vice-versa, resulting in a redundant representation. |
+ | |Aim=This pattern allows representing symmetric n-ary relationships, i.e. binary relationships between two elements that need a further argument that has the same value for both directions of the relationship. | ||
+ | If SNAry is the symmetric n-ary relationship and z is its value for the elements x and y, then: | ||
+ | SNAry(x,y)=z iff SNAry(y,x)=z | ||
+ | |Solution=A class to represent the n-ary relationship together with the value for the further needed argument (Relationship or Attribute) has been created. | ||
+ | A relationship between the abovementioned class and the classes involved in the symmetric n-ary relationship is created. | ||
|Elements=Class, Relationship, Attribute | |Elements=Class, Relationship, Attribute | ||
Axioms: cardinality and equivalentClass | Axioms: cardinality and equivalentClass | ||
Line 20: | Line 24: | ||
{{Logical OP Example Template | {{Logical OP Example Template | ||
|ProblemExample=For example, we might want to represent the distance expressed in kilometres between two places. | |ProblemExample=For example, we might want to represent the distance expressed in kilometres between two places. | ||
− | |SolutionExample=http://ontologydesignpatterns.org/wiki/images/ | + | |SolutionExample=http://ontologydesignpatterns.org/wiki/images/b/bd/Symmetric_n-ary_relationship_distance.jpg |
− | |Consequences=The main advantage of this pattern is that allows representing distance between places without | + | |Consequences=The main advantage of this pattern is that allows representing distance between places without including redundancy in the ontology. |
}} | }} | ||
{{Logical OP Reference Template | {{Logical OP Reference Template | ||
− | |Origin= | + | |Origin=Modelling distance between stages of St James Way during the Geobuddies ontology network development (http://geobuddies.dia.fi.upm.es). |
|KnownUse=Geobuddies ontology network | |KnownUse=Geobuddies ontology network | ||
|RelatedTo=N-ary Relation: New Class (LP-NR -01) | |RelatedTo=N-ary Relation: New Class (LP-NR -01) | ||
Line 37: | Line 41: | ||
|Event=WOP:2010 | |Event=WOP:2010 | ||
}} | }} | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | [[Category:Review assigned]] |
Diagram
Name | Symmetric n-ary relationship |
---|---|
Also known as | |
Author(s) | MariaPoveda, MariCarmenSuarezFigueroa |
SubmittedBy | MariaPoveda, MariCarmenSuarezFigueroa |
Motivation | The symmetric n-ary relationship pattern emerged from the need of modelling distances among two points.
This problem is a clear case of an n-ary relationship where the relation between two points needs a further argument to represent the distance between such points. Once we have applied the n-ary pattern for this use case (http://www.w3.org/TR/swbp-n-aryRelations/#useCase1), we can realize that the origin and the destination of the n-ary relation belong to the same class. In addition, the value for the relationship is the same to represent the distance from A to B and vice-versa. Then, if we want to represent both distances we should instanciate the pattern twice, from A to B and vice-versa, resulting in a redundant representation. |
---|---|
Aim | This pattern allows representing symmetric n-ary relationships, i.e. binary relationships between two elements that need a further argument that has the same value for both directions of the relationship.
If SNAry is the symmetric n-ary relationship and z is its value for the elements x and y, then: SNAry(x,y)=z iff SNAry(y,x)=z |
Solution description | A class to represent the n-ary relationship together with the value for the further needed argument (Relationship or Attribute) has been created.
A relationship between the abovementioned class and the classes involved in the symmetric n-ary relationship is created. |
Elements | Class, Relationship, Attribute
Axioms: cardinality and equivalentClass |
Implementation | |
Reusable component | |
Component type |
Origin | Modelling distance between stages of St James Way during the Geobuddies ontology network development (http://geobuddies.dia.fi.upm.es). |
---|---|
Known use | Geobuddies ontology network |
Reference | |
Related ODP | N-ary Relation: New Class (LP-NR -01) |
Used in combination with | |
Test |
No scenario is added to this Content OP.
This revision (revision ID 10106) takes in account the reviews: none
Other info at evaluation tab
![]() |
Submission to event |
---|