Submissions:View Inheritance

From Odp

(Difference between revisions)
Jump to: navigation, search
Line 9: Line 9:
}}
}}
{{Architectural OP Description Template
{{Architectural OP Description Template
-
|Problem=There are ontology domain concepts that are difficult to represent due to the complexities in their de�nition and the presence of multiple alternative criteria to classify their abstractions.
+
|Problem=There are ontology domain concepts that are difficult to represent due to the complexities in their definition and the presence of multiple alternative criteria to classify their abstractions.
 +
|Solution=Introduce a class that represent each one of the alternative abstraction criteria identified for the domain concept. In the figure, the classes named ''Criterion_i''
}}
}}
{{Architectural OP Example Template}}
{{Architectural OP Example Template}}

Revision as of 07:36, 29 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 information about the evaluation process of this proposal

Current revision ID: 5634

Image:Fig_view_inheritance_structure.png

General information

Name View Inheritance
Also known as
Author(s) Benedicto Rodriguez-Castro, Hugh Glaser
Domain (if applicable)
Submitted by BenedictoRodriguezCastro, Hugh Glaser


Description

Problem description There are ontology domain concepts that are difficult to represent due to the complexities in their definition and the presence of multiple alternative criteria to classify their abstractions.
Solution description Introduce a class that represent each one of the alternative abstraction criteria identified for the domain concept. In the figure, the classes named Criterion_i
Implementation workflow
Reusable component


Example

Problem example
Solution example
Consequences


Pattern reference

Origin
Known use
Reference
Related ODP


Scenarios

Scenarios about View Inheritance

No scenario is added to this Content OP.

Reviews

Reviews about View Inheritance

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

Other info at evaluation tab

Personal tools
Quality Committee
Content OP publishers