Category:ContentOP
From Odp
Current revision (22:27, 3 July 2009) (view source) |
|||
| (6 intermediate revisions not shown.) | |||
| Line 1: | Line 1: | ||
{{Definition | {{Definition | ||
|Content Ontology Design Patterns (CPs) | |Content Ontology Design Patterns (CPs) | ||
| - | |CPs are distinguished networked ontologies and have their own namespace. | + | |CPs are distinguished networked ontologies and have their own namespace. They cover a specific set of competency questions (requirements), which represent the problem they provide a solution for. Furthermore, CPs show certain characteristics, i.e. they are: computational, small, autonomous, hierarchical, cognitively relevant, linguistically relevant, and best practices. See [[Odp:EvaluationPrinciples| evaluation principles]] for more details. |
}} | }} | ||
| - | + | == Description == | |
| - | + | ||
| - | |||
| - | |||
They show the following characteristics: | They show the following characteristics: | ||
| + | CPs encode conceptual, rather than logical design patterns. In other words, | ||
| + | while Logical OPs solve design problems independently of a particular conceptualization, CPs propose patterns for solving design problems for the domain | ||
| + | classes and properties that populate an ontology, therefore addressing con- | ||
| + | tent problems. CPs are instantiations of Logical OPs (or of compositions | ||
| + | of Logical OPs), featuring a non-empty signature. Hence, they have an explicit non-logical vocabulary for a specific domain of interest (i.e. they are | ||
| + | content-dependent). CPs provide solutions to domain modeling problems and | ||
| + | affect only the specific region of the ontology dealing with such domain modeling problems. They are typically reused by applying specialization, extension, | ||
| + | and composition to them. In principle, CPs do not depend on any specific | ||
| + | language, however in order to reuse them as building blocks, they have to be | ||
| + | implemented in some way. In the portal we mainly deal with CPs | ||
| + | in a Semantic Web context, hence we currently support OWL as a reference formalism for | ||
| + | representation. | ||
| + | |||
References: | References: | ||
| Line 19: | Line 29: | ||
* [[:Category:CertifiedContentOP| Certified CPs]] must satisfy a set of [[Odp:EvaluationPrinciples| evaluation principles]] and are listed in the [[Catalogue:Main| official catalogue]] | * [[:Category:CertifiedContentOP| Certified CPs]] must satisfy a set of [[Odp:EvaluationPrinciples| evaluation principles]] and are listed in the [[Catalogue:Main| official catalogue]] | ||
* [[:Category:ProposedContentOP| Proposed CPs]] are submitted by users of the ODP community and are listed in the [[Submissions:Main| submission area]]. | * [[:Category:ProposedContentOP| Proposed CPs]] are submitted by users of the ODP community and are listed in the [[Submissions:Main| submission area]]. | ||
| + | |||
| + | |||
| + | [[Category:OntologyDesignPattern]] | ||
Current revision
Description
They show the following characteristics: CPs encode conceptual, rather than logical design patterns. In other words, while Logical OPs solve design problems independently of a particular conceptualization, CPs propose patterns for solving design problems for the domain classes and properties that populate an ontology, therefore addressing con- tent problems. CPs are instantiations of Logical OPs (or of compositions of Logical OPs), featuring a non-empty signature. Hence, they have an explicit non-logical vocabulary for a specific domain of interest (i.e. they are content-dependent). CPs provide solutions to domain modeling problems and affect only the specific region of the ontology dealing with such domain modeling problems. They are typically reused by applying specialization, extension, and composition to them. In principle, CPs do not depend on any specific language, however in order to reuse them as building blocks, they have to be implemented in some way. In the portal we mainly deal with CPs in a Semantic Web context, hence we currently support OWL as a reference formalism for representation.
References:
- NeOn deliverable 2.5.1 for details on ontology design patterns
- NeOn deliverable 1.1.2 for details on networked ontologies.
See also
- Certified CPs must satisfy a set of evaluation principles and are listed in the official catalogue
- Proposed CPs are submitted by users of the ODP community and are listed in the submission area.
Subcategories
This category has the following 2 subcategories, out of 2 total.
