Submissions:CyclicSubClassOf

From Odp

(Difference between revisions)
Jump to: navigation, search
(New page: {{Reengineering_OP_Proposal_toolbar}} {{Reengineering OP Proposal General Information Template |Name=CyclicSubClassOf |Problem=Sometimes there are several syntactical forms (e.g. syntacti...)
Line 1: Line 1:
{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
{{Reengineering OP Proposal General Information Template
-
|Name=CyclicSubClassOf  
+
|Name=CyclicSubClassOf
|Problem=Sometimes there are several syntactical forms (e.g. syntactical sugar) with the same logical meaning. Refactoring patterns can transform one form to another, they are independant of a specific domain.
|Problem=Sometimes there are several syntactical forms (e.g. syntactical sugar) with the same logical meaning. Refactoring patterns can transform one form to another, they are independant of a specific domain.
Line 13: Line 13:
|Description=The ontology before applying the pattern contains an explicitly defined cyclic SubClassOf chain with an arbitrary number of classes Ci (i > 0):
|Description=The ontology before applying the pattern contains an explicitly defined cyclic SubClassOf chain with an arbitrary number of classes Ci (i > 0):
-
SubClassOf(A C1)
+
''SubClassOf(A C1)
SubClassOf(C1 C2)
SubClassOf(C1 C2)
Line 19: Line 19:
SubClassOf(C2 C3)
SubClassOf(C2 C3)
-
  ...
+
...
-
SubClassOf(Cn A)
+
SubClassOf(Cn A)''
-
|Graphical Representation=Image:CyclisSubClassOf.png
+
 
 +
|Graphical Representation=CyclisSubClassOf.png
}}
}}
{{Reengineering OP Proposal Process Template
{{Reengineering OP Proposal Process Template
Line 28: Line 29:
EquivalentClasses( A C1 C2 C3 ... Cn)
EquivalentClasses( A C1 C2 C3 ... Cn)
-
|Graphical Representation=Image:EquivalentClassesAxiom.png
+
|Graphical Representation=EquivalentClassesAxiom.png
}}
}}
{{Reengineering OP Proposal Scenario Example Template
{{Reengineering OP Proposal Scenario Example Template
|Description=Refactoring patterns are independant of a specific scenario resp. domain
|Description=Refactoring patterns are independant of a specific scenario resp. domain
-
 
}}
}}
{{Reengineering OP Proposal NOR Example Template
{{Reengineering OP Proposal NOR Example Template

Revision as of 12:42, 21 August 2009


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 informations about the evaluation process of this proposal

Current revision ID: 5565

General information

Name CyclicSubClassOf
Problem Sometimes there are several syntactical forms (e.g. syntactical sugar) with the same logical meaning. Refactoring patterns can transform one form to another, they are independant of a specific domain.

A explicitly defined cyclic SubClassOf chain is more difficult to discover and understand by a human than an EquivalentClassAxiom. Because it is explicitly defined there is not any dange in replacing it with an (explicitly defined) EquivalentClassAxioms.


Non-Ontological Resource

Description Not applicable for refactoring patterns
Graphical Representation

Diagram (this article has no graphical representation)


Ontology

Description The ontology before applying the pattern contains an explicitly defined cyclic SubClassOf chain with an arbitrary number of classes Ci (i > 0):

SubClassOf(A C1)

SubClassOf(C1 C2)

SubClassOf(C2 C3)

...

SubClassOf(Cn A)

Graphical Representation

Diagram

Image:CyclisSubClassOf.png


Process

Description Replacing the cyclic SubClassOf chain with an EquivalentClassesAxiom:

EquivalentClasses( A C1 C2 C3 ... Cn)

Graphical Representation

Diagram

Image:EquivalentClassesAxiom.png


Scenario example

Description Refactoring patterns are independant of a specific scenario resp. domain


Example of a Non-Ontological Resource

Description Not applicable for refactoring patterns
Graphical Representation

Diagram (this article has no graphical representation)

Web Reference http://Not applicable for refactoring patterns


Ontology example

Description Not applicable for this refactoring pattern
Graphical Representation

Diagram (this article has no graphical representation)

Web Reference http://Not applicable for this refactoring pattern


Process example

Description Not applicable for this refactoring pattern
Graphical Representation

Diagram (this article has no graphical representation)


About

SubmittedBy OlafNoppens
Author OlafNoppens
Also known as
Known uses
Related to
Other References


Scenarios

Scenarios about CyclicSubClassOf

No scenario is added to this Content OP.

Reviews

Reviews about CyclicSubClassOf

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

Other info at evaluation tab

Personal tools
Quality Committee
Content OP publishers