Submissions:SynonymOrEquivalence (SOE)

From Odp

(Difference between revisions)
Jump to: navigation, search
Current revision (08:30, 31 May 2010) (view source)
m (Text replace - 'WOP2009:Main' to 'WOP:2009')
 
(9 intermediate revisions not shown.)
Line 1: Line 1:
{{Logical_OP_Proposal_toolbar}}
{{Logical_OP_Proposal_toolbar}}
-
{{Include Image
+
{{Graphical representation header}}
 +
{{Graphical representation
|ImageName=[[Image:AntipatternSOE.jpg]]
|ImageName=[[Image:AntipatternSOE.jpg]]
}}
}}
Line 19: Line 20:
}}
}}
{{Logical OP Reference Template}}
{{Logical OP Reference Template}}
-
 
+
{{Additional information header}}
 +
[[Category:Review assigned]]
{{Scenarios about me}}
{{Scenarios about me}}
{{Reviews about me}}
{{Reviews about me}}
 +
{{Modeling issues about me}}
 +
{{My references}}
 +
{{Submission to event
 +
|Event=WOP:2009
 +
}}

Current revision


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: 9708

Graphical representation

Diagram (this article has no graphical representation)

General information

Name SynonymOrEquivalence (SOE)
Also known as
Author(s)
SubmittedBy Catherine Roussey, Oscar Corcho


Description

Motivation We have identified a set of patterns that are commonly used by domain experts in their DL formalisations and OWL implementations, and that normally result in unsatisfiable classes or modelling errors. As aforementioned all these antipatterns come from a misuse and misunderstanding of DL expressions by ontology developers. Thus they are all Logical AntiPatterns (LAP): they are independent from a specific domain of interest, but dependent on the expressivity of the logical formalism used for the representation. We have categorized them into three groups:
Aim The ontology developer wants to express that two classes C1 and C2 are identical. This is not very useful in a single ontology that does not import others. Indeed, what the ontology developer generally wants to represent is a terminological synonymy relation: the class C1 has two labels: C1 and C2. Usually one of the classes is not used anywhere else in the axioms defined in the ontology.
Solution description C1 isEquivalentTo C2

The proposal for avoiding this antipattern is the following (if C2 is the less used term in the ontology) add all the comments and labels of C2 into C1 and remove C2

Elements
Implementation
Reusable component
Component type


Example

Problem example Subterranean_Watercourses isEquivalentTo Subterranean_Rivers

see Corriente_Subterranea concept in Hydrontology

Pattern solution example http://www.dia.fi.upm.es/~ocorcho/OWLDebugging/
Consequences


Pattern reference

Origin
Known use
Reference
Related ODP
Used in combination with
Test

Additional information

Scenarios

Scenarios about SynonymOrEquivalence (SOE)

No scenario is added to this Content OP.

Reviews

Reviews about SynonymOrEquivalence (SOE)
Review article Posted on About revision (current is 9708)
MartaSabou about SynonymOrEquivalence (SOE) 24550838 September 2009 56175,617
GerdGroener about SynonymOrEquivalence (SOE) 24550838 September 2009 57095,709

This revision (revision ID 9708) takes in account the reviews: none

Other info at evaluation tab


Modeling issues

Modeling issues about SynonymOrEquivalence (SOE)

There is no Modeling issue related to this proposal.


References

Add a reference


Submission to event

WOP:2009

Personal tools
Quality Committee
Content OP publishers