Pages using the property "Has processing error text"

Showing 25 pages using this property.

View (previous 25 | next 25) (20 | 50 | 100 | 250 | 500)

E
Enlarge Class Definition for Resolving Disjointness due to Subsomption +The wikipage input value "The application of the pattern to resolve the example above is performed as follow: 1) The pattern enlarges the definition of the sub-class object of the disjointness inconsistency Carnivorous-Plant by defining –in its description– a union of the definitions of the disjoint classes involved in the inconsistency: the classes Animal and Plant." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
EthnicGroup +Some subquery has no valid condition.  +
EventCore +Some subquery has no valid condition.  +
EventCore +The wikipage input value "The purpose of this pattern is to provide a minimalistic model of event where it is not always possible to separate its spatial and the temporal aspects, thus can model events that move or possess discontinuous temporal extent. Events according to this model has at least one participant, attached via a participant-role, and may have additional descriptive information through its information object." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
EventCore +The wikipage input value "This pattern can model moving events and events with discontinuous temporal extents, provided an appropriate spatiotemporal extent model is used. This pattern, however, does not facilitate modeling complex relationships between events, such as causality, provenance, or correlation" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
EventProcessing +Some subquery has no valid condition.  +
EventProcessing +The wikipage input value "To model event objects (in the context of complex event processing), their attributes, and their relations actual events, and sensor readings producing the events. Different types of event objects, such as complex, composite, and simple events are modelled, preoperties for expressing relations between event objects, such as constituency and componency are expressed, and attributes of event objects, such as timestamps and other data values. This pattern is aligned both to the SSN (Semantic Sensor Network) ontology, and the Event-F model, which in turn both use DUL as an upper layer." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
Experience & Observation +The wikipage input value "In what ways can one person be engaged in a single activity? - What personal observations were produced by reflecting upon an activity being carried out? - Which activities performed by someone have prompted an observation from that person and which haven't?" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
Experience & Observation +Some subquery has no valid condition.  +
Experience & Observation +The wikipage input value "Adopting this pattern decomposes the lax notion of experience (e.g. through engaging in reading a book or incidentally hearing some music) into distinguishable elements that can be used in e.g. text annotation with greater precision than with a single named entity representing the experience." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
Experience & Observation +The wikipage input value "to represent the epistemological "missing link" between a cognitive activity, e.g. the interaction with a cultural object, and any evidence of the effects this activity has on the individuals that are engaged with it; what can collectively be considered as an experience." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
ExplanationODP +Some subquery has no valid condition.  +
F
Faceted Classification Scheme +

The wikipage input value "A FCS is defined as: "a set of mutually exclusive and jointly exhaustive categories, each made by isolating one perspective on the items (a facet), that combine to completely describe all the objects in question, and which users can use, by searching and browsing, to find what they need" (Denton, 2003).

The following notation is introduced to refer to the elements of a generic FCS in the figure below:

  • Target Domain Concept (TDC) denotes the domain of discourse. The domain-specific concept targeted by the FCS.
  • Facet_i denotes one of the facets of the FCS.
  • F_iTerm_j denotes one of the terms of Facet_i.
  • Item_x denotes one the items from the domain of discourse (TDC) to be classified." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  +,

The wikipage input value "Generic structure of the Normalization ODP used to represent a Faceted Classification Scheme (FCS).

The symbol (≡) denotes an OWL defined class.

The figure below represents a further generalization of the Normalization ODP and introduces the following notation:

  • :TDC denotes a primitive class representing the domain concept being normalized.
  • :Module_i denotes a primitive class that represents one of the modules.
  • :M_iClass_j denotes a primitive class that represents a subset of the module class :Module_i.
  • :hasModule_i denotes an object property that links every module :Module_i to the different subclasses of the target domain concept :M_iClass_jTDC and :SpecificTDC_x.
  • :M_iClass_jTDC denotes a defined class that represents a subset of the target domain concept class :TDC. Every class :M_iClass_jTDC is defined based on its relationship to the single corresponding class :M_iClass_j that it is derived from.
  • :SpecificTDC_x denotes a primitive class that represents a subset of the target domain concept class :TDC and an entity from the domain to be classified. Every class :SpecificTDC_x is described based on its relationship to various classes :M_iClass_j from potentially different modules. As a consequence of this relationship, the classes :SpecificTDC_x could introduce the polyhierarchy scenarios in the ontology model that the Normalization ODP aims to manage and untangle.

The implementation of a generic defined class :M_iClass_jTDC is given as follows:

:M_iClass_jTDC rdf:type owl:Class ;
               rdfs:subClassOf :TDC ;
               owl:equivalentClass [ rdf:type owl:Restriction ;
                                     owl:onProperty :hasModule_i ;
                                     owl:someValuesFrom :M_iClass_j
                                   ] .

The implementation of a generic class :SpecificTDC_x is given as follows:

:SpecificTDC_x rdf:type owl:Class ;
               rdfs:subClassOf :TDC ,
                               [ rdf:type owl:Restriction ;
                                 owl:onProperty :hasModule_i ;
                                 owl:someValuesFrom :M_iClass_j
                               ] ,
                               [ ... rest of existential restrictions on property :hasModule_i
                                     for every class :M_iClass_j that participates
                                     in the description of :SpecificTDC_x
                               ] .

This implementation of the classes :M_iClass_jTDC and :SpecificTDC_x respectively, enable a reasoner to infer and maintain the subsumption relations between a given class :SpecificTDC_x and the various classes :M_iClass_jTDC that it is related to." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.

  +,

The wikipage input value "Mapping between the elements in the generic structure of a Faceted Classification Scheme and the Normalization ODP.

The table below summarizes the alignment of the elements in the generic structure of both conceptual models. This alignment enables the conversion from a FCS to an OWL DL ontology by applying the Normalization ODP:

  • The first column (leftmost), contains the elements of a generic FCS as introduced in section Non-Ontological Resource above.
  • The second column contains the elements of the Normalization ODP generic structure

as introduced in section Ontology above.

  • The third column represents the selected OWL notation for the elements of a generic FCS in the context of the Normalization ODP generic structure.
  • The forth column (rightmost), indicates the OWL implementation chosen for every element. The selection complies with the requirements of the normalization mechanism.
MappingFCSNormalizationODP.png

Based on the principle of representating each facet of a FCS as a module of the Normalization ODP, the underlying ideas behind the mappings in the figure(table) above can be outlined as follows:

  • The target domain concept TDC represents the domain of discourse of both a FCS and the Normalization ODP. The primitive class :TDC fulfills that role in the normalized ontology.
  • A facet Facet_i from a generic FCS corresponds to a module :Module_i in the Normalization ODP, therefore it becomes a primitive class :Facet_i in the normalized ontology model.
  • A facet Facet_i from a FCS also becomes an object property :hasFacet_i in the normalized ontology, given that for every module :Module_i in the Normalization ODP, there is an object property :has_Module_i.
  • From the relationship between facet and module, it follows that a facet term F_iTerm_j from a FCS maps to a module subclass :M_iClass_j from the Normalization ODP. Both elements represents the same notion in their respective conceptual models. A subvidision, a refinement of the facet or module that they complement respectively. Therefore, a facet term F_iTerm_j from a FCS becomes a primitive class :F_iTerm_j in the normalized ontology.
  • A facet term F_iTerm_j from a FCS also produces a defined class :F_iTerm_jTDC in the normalized ontology, given that for every primitive class :M_iClass_j in the Normalization ODP, there is a corresponding defined class :M_iClass_jTDC.
  • Every item Item_x to be classified in the FCS aligns to a class :Specific_x that is automatically classified by a reasoner in the Normalization ODP. Therefore, every element Item_x is represented as a primitive class :SpecificTDC_x in the normalized ontology." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  +,
Faceted Classification Scheme +The wikipage input value "Community:Faceted Classification Scheme|Faceted Classification Scheme]] (FCS)" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
Faceted Classification Scheme +Some subquery has no valid condition.  +
G
GO Top +The wikipage input value "It allows to categorize gene-related types into three main types. It allows to represent parts of gene-related entities (transitively). It does not allow to represent the relationships between entities of different types. It does not say anything about disjointness of categories." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
GO Top +Some subquery has no valid condition.  +
GearSpecies +The wikipage input value "The pattern outlines the relations between aquatic species and types of fishing gear that are suitable for catching exemplars thereof. While we do not make this distinction from the species' viewpoint, we do distinguish what species are gear types targeted to and what can be also incidentally caught. Since the original model does not hint at any other possible use for the three object properties presented herein, restriction superclasses for domains and ranges have been refactored as domain and range axioms for said properties. Note that this pattern can also be combined with :gearvessel.owl for answering what species can be caught using what vessel types. This can be inferred transitively." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
GearSpecies +Some subquery has no valid condition.  +
GearVessel +The wikipage input value "This is a straightforward pattern that describes vessel types in terms of the fishing gear they can be equipped with. The original usesGearType object property has been reworked, in that subclass restrictions for affected classes have been replacd with domain and range axiom. This also allows the definition of inverse property usedByVesselType." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
GearVessel +Some subquery has no valid condition.  +
GearWaterArea +The wikipage input value "The relation between gear types and water areas is general, i.e. not expressed in terms of logistics, legal constraints etc. Note that no statement is made as for the domain of the hasWaterArea property, as it applies to both GearType and VesselType in other patterns, and in principle could apply to other entities. Hence the domain is expressed through superclass universal restrictions on the GearType class." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
GearWaterArea +Some subquery has no valid condition.  +
Gesture Interaction +Some subquery has no valid condition.  +
Gesture Interaction +

The wikipage input value "The Gesture Interaction Pattern aims to model the pose and movement of human body that are used to interact with devices (particularly with device affordances). This helps to describe a human gesture with its relationship between certain device affordances, related body parts and the temporal components associated with those.

This might be helpful in creating user specific gesture profiles. This ontology pattern is geared at mapping the ubiquitousness in gesture vocabularies by linking them appropriately and does not enforce designers and manufacturers to follow a standard." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.

  +
The page [[Bootstrap:Footer]] was not found.