Showing 25 pages using this property.
D | |
|---|---|
| DigitalVideo + | The wikipage input value "The pattern’s main entity is a digital video file (DigitalVideo). Appropriate object properties connect the video file with codecs, streams, containers, etc. Additionally, the model includes the most significant descriptors for all the previous notions, such as bitrate, aspect ratio, compression type, etc." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| DigitalVideo + | Some subquery has no valid condition. + |
| DigitalVideo + | The wikipage input value "What does a digital video file consist of? A digital video file usually consists of one or more streams. These streams are compressed using codecs (coder-decoder) and wrapped into a container.
|
| DigitalVideo + | The wikipage input value "The pattern intends to model digital video files, their components and other associated entities, such as codecs and containers. This pattern has been developed by MKLab at CERTH/ITI for the PERICLES FP7 project." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| DigitalVideo + | The wikipage input value "
|
| Disjoint Classes + | The wikipage input value "Example in EDOAL, the expressive and declarative ontology alignment language <Cell> <entity1><Class rdf:about="O1:Top"/></entity1> <entity2><Class rdf:about="O2:Top"/></entity2> <relation>Disjoint</relation> </Cell>" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.+ |
| Disjoint Classes + | The wikipage input value "Two classes have a different intension, and no intersection of their extension. Specifying a disjoint correspondence may help a matcher in not proposing any correspondences between these classes." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Disjoint Classes + | Some subquery has no valid condition. + |
| DisjointnessOfComplement (DOC) + | The wikipage input value "C1 isEquivalentTo not C2 should be replace by C1 disjointWith C2" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| DisjointnessOfComplement (DOC) + | The wikipage input value "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. As aforementioned 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. + |
| DisjointnessOfComplement (DOC) + | Some subquery has no valid condition. + |
| DisjointnessOfComplement (DOC) + | The wikipage input value "Salt_Lagoon isEquivalentTo not Fresh_Waters see concept Laguna_Salada in Hydrontology" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Disposition + | The wikipage input value "a dose of penicilin can unfold its antibiotic disposition when being swallowed) What is the realization of a given disposition? (e.g." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Disposition + | Some subquery has no valid condition. + |
| Disposition + | The wikipage input value "Relations are being defined between dispositions, their realizations processes and their triggering processes. The pattern is easily compatible with many top-level ontologies. In this description, we use classes from BFO and BioTop. References: - Roehl/Jansen: "Representing Dispositions", Journal of Biomedical Semantics 2011, 2(Suppl 4):S4 (9 August 2011). - BioTop, http://www.imbi.uni-freiburg.de/ontology/biotop/." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
E | |
| EEP + | The wikipage input value "To represent executions made by executors that implement procedures. Executions are events like observations or actuations. Executors are systems like sensors or actuators that produce executions. Executors implement procedures to carry out their goals. Executions and executors are taken over features of interest and their intrinsic properties/qualities." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| EEP + | Some subquery has no valid condition. + |
| EEP + | The wikipage input value "Axioms included in the EEP ODP provide inferences that allow to answer the competency questions properly. Therefore, solving some weaknesses of the sosa/ssn ontologies. Note that only triples about the four functional object properties: eep:madeBy, eep:usedProcedure, eep:onQuality, and aff:belongsTo, needs to be asserted, the remaining triples are inferred by the property axioms." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| EEP + | The wikipage input value "The Execution-Executor-Procedure (EEP) ODP imports the AffectedBy ODP (https://w3id.org/affectedBy), that involves classes for Features of Interest and their intrinsic Properties/Qualities. The EEP ODP is an adaptation of the Procedure Execution Ontology (PEP) (https://w3id.org/pep/pep-1.1) from the SEAS ontology which, in turn, is a generalization of the Observation-Sensor-Procedure and Actuation-Actuator-Procedure patterns used in the SOSA (http://www.w3.org/ns/sosa/) and SSN (http://www.w3.org/ns/ssn/) ontologies. From the AffectedBy ODP, the EEP ODP imports the notion that a property/quality is intrinsic to the feature of interest that it belongs to (i.e., according to the definition of the class Quality in the DUL ontology http://www.ontologydesignpatterns.org/ont/dul/DUL.owl). Apart from the two classes imported from the AffectedBy ODP (aff:FeatureOfIntetest and aff:Quality), the EEP ODP consists of three more classes: Execution, Executor, and Procedure. The class Execution and their three functional object properties eep:madeBy, eep:usedProcedure, and eep:onQuality, form the backbone of the ODP. The property eep:madeBy links an execution to its executor, the property eep:usedProcedure links an execution to its procedure, and the property eep:onQuality links an execution to the quality/property concerned by the execution. Therefore, an execution jointly with their three object values of the three aforementioned properties can be considered as a n-ary relationship. Note that every quality belongs to unique feature of interest. Therefore, a feature of interest is involved in the n-ary relationship. The remaining object properties: eep:implements, that links executors to procedures, eep:hasFeatureOfInteres, that links executions to features of interest, eep:forQuality, that links executors to qualities, and eep:forFeatureOfInterest, that links executors to features of interest, are defined in terms of the functional object properties using property chain axioms." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Enlarge Class Definition for Resolving Disjointness due to Subsomption + | 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. + |
| Enlarge Class Definition for Resolving Disjointness due to Subsomption + | The wikipage input value "the following elements are manipulated by the pattern: ID of the sub-class to enlarge (Sub_Class). ID of the first disjoint class (Disjoint_Class 1). ID of the second disjoint class (Disjoint_Class 2)." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Enlarge Class Definition for Resolving Disjointness due to Subsomption + | 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. + |
| Enlarge Class Definition for Resolving Disjointness due to Subsomption + | Some subquery has no valid condition. + |
| Enlarge Class Definition for Resolving Disjointness due to Subsomption + | The wikipage input value "The pattern resolves a disjointness inconsistency –caused by a subsumption– by enlarging the definition of the sub-class object of the disjointness inconsistency, based on the definition of the involved disjoint classes. The definition of the sub-class is enlarged by 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 enlarges the definition of the sub-class object of the disjointness inconsistency by defining –in its description– a union of the definitions of the disjoint classes involved in the inconsistency to be resolved." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. + |
| Enlarge Class Definition for Resolving Disjointness due to Subsomption + | 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. + |
'Ontology Design Patterns'