Showing 25 pages using this property.
P | |
|---|---|
| PartOf + | The wikipage input value "This Content OP allows designers to represent entities and their parts i.e., part-whole relations, with transitivity. The temporal aspect of this relations cannot be expressed with this Content OP; in order to solve this issue the time indexed part of Content OP can be used. For an intransitive part-of Content OP see componency." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| PartOf + | Some subquery has no valid condition. + |
| ParticipantRole + | Some subquery has no valid condition. + |
| Participation + | Some subquery has no valid condition. + |
| Participation + | The wikipage input value "It is possible to model whatever relation between objects and events. Using cardinality restrictions appropriately allows to limit the number of participants, e.g. 'life of' is a specialization of this pattern that requires a functional object property (cardinality 1. . .1). This is a non-temporal version of the particpation relation. If we need a time-indexed relation, use http://ontologydesignpatterns.owl/cp/owl/timeindexedparticipation.owl" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Partition + | The wikipage input value "Let P be a named concept that is the partition which is divided into several concepts C_i. Then the partition is defined by introducing the following axioms (expressed in KRSS [1]): (define-concept P (or C0 C1 ... Cn) ) (disjoint Ci Cj) ( 0 ≤ i,j ≤ n, i ≠ j ). Here (disjoint C_i C_j)a placeholder for the pair-wise disjointness of all C_i. Note that C_i can also be arbitrary concept expressions (even if this is not allowed in the original KRSS syntax). In OWL 2 [2] the axioms can be expressed as follows (using OWL 2 Abstract Syntax): EquivalentClasses(P, ObjectUnionOf(C1, ..., Cn)) DisjointClasses(C1, ..., Cn) [1] Patel-Schneider, P. F., Swartout, B.: Description-Logic Knowledge Representation System Specification, 1993 [2] Motik, B., Patel-Schneider, P. F., Parsia, B.: OWL 2 Structural Specification and Functional-Style Syntax. W3C Candidate Recommendation 11 June 2009." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Partition + | The wikipage input value "The Partition Pattern is a logical pattern that introduces axioms which model a partition of concepts. A partition is a general structure which is divided into several disjoint parts. With respect to ontologies the structure is a concept which is divided into several pair-wise disjoint concepts. This pattern reflects the simplest case where a named concept is defined as a partition of concepts." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Partition + | Some subquery has no valid condition. + |
| Partition + | The wikipage input value "In an ontology about family relationship we defined concepts such as Person, Aunt and ParentOfSon which are characterized by a relationships such as hasChild(resp. the inverse relationship hasParent), hasSibling, ' married-with as well as by the gender of people (Male respectively Female). There are a lot of similar ontologies about family relationships. EquivalentClasses(Parent-Of-Son ObjectSomeValuesFrom (has-Child Male) ) EquivalentClasses(Parent-Of-Daughter ObjectSomeValuesFrom(has-Child Female) ) EquivalentClasses(Aunt ObjectIntersectionOf(Uncle-Or-Aunt Female)) EquivalentClasses(Uncle-Or-Aunt ObjectIntersectionOf(Person ObjectSomeValuesFrom(has-Sibling Parent))) The concept Gender is partitioned in Male and Female. Applying this pattern results in the following axioms: EquivalentClasses(Gender, ObjectUnionOf(Male Female)) DisjointClasses(Male Female)" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Pattern for re-engineering a classification scheme, which follows the adjacency list data model, into an ontology schema + | Some subquery has no valid condition. + |
| Pattern for re-engineering a classification scheme, which follows the adjacency list data model, into an ontology schema + | The wikipage input value "A non-ontological resource holds a classification scheme which follows the adjacency list model.
A classification scheme is a rooted tree of concepts, in which each concept groups entities by some particular degree of similarity. The semantics of the hierarchical relation between parents and children concepts may vary depending of the context. The adjacency list data model for hierarchical classifications proposes to create an entity which holds a list of items with a linking column associated to their parent items." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, The wikipage input value "The generated ontology will be based on the taxonomy architectural pattern (AP-TX-01). Each category in the classification scheme is mapped to a class, and the semantics of the relationship between children and parent categories are disambiguated by using an external resource. In the case of that the external resource does not provide any relation between two items, the pattern takes advantage of the use of logical patterns for asserting the relation partOf or subClassOf, as appropriate." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, The wikipage input value "1. Identify the classification scheme items which do not have a parent key value, i.e. classification scheme items without parents. 2. For each one of the above identified classification scheme items cei: 2.1. Create the corresponding ontology class, Ci class. 2.2. Identify the classification scheme items, cej , which are children of cei, by using the parent key values. 2.3. For each one of the above identified classification scheme items cej : 2.3.1. Create the corresponding ontology class, Cj class. 2.3.2. Using the external resource identify the semantics of the relation between Cj and Ci, and set up the relation identified. 2.3.3. Repeat from step 2.2 for cej as a new cei. 3. If there are more than one classification scheme items without parent cei 3.1. Create an ad-hoc class as the root class of the ontology. 3.2. Using the external resource identify the semantics of the relation between Ci class and the root class, and set up the relation identified." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, … |
| Pattern for re-engineering a classification scheme, which follows the flattened data model, into an ontology schema + | The wikipage input value "A non-ontological resource holds a classification scheme which follows the flattened data model. A classification scheme is a rooted tree of concepts, in which each concept groups entities by some particular degree of similarity. The semantics of the hierarchical relation between parents and children concepts may vary depending of the context.
The flattened data model is a denormalized structure for hierarchy representations.
In this case, each hierarchy level is represented on a different column. There are as many columns as levels the classification scheme has. Therefore each row has the complete path from the root to a leaf node." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, The wikipage input value "The generated ontology will be based on the taxonomy architectural pattern (AP-TX-01). Each category in the classification scheme is mapped to a class, and the semantics of the relationship between children and parent categories are disambiguated by using an external resource. In the case of that the external resource does not provide any relation between two items, the pattern takes advantage of the use of logical patterns for asserting the relation partOf or subClassOf." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, The wikipage input value "1. Select all the classification scheme items from the first level, using the level column and taking care to avoid duplicity. 2. For each one of the above selected classification scheme items cei: 2.1. Create the corresponding ontology class, Ci class. 2.2. Identify the classification scheme items, cej , on the next level, which are children of cei, by using the path and level columns. 2.3. For each one of the above identified classification scheme items cej : 2.3.1. Create the corresponding ontology class, Cj class. 2.3.2. Using the external resource identify the semantics of the relation between Cj and Ci, and set up the relation identified. 2.3.3. Repeat from step 2.2 for cej as a new cei. 3. If there are more than one classification scheme items from the first level cei 3.1. Create an ad-hoc class as the root class of the ontology. 3.2. Using the external resource identify the semantics of the relation between Ci class and the root class, and set up the relation identified." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, … |
| Pattern for re-engineering a classification scheme, which follows the flattened data model, into an ontology schema + | Some subquery has no valid condition. + |
| Pattern for re-engineering a classification scheme, which follows the path enumeration data model, into an ontology schema + | The wikipage input value "A non-ontological resource holds a classification scheme which follows the path enumeration model.
A classification scheme is a rooted tree of concepts, in which each concept groups entities by some particular degree of similarity. The semantics of the hierarchical relation between parents and children concepts may vary depending of the context.
The path enumeration data model, for classification schemes, takes advantage of that there is one and only one path from the root to every item in the classification. The path enumeration model stores that path as string by concatenating either the edges or the keys of the classification scheme items in the path." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, The wikipage input value "The generated ontology will be based on the taxonomy architectural pattern (AP-TX-01). Each category in the classification scheme is mapped to a class, and the semantics of the relationship between children and parent categories are disambiguated by using an external resource. In the case of that the external resource does not provide any relation between two items, the pattern takes advantage of the use of logical patterns for asserting the relation partOf or subClassOf, as appropriate." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, The wikipage input value "1. Identify the classification scheme items whose their path enumeration values have the shortest length, i.e. classification scheme items without parents. 2. For each one of the above identified classification scheme items cei: 2.1. Create the corresponding ontology class, Ci class. 2.2. Identify the classification scheme items, cej , which are children of cei, by using the path enumeration values. 2.3. For each one of the above identified classification scheme items cej : 2.3.1. Create the corresponding ontology class, Cj class. 2.3.2. Using the external resource identify the semantics of the relation between Cj and Ci and set up the relation identified. 2.3.3. Repeat from step 2.2 for cej as a new cei. 3. If there are more than one classification scheme items without parent cei 3.1. Create an ad-hoc class as the root class of the ontology. 3.2. Using the external resource identify the semantics of the relation between Ci class and the root class, and set up the relation identified" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, … |
| Pattern for re-engineering a classification scheme, which follows the path enumeration data model, into an ontology schema + | Some subquery has no valid condition. + |
| Pattern for re-engineering a classification scheme, which follows the path enumeration data model, into an ontology schema + | The wikipage input value "http://ec.europa.eu/eurostat/ramon/nomenclatures/index.cfm?%20TargetUrl=LST_NOM&StrLanguageCode=EN&IntFamilyCode=260276&TxtSearch=" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Pattern for re-engineering a classification scheme, which follows the snowflake data model, into an ontology schema + | Some subquery has no valid condition. + |
| Pattern for re-engineering a classification scheme, which follows the snowflake data model, into an ontology schema + | The wikipage input value "A non-ontological resource holds a classification scheme which follows the snowflake model. A classification scheme is a rooted tree of concepts, in which each concept groups entities by some particular degree of similarity. The semantics of the hierarchical relation between parents and children concepts may vary depending of the context. The snowflake data model is a normalized structure for hierarchy representations. In this case, the classification scheme items are grouped by levels or entities. There are as many groups as levels the classification scheme has." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, The wikipage input value "The generated ontology will be based on the taxonomy architectural pattern (AP-TX-01). Each category in the classification scheme is mapped to a class, and the semantics of the relationship between children and parent categories are disambiguated by using an external resource. In the case of that the external resource does not provide any relation between two items, the pattern takes advantage of the use of logical patterns for asserting the relation partOf or subClassOf." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, The wikipage input value "1. Select all the classification scheme items from the first level. 2. For each one of the above selected classification scheme items cei: 2.1. Create the corresponding ontology class, Ci class. 2.2. Identify the classification scheme items, cej , on the next level, which are children of cei, by using the parent key values. 2.3. For each one of the above identified classification scheme items cej : 2.3.1. Create the corresponding ontology class, Cj class. 2.3.2. Using the external resource identify the semantics of the relation between Cj and Ci, and set up the relation identified. 2.3.3. Repeat from step 2.2 for cej as a new cei. 3. If there are more than one classification scheme items from the first level cei 3.1. Create an ad-hoc class as the root class of the ontology. 3.2. Using the external resource identify the semantics of the relation between Ci class and the root class, and set up the relation identified." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, … |
| Pattern for re-engineering a term-based thesaurus, which follows the recordbased data model, into an ontology schema + | The wikipage input value "1. Identify the records which contain thesaurus terms without a broader term. 2. For each one of the above identified thesaurus terms ti: 2.1. Create the corresponding ontology class, Ci class, if it is not created yet. 2.2. Identify the thesaurus terms, tj , which are narrower terms of ti. They are referenced in the same record which contains ti. 2.3. For each one of the above identified thesaurus term tj : 2.3.1. Create the corresponding ontology class, Cj class, if it is not created yet. 2.3.2. Using the external resource identify the semantics of the relation between Cj and Ci, and set up the relation identified. 2.3.3. Repeat from step 2.2 for cj as a new ci 2.4. Identify the thesaurus terms, tr, which are related terms of ti. They are referenced in the same record which contains ti. 2.5. For each one of the above identified thesaurus terms tr: 2.5.1. Create the corresponding ontology class, Cr class, if it is not created yet. 2.5.2. Using the external resource identify the semantics of the relation between Cr and Ci, and set up the relation identified. 2.5.3. Repeat from step 2.4 for cr as a new ci 2.6. Identify the thesaurus terms, tq, which are equivalent terms of ti. They are referenced in the same record which contains ti. 2.7. For each one of the above identified thesaurus terms tq: 2.7.1. Use the logical pattern proposed by Corcho et al. 2.7.2. Repeat from step 2.6 for cq as a new ci." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, The wikipage input value "A non-ontological resource holds a term-based thesaurus which follows the record-based model. A thesaurus represents the knowledge of a domain with a collection of terms and a limited set of relations between them. The record-based data model is a denormalized structure, uses a record for every term with the information about the term, such as synonyms, broader, narrower and related terms." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +,The wikipage input value "1. Create the learning class and the personal development class. 2. Create the competence class. 3. Using the external resource identify the semantics of the relation between competence and learning, and set up the relation identified. 4. Create the performance class. 5. Using the external resource identify the semantics of the relation between performance and personal development, and set up the relation identified. 6. Assert that achievement is label of the performance class. 7. Using the external resource identify the semantics of the relation between competence and performance, and set up the relation identified. 8. Create the skill class. 9. Using the external resource identify the semantics of the relation between skill and competence, and set up the relation identified. 9.1. Create the efficiency class. 9.2. Using the external resource identify the semantics of the relation between efficiency and performance, and set up the relation identified. 9.3. Create the failure class. 9.4. Using the external resource identify the semantics of the relation between failure and performance, and set up the relation identified. 9.5. Create the success class. 9.6. Using the external resource identify the semantics of the relation between success and performance, and set up the relation identified." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, … |
| Pattern for re-engineering a term-based thesaurus, which follows the recordbased data model, into an ontology schema + | Some subquery has no valid condition. + |
| Pattern for re-engineering a term-based thesaurus, which follows the relationbased data model, into an ontology schema + | Some subquery has no valid condition. + |
| Pattern for re-engineering a term-based thesaurus, which follows the relationbased data model, into an ontology schema + | The wikipage input value "A non-ontological resource holds a term-based thesaurus which follows the relation-based model.
A thesaurus represents the knowledge of a domain with a collection of terms and a limited set of relations between them.
The relation-based data model is a normalized structure, in which relationship
types are not defined as fields in a record, but they are simply data values in a relationship record, thus new relationship types can be introduced with ease." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, The wikipage input value "The generated ontology will be based on the lightweight ontology architectural pattern (AP-LW-01). Each thesaurus term is mapped to a class. For the disambiguation of the semantics of the BT, NT and RT relations among thesaurus terms the pattern relies on an external resource. In the case the external resource does not provide any relation between two terms, the pattern takes advantage of the use of logical patterns for asserting the relation partOf, subClassOf or relatedClass. For the UF/USE relations we use the logical pattern proposed by Corcho et al. suggested as best practice in the context of this antipattern: the tendency to declare two classes equivalent when in fact their labels simply express synonym." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, The wikipage input value "1. Identify the records which contain thesaurus terms without a broader term, within the term-term relationship entity. 2. For each one of the above identified thesaurus terms ti: 2.1. Obtain the thesaurus term within the term entity. 2.2. Create the corresponding ontology class, Ci class, if it is not created yet. 2.3. Identify the thesaurus term, tj, which are narrower terms of ti, within the term-term relationship entity. 2.4. For each one of the above identified thesaurus terms tj : 2.4.1. Obtain the thesaurus term within the term entity. 2.4.2. Create the corresponding ontology class, Cj class, if it is not created yet. 2.4.3. Using the external resource identify the semantics of the relation between Cj and Ci, and set up the relation identified. 2.4.4. Repeat from step 2.2 for cj as a new ci 2.5. Identify the thesaurus term, tr, which are related terms of ti, within the term-term relationship entity. 2.6. For each one of the above identified thesaurus term tr: 2.6.1. Obtain the thesaurus term within the term entity. 2.6.2. Create the corresponding ontology class, Cr class, if it is not created yet. 2.6.3. Using the external resource identify the semantics of the relation between Cr and Ci, and set up the relation identified. 2.6.4. Repeat from step 2.4 for cr as a new ci 2.7. Identify the thesaurus term, tq, which are equivalent terms of ti, within the term-term relationship entity. 2.8. For each one of the above identified thesaurus term tq: 2.8.1. Use the logical pattern proposed by Corcho et al. 2.8.2. Repeat from step 2.6 for cq as a new ci" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, … |
| PeriodicInterval + | The wikipage input value "The class “Interval” defined in the OWL-Time ontol-ogy has been extended within this pattern by means of the class “PeriodicInterval”. This concept has been created in order to define periodic intervals. As we have al-ready mentioned, these intervals are defined by four elements, namely, its beginning, its end, the duration of each subinterval and the duration of the period, that is, the gaps between two subintervals. In order to model the beginning and end of the inter-val, we have reused the relationships “hasBeginning” and “hasEnd” already defined in the OWL-Time ontology. By taking advantage of the concepts and relations al-ready defined in the OWL-Time ontology instead of creating new ones we both pro-mote the reuse of existing models and avoid the inclusion of unnecessary complexity within the pattern being developed. The durations of the subintervals and the period between them have been modelled by means of the relationships “hasIntervalDura-tionPerPeriod” and “hasPeriod” respectively. Both relationships are defined between the concepts “PeriodicInterval” and “DurationDescription”." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| PeriodicInterval + | Some subquery has no valid condition. + |
| Persons + | Some subquery has no valid condition. + |
'Ontology Design Patterns'