'Ontology Design Patterns':ContentODPEvaluationPrinciples - Revision history

EvaBlomqvist: Odp:EvaluationPrinciples moved to Odp:ContentODPEvaluationPrinciples: Better name, so they are not confused with principles for all types of ODPs

2010-05-09T13:31:37Z

Odp:EvaluationPrinciples moved to Odp:ContentODPEvaluationPrinciples: Better name, so they are not confused with principles for all types of ODPs

EvaBlomqvist at 13:30, 9 May 2010

2010-05-09T13:30:21Z

Admin at 12:00, 8 May 2008

2008-05-08T12:00:54Z

Admin: /* Requirements */

2008-05-06T11:57:07Z

‎Requirements

Admin at 11:52, 6 May 2008

2008-05-06T11:52:08Z

Admin at 11:51, 6 May 2008

2008-05-06T11:51:37Z

Admin at 11:50, 6 May 2008

2008-05-06T11:50:10Z

Admin at 11:49, 6 May 2008

2008-05-06T11:49:47Z

Admin at 23:20, 5 May 2008

2008-05-05T23:20:51Z

Admin: /* Characteristics */

2008-05-05T23:05:48Z

‎Characteristics

@@ Line 1: / Line 1: @@
-[[:Category:CertifiedContentOP| Certified Content OPs]] must comply to a set of criteria and requirements described below.
+[[:Category:CertifiedContentOP| Certified Content ODPs (CPs)]] must comply to a set of criteria and requirements described below.
-Members of the [[QualityCommittee| Quality Committee]] use them in order to review and certify [[:Category:ProposedContentOP| Proposed Content OPs]].
+Members of the [[QualityCommittee| Quality Committee]] use them in order to review and certify [[:Category:ProposedContentOP| Proposed Content ODPs]].
-Such crtieria can also be useful as guidelines for those who want to [[Submissions:ProposeCP|propose a CP]].
+Such criteria can also be useful as guidelines for those who want to [[Submissions:ProposeCP|propose a Content ODP]].
 == Criteria ==

← Older revision		Revision as of 12:00, 8 May 2008
Line 26:		Line 26:

	* Each CP must be associated with: an OWL implementation, at least one OWL instantiation example, a UML diagram, the description of all its ontology elements, the domain, at least one competency question and one scenario, a source model from which it has been extracted/reengineered from.		* Each CP must be associated with: an OWL implementation, at least one OWL instantiation example, a UML diagram, the description of all its ontology elements, the domain, at least one competency question and one scenario, a source model from which it has been extracted/reengineered from.
−	* The CP OWL implementation has to be annotated by means of the [http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl\| ODP CP annotation schema]	+	* The CP OWL implementation has to be annotated by means of the [http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl ODP CP annotation schema]

← Older revision		Revision as of 11:57, 6 May 2008
Line 25:		Line 25:
	== Requirements ==		== Requirements ==

		+	* Each CP must be associated with: an OWL implementation, at least one OWL instantiation example, a UML diagram, the description of all its ontology elements, the domain, at least one competency question and one scenario, a source model from which it has been extracted/reengineered from.
	* The CP OWL implementation has to be annotated by means of the [http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl\| ODP CP annotation schema]		* The CP OWL implementation has to be annotated by means of the [http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl\| ODP CP annotation schema]

@@ Line 21: / Line 21: @@
 * '''Linguistically relevant components'''. Many CPs nicely match linguistic patterns called frames. A frame can be described as a lexically founded ontology design pattern; frames typically encode argument structures for verbs, e.g. the frame Desiring associates elements (or semantic roles) such as Experiencer, Event, FocalParticipant, LocationOfEvent, etc. The richest repository of frames is [http://framenet.icsi.berkeley.edu/ FrameNet]. Frames can be used for validating CPs with respect to lexical coverage, for lexicalizing them, and can be reengineered in order to populate the CP catalogue.
-* '''Best practice components'''. A CP should be used to describe a good practice of modelling. Good practices are intended here as local, thus derived from experts. The quality of CPs is currently based on the personal experience and taste of the proposers, or on the provenance of the knowledge resource
+* '''Best practice components'''. A CP should be used to describe a good practice of modelling. Good practices are intended here as local, thus derived from experts. The quality of CPs is currently based on the personal experience and taste of the proposers, or on the provenance of the knowledge resource where the CP comes from. However, evidence from reusability across different projects, large-scale applications, and open rating systems will provide a good base for CP evaluation.
 where the CP comes from. However, evidence from reusability across different projects, large-scale applications, and open rating systems will provide a good base for CP evaluation.
 == Requirements ==
 * The CP OWL implementation has to be annotated by means of the [http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl| ODP CP annotation schema]

@@ Line 1: / Line 1: @@
-[[:Category:CertifiedContentOP| Certified Content OPs]] must comply to a set of criteria described below.
+[[:Category:CertifiedContentOP| Certified Content OPs]] must comply to a set of criteria and requirements described below.
 Members of the [[QualityCommittee| Quality Committee]] use them in order to review and certify [[:Category:ProposedContentOP| Proposed Content OPs]].
@@ Line 21: / Line 21: @@
 * '''Linguistically relevant components'''. Many CPs nicely match linguistic patterns called frames. A frame can be described as a lexically founded ontology design pattern; frames typically encode argument structures for verbs, e.g. the frame Desiring associates elements (or semantic roles) such as Experiencer, Event, FocalParticipant, LocationOfEvent, etc. The richest repository of frames is [http://framenet.icsi.berkeley.edu/ FrameNet]. Frames can be used for validating CPs with respect to lexical coverage, for lexicalizing them, and can be reengineered in order to populate the CP catalogue.
 == Requirements ==
 * The CP OWL implementation has to be annotated by means of the [http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl| ODP CP annotation schema]

← Older revision	Revision as of 13:31, 9 May 2010
(No difference)

@@ Line 15: / Line 15: @@
 * '''Hierarchical components'''. A CP can be an element in a partial order, where the ordering relation requires that at least one of the classes or properties in the pattern is either specialized or generalized. A hierarchy of CPs can be built by specializing or generalizing some of the elements (either classes or relations).
-* '''Cognitively relevant components'''. CP visualization must be intuitive and compact, and should catch relevant, ''core'' notions of a [[Community:Domain|  domain]]. An interesting result from cognitive learning is that the development of expert skills typically ''selects'' patterns of concepts that are richly interconnected, and in normal cases, these patterns are applied without an explicit reference to the underlying detailed  knowledge acquired during the training period. This result matches the need to quickly reason or to automatize cer tain tasks, and the experimental
+* '''Cognitively relevant components'''. CP visualization must be intuitive and compact, and should catch relevant, ''core'' notions of a [[Community:Domain|  domain]]. An interesting result from cognitive learning is that the development of expert skills typically ''selects'' patterns of concepts that are richly interconnected, and in normal cases, these patterns are applied without an explicit reference to the underlying detailed knowledge acquired during the training period. This result matches the need to quickly reason or to automatize cer tain tasks, and the experimental data on short-term memory capacity. For this reason, independently of the generality at which a CP is singled out, it must contain the central notions that ''make rational thinking move'' for an expert in a given [[Community:Domain|  domain]] for a given task.
 data on short-term memory capacity. For this reason, independently of the generality at which a CP is singled out, it must contain the central notions that ''make rational thinking move'' for an expert in a given [[Community:Domain|  domain]] for a given task.
 * '''Reasoning relevant components'''. A CP has to allow some form of inference.

@@ Line 9: / Line 9: @@
 * '''Computational components'''. CPs are language-independent, and should be encoded in a higher-order representation language. Nevertheless, their (sample) representation in OWL is needed in order to (re)use them as ''building blocks'' over the Semantic Web.
-* '''Requirements covering components'''. A CP is deﬁned in terms of the requirements it satisﬁes, which
+* '''Requirements covering components'''. A CP is deﬁned in terms of the requirements it satisﬁes, which are expressed in terms of competency questions. This aspects is also important for stating the relevance of the CP with reference to a certain [[Community:Domain|  domain]].
 are expressed in terms of competency questions. This aspects is also important for stating the relevance of the CP with reference to a certain
-domain.
+* '''Small, autonomous components'''. Regardless of the particular way a CP has been created it is a small, autonomous ontology. Smallness and autonomy of CPs facilitate ontology designers: composing CPs enable them to govern the complexity of the whole ontology, because of the explicit rationales and the amount of know-how provided by the users of a same CP library. Smallness also allows diagrammatical visualizations that are aesthetically acceptable and easily memorizable.