Showing 25 pages using this property.
N | |
|---|---|
| NewsReportingEvent + | The wikipage input value "The pattern can be used for modelling situations in which we are not certain that a particular actual event has the properties which were described in a news message. We want to define the properties of an actual event which were reported (time, place, actors, subevents, cause, effect etc.), but not to treat them as universal, verified knowledge. The pattern also allows to define who is responsible for a particular description of an event and how this description is dealt with." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| NewsReportingEvent + | The wikipage input value "The pattern extends the ReportingEvent pattern by specifying the primary properties of the specialisation of the ReportingEvent class. The specialisation, NewsReportingEvent, denotes the act of providing a unit of information (ActualEventView) to the general public. The act utilises a certain Media (TV station, radio station, newspaper, website). A Media is owned by a certain SocialAgent - NewsProvider. This agent takes partial responsibility for the content provided, but its responsibility differs from the one of the NewsEventReporter, an Agent that directly reports the ActualEvent. Other properties which are very important for a NewsReportingEvent are time at which the event is reported and the context of presentation." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Normalization + | The wikipage input value "Image:Normalisation_instance.png|center" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Normalization + | Some subquery has no valid condition. + |
| Normalization + | The wikipage input value "There are ontologies where a given class can have plenty of superclasses, building a polyhierarchy. If all those subsumption relationships are directly stated by the ontology maintainer, two main problems rise: (i) the ontology becomes very difficult to maintain: whenever a subsumption must be deleted (because a class has changed) or created (because a new class has been created) it has to be done by hand; in a polyhierarchy the process becomes very inefficient and error-prone. (ii) the semantics are implicitly stated, not explicitly: any other ontologist or reasoner only knows that a class is a subclass of its superclasses, without knowing why." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Normalization + | The wikipage input value "See [[Community:References/Modularisation of domain ontologies implemented in description logics and related formalisms including owl 3|(Rector, 2003)" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Normalization + | The wikipage input value "To untangle a polyhierarchy, coding the subsumption relationships using restrictions rather than class-subclass relationships. The application example for this ODP is adapted from the Cell Type Ontology. In the example, the subsumption relationships that already are in the Cell Type Ontology are inferred by the reasoner instead of hard-coded. The term Neutrophil is used as an example class to show how a class can relate to different modules." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Normalization + | The wikipage input value "The original classes of the ontology are divided in different axes. The conditions for each subsumption relationship are encoded as restrictions (e.g. [PerformsFunction some Defense]) that will relate the different modules." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Normalization + | The wikipage input value "Identify the modules: group the classes. Create the modules, maintaining only one parent for any given primitive class and making primitive siblings disjoint. Redefine the classes (or define the newly added classes) according to the conditions for belonging to each module. Protege includes a wizard, the restrictions matrix, that helps in the process." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Normalization + | The wikipage input value "See [[Community:References/Modularisation of domain ontologies implemented in description logics and related formalisms including owl 3|(Rector, 2003)" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
O | |
| OOPMetrics + | The wikipage input value "To represent software metrics especially for the purpose of detecting design-flaws in software systems based on these metrics. This is useful for re-engineering the software system., De a reprezenta metricile soft in special in scopul detectarii defectelor de proiectare din sistemele soft pe baza acestor metrici. Acest lucru este folositor pentru reingineria sistemului soft." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| OOPMetrics + | The wikipage input value "What are the software metrics for a particular project/package/class/method? Knowing the software metrics" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. +, The wikipage input value "Care sunt metricile soft pentru un anumit proiect/pachet/clasa/metoda? Cunoscand metricile soft" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| OOPMetrics + | Some subquery has no valid condition. + |
| Object with states + | The wikipage input value "The pattern contains three classes, one for representing objects, another for representing object states, and a third one for representing sets of states. Besides, it contains object properties for relating objects and states (which are subproperties of those defined in the Situation pattern [[1]]) and for relating states and sets of states (reused from the CollectionEntity pattern [[2]]) and a datatype property for defining the size of a set of states (reused from the Set pattern [[3]]). For applying the pattern, first all the possible states of the object must be created as instances of the state class using the Value Partition pattern [4]. Then, different classes must be defined to represent the object in each of the states and state-specific restrictions must be applied to those classes; the object class must be defined as a disjoint union of these classes." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Object with states + | Some subquery has no valid condition. + |
| Objectrole + | The wikipage input value "it is possible to make assertions about roles, which are typically considered at the meta- level of an ontology. Instances of Submissions:Objectrole/Role reify such elements, which are therefore put in the ordinary domain of an ontology. It is not possible to parametrize the classification over different dimensions e.g., time, space, etc." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Objectrole + | Some subquery has no valid condition. + |
| Observation + | Some subquery has no valid condition. + |
| OnlynessIsLoneliness (OIL) + | Some subquery has no valid condition. + |
| OnlynessIsLoneliness (OIL) + | The wikipage input value "Transtitional_Waters subClassOf is_nearby only (Sea_Waters or River_Mouths); River_Mouths disjointWith Sea_Waters Wet_Zone subClassOf Wetlands and are_inundated only (Sea_Water or Surface_Water) and are_inundated min 1 Thing;" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| OnlynessIsLoneliness (OIL) + | The wikipage input value "Our work is based on the debugging process of real ontologies that have been developed by domain experts, who are not necessarily too familiar with DL, and hence can misuse DL constructors and misunderstand the semantics of some OWL expressions, leading to unwanted unsatisfiable classes. Our patterns were first found during the debugging process of a medium-sized OWL ontology (165 classes) developed by a domain expert in the area of hydrology called HydrOntology. The first version of this ontology had a total of 114 unsatisfiable classes. The information provided by the debugging systems used on (root) unsatisfiable classes was not easily understandable by domain experts to find the reasons for their unsatisfiability. And in several occasions during the debugging process the generation of justifications for unsatisfiability took several hours, what made these tools hard to use. Using this debugging process and several other real ontologies debugging one, we found out that in several occasions domain experts were just changing axioms from the original ontology in a somehow random manner, even changing the intended meaning of the definitions instead of correcting errors in their formalisations. We have identified a set of patterns that are commonly used by domain experts in their DL formalisations and OWL implementations, and that normally result in unsatisfiable classes or modelling errors. Thus they are antipatterns. A Koenig define antipatterns as patterns that appear obvious but are ineffective or far from optimal in practice, representing worst practice about how to structure and build software. We also have made an effort to identify common alternatives for providing solutions to them, so that they can be used by domain experts to debug their ontologies. All these antipatterns come from a misuse and misunderstanding of DL expressions by ontology developers. Thus they are all Logical AntiPatterns (LAP): they are independent from a specific domain of interest, but dependent on the expressivity of the logical formalism used for the representation." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| OnlynessIsLoneliness (OIL) + | The wikipage input value "Transtitional_Waters subClassOf is_nearby only Sea_Waters; Transitional_Waters subClassOf is_nearby only River_Mouths; River_Mouths disjointWith Sea_Waters see Aguas_de_Transicion concept in hydrontology. Wet_Zone subClassOf Wetlands and are_inundated only Sea_Water and are_inundated only Surface_Water and are_inundated min 1 Thing; see Zona_Humeda concept in hydrontology." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| OnlynessIsLoneliness (OIL) + | The wikipage input value "The ontology developer created a universal restriction to say that C1 instances can only be linked with property R to C2 instances. Next, a new universal restriction is added saying that C1 instances can only be linked with R to C3 instances, with C2 and C3 disjoint. In general, this is because the ontology developer forgot the previous axiom in the same class or in the parent class." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| OnlynessIsLoneliness (OIL) + | The wikipage input value "C1 subClassOf R only C2; C1 subClassOf R only C3; C2 disjointWith C3 If it makes sense, we propose to the domain expert to transform the two universal restrictions into only one that refers to the disjunction of C2 and C3. C1 subClassOf R only (C2 or C3); C2 disjointWith C3 other alternative solutions could be: 1) suppress the disjointness axiom. 2) create two sublass of C1 such as: C1.1 subClassOf C1; C1.1 subClassOf R only C2; C1.2 subClassOf C1; C1.2 subClassOf R only C3; C2 disjointWith C3; 3) create C4 such as C4 isEqualTo C2 or C3; C1 subClassOf R only C4; C2 disjointWith C3. 4) create two subproperty of R: R2 subPropertyOf R; R3 subProperty of R; C1 subClassOf R2 only C2; C1 subClassOf R3 only C3; C2 disjointWith C3." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
P | |
| Parameter + | Some subquery has no valid condition. + |
'Ontology Design Patterns'