Showing 25 pages using this property.
C | |
|---|---|
| Course + | Some subquery has no valid condition. + |
| Create Disjoint Siblings + | Some subquery has no valid condition. + |
| Criterion + | Some subquery has no valid condition. + |
| CriterionS + | Some subquery has no valid condition. + |
| CriterionSetter + | The wikipage input value "This is a specialization of criterion pattern. The criterion setter can be used as an abstract container for requirements, recommendations, constraints etc. The owl file linked below contains a simple example of how this pattern could be implemented for modeling a requirement (see 'Examples')." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| CriterionSetter + | Some subquery has no valid condition. + |
| CriterionSetter + | The wikipage input value "The purpose of this pattern is to provide a broader context for criteria modeling. Possible specializations could introduce new kinds of criteria setters representing criteria in detailed contexts (for example: a pattern for describing the success/failure condition for some actions). Possible criteria setters may include requirements, recommendations, constraints etc." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| CyclicSubClassOf + | Some subquery has no valid condition. + |
| CyclicSubClassOf + | The wikipage input value "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." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| CyclicSubClassOf + | The wikipage input value "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)" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +,The wikipage input value "Replacing the cyclic SubClassOf chain with an EquivalentClassesAxiom: EquivalentClasses( A C1 C2 C3 ... Cn)" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
D | |
| DataTransformationPattern + | Some subquery has no valid condition. + |
| Define Hybrid Class Resolving Disjointness due to Subsumption + | Some subquery has no valid condition. + |
| Define Hybrid Class Resolving Disjointness due to Subsumption + | The wikipage input value "Problem : This pattern helps resolving a logical inconsistency triggered by a situation of disjoint classes subsuming a common sub-class. When we need to define – for some modeling issues related to domain of interest – a class as a sub-class of two disjoint classes, a disjointness inconsistency is caused. The problem can be illustrated by the following scenario: let’s consider a class Sub_Class defined as a sub-class of a class Disjoint_Class 2; and a class Disjoint_Class 1 disjoint with the Disjoint_Class 2 (see diagram in attached file). If we need to add a sub-class relation between the Sub_Class and the Disjoint_Class 1, this generates a disjointness inconsistency: - If the extension of the Sub_Class contains individuals instantiating this sub-class, the logical inconsistency will be extended to the knowledge base; - If the Sub_Class is not instantiated to individuals, it will be diagnosed as an unsatisfiable class. To solve this inconsistency, one can think about deleting the disjointness axiom. However, this can alter the semantics expressed in the ontology, and negatively affect consistency checking and automatic evaluation of existing individuals as explained in [1]. This pattern tackles the questions of how to resolve the inconsistency caused by such kind of subsumption while preserving existing knowledge. [1] Völker, J., Vrandecic, D., Sure, Y., Hotho, A.: Learning Disjointness. In F., Enrico, K., Michael, May. Wolfgang (Eds.). Proceedings of the 4th European Semantic Web Conference, ESWC 2007. LNCS: Vol. 4519 pp: 175-189. (2007)" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Define Hybrid Class Resolving Disjointness due to Subsumption + | The wikipage input value "Intent: The purpose of this pattern is to support the semantics of a subsumption defined under two disjoint classes and resolve the resulting inconsistency. Covered Requirements: The pattern solves a problem of disjointness inconsistency caused by a subsumption relation without deleting the disjointness axiom so that existing knowledge can be preserved." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Define Hybrid Class Resolving Disjointness due to Subsumption + | The wikipage input value "The pattern resolves a disjointness inconsistency –due to a subsumption–by defining a Hybrid Class based on the definition of disjoint classes implicated in the inconsistency; and redistributing correctly sub-class relations between the sub-class, the hybrid class, and the most specific common super-class of the disjoint classes implicated. The definition of the Hybrid Class is the union (OR) of the definitions of the disjoint classes. The application of the solution can be described by the following process (see diagram in attached file): 1.The pattern defines a Hybrid Class as a union of the definitions of the disjoint classes implicated in the inconsistency to be resolved; 2.The pattern defines a subsumption between the most specific common super-class of the disjoint classes implicated in the inconsistency, and the Hybrid Class created; 3.The pattern defines a subsumption between the Hybrid Class and the sub-class involved in the inconsistency. Consequences: The application of the pattern resolves the disjointness inconsistency (even if the involved sub-class is instantiated by individuals) and preserves existing knowledge. As a Logical OP, this pattern is independent from a specific domain of interest. However, it depends on the expressivity of the logical formalism used for the representation of the ontology. Therefore, the language of the targeted ontology should allow expressing class union." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Define Hybrid Class Resolving Disjointness due to Subsumption + | The wikipage input value "The application of the pattern to resolve the example above is performed as follow: 1.The pattern defines a class Animal_Plant as a union of the definitions of the disjoint classes Animal and Plant; 2.The pattern defines a subsumption between the most specific common super-class of the disjoint classes Fauna-Flora and the hybrid class created Animal_Plant; 3.The pattern defines a subsumption between the defined hybrid class Animal_Plant and the sub-class Carnivorous-Plant involved in the inconsistency." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Define Hybrid Class Resolving Disjointness due to Subsumption + | The wikipage input value "The following elements are manipulated by the pattern: ID of the sub-class (Sub_Class). ID of the first disjoint class (Disjoint_Class 1). ID of the second disjoint class (Disjoint_Class 2). ID of the most specific common super-class of the disjoint classes involved (Common_Super_Class)." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Define Hybrid Class Resolving Disjointness due to Subsumption + | The wikipage input value "Let’s consider the OWL ontology O defined by the following axioms: {Animal ⊑Fauna-Flora, Plant ⊑Fauna-Flora, Carnivorous-Plant ⊑Plant, Plant ⊑ Not(Animal)} If we apply a change to the ontology defining Carnivorous-Plant class as a sub-class of the class Animal, we cause a disjointness inconsistency. The proposed pattern resolves this kind of inconsistency." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Description + | Some subquery has no valid condition. + |
| Description in Range + | Some subquery has no valid condition. + |
| DescriptionAndSituation + | Some subquery has no valid condition. + |
| DetectorFinalState + | The wikipage input value "Retrieve all analyses that veto extra leptons. Retrieve all analyses that used jets in the final state. Retrieve all analyses requireing particles to have an invariant mass near the Z pole. Retrieve all analyses requiring large missing energy." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| DetectorFinalState + | The wikipage input value "This pattern represent schematic model for data obtained from results of high-energy physics experiments, such as ones ran in the CERN's Large Hadron Collider. Specifically, this pattern models the notion of Detector Final State, a composition obatined by a selection of some target characteristics concerning physics measurements and parameters of experiments." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| DetectorFinalState + | Some subquery has no valid condition. + |
| Device-Interface-Link Pattern + | Some subquery has no valid condition. + |
'Ontology Design Patterns'