Pages using the property "Has processing error text"

Showing 25 pages using this property.

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

T
Trajectory +The wikipage input value "The pattern provides a model of trajectory, which is understood as a sequence of spatiotemporal points. The model generalizing the Semantic Trajectory pattern from [Hu, et al., COSIT 2013] by employing the notion of place, instead of location/geo-coordinate, to represent the spatial extent of the trajectory. This pattern is suitable for a variety of trajectory datasets and easily extendible by by aligning to or matching with existing trajectory ontologies, foundational ontologies, or other domain specific vocabularies." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
Trajectory +Some subquery has no valid condition.  +
Trajectory +The wikipage input value "This pattern is reengineered from [Hu, et al., COSIT 2013] with changes as described in the intent of the pattern." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
Trajectory +The wikipage input value "Unlike the original version of Semantic Trajectory, this pattern omits the hook to the data source for fixes (which was a subclass of ssn:Device) because instead of location/geo-coordinate, the notion of place is employed to capture the spatial extent. Nevertheless, it should be relatively straightforward to extend this version if the user wishes to attach data source information to the fixes." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
Trajectory +The wikipage input value "Yingjie Hu; Krzysztof Janowicz; David Carral; Simon Scheider; Werner Kuhn; Gary Berg-Cross; Pascal Hitzler; Mike Dean; Dave Kolas: A Geo-ontology Design Pattern for Semantic Trajectories. In International Conference on Spatial Information Theory (COSIT) 2013) 438-456" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
Transition +The wikipage input value "This pattern composes the Time-indexed participation, Region, and Sequence patterns in order to represent changing of states for objects, fired by some event, through an underlying process." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
Transition +The wikipage input value "We are able to represent part of the semantics involved in transitions (e.g. what is implied by Petri Nets): initial and final states, causal events, underlying processes, affected objects, and sequences of time intervals for situations and events. However, it is not possible to define axioms for automatically infer initial and final states from time sequences, because coreference is not allowed in OWL (not even in OWL2)." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
Transition +Some subquery has no valid condition.  +
TransportPattern +The wikipage input value "What is the extent of a point source pollution event? Where was a package shipped from and where was it shipped to?" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
TransportPattern +The wikipage input value "The rive water was polluted from effluent near a large factory. A package left Auckland, New Zealand, at 5:45am on 01/06/2012 and arrived in Los Angeles, USA, on 01/12/2012." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
TransportPattern +Some subquery has no valid condition.  +
Tree Pattern +The wikipage input value "Trees - i.e., the type of data structure known under this name - are central to many aspects of knowledge organization. We investigate some central design choices concerning the ontological modeling of such trees. In particular, we consider the limits of what is expressible in the Web Ontology Language, and provide a reusable ontology design pattern for trees." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
Tree Pattern +Some subquery has no valid condition.  +
Types of entities +Some subquery has no valid condition.  +
V
VerticalDistribution +The wikipage input value "This pattern only allows to query what vertical distribution is typical of an aquatic resource. Whereas such values can be subject to observation, another pattern based on the generic 'observation' pattern should be used. The vertical distribution is intended to have a fixed set of values (to be defined as nominals) but this is not explicit in the pattern." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
VerticalDistribution +Some subquery has no valid condition.  +
VesselSpecies +The wikipage input value "This pattern should be used in scenarios where a VesselType can be deemed suitable for catching some AquaticSpecies for reasons other than mounting some fishing gear of a suitable GearType. It is strictly related to the gearspecies pattern, in that it uses the catchesSpecies and isCaught property pair to define this behaviour. For the sake of reuse, no domain is declared for catchesSpecies, appropriate restrictions having beed applied instead." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
VesselSpecies +Some subquery has no valid condition.  +
VesselWaterArea +The wikipage input value "The pattern can be used to represent a water area setting and the vessels that can be used there, no matter whether these constraints are legal or logistic. The hasWaterArea object property is used as in the gearwaterarea pattern. Usage of this property as applied to VesselTypes is related to, but not strictly dependent on the hasWaterArea property as applied to GearTypes." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.  +
VesselWaterArea +Some subquery has no valid condition.  +
View Inheritance +

The wikipage input value "Introduce the following types of classes:

  • Criterion_i: These classes represent each one of the alternative abstraction criteria of the TargetDomainConcept (Criterion1, Criterion2, Criterion_i in the Figure above). The list of classes may not be exhaustive or pairwise disjoint.
  • Ci_Class_x: These classes refine each abstraction criteria class (C1_Class1, ..., C2_Class1, ..., Ci_Class_i in the Figure above). The list of classes may not be exhaustive or pairwise disjoint.
  • CiClass_xCjClass_y, Ci_Class_xClass_y: These classes participate in multiple inheritance relationships combining different refinements from the alternative abstraction criteria classes (C1Class3_C2Class2 and C1_Class1Class2 in the Figure above)." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  +
View Inheritance +

The wikipage input value "Inter- and Intra-criterion Multiple Inheritance. There is an interesting feature regarding the types of multiple inheritance relations that can take place in the context of a View Inheritance pattern. These types of multiple inheritance relationships can be characterized as:

  • Inter-criterion, when the parent classes involved in the multiple inheritance relation are subclasses of different abstraction criteria. The class C1Class3_C2Class2 in Figure 1 is an example of this type of inheritance because one of its parent classes, C1_Class3, is a refining concept of Criterion1 and the other parent class, C2_Class2, is a refining concept of Criterion2.
  • Intra-criterion, when the parent classes involved in the multiple inheritance relation are subclasses of the same abstraction criterion. The class C1_Class1Class2 is an example of this type of inheritance because all of its parents classes, C1_Class1 and C1_Class2, are refining concepts of the same criterion, Criterion1.
  • Intra- and inter-criterion, when there are at least two parents involved in the relation that are subclasses of the same abstraction criterion and there is at least one more different parent that is a subclass of a different abstraction criterion. An example of this type of inheritance is trivial to extrapolate from the composition of the previous two." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  +
View Inheritance +Some subquery has no valid condition.  +
View Inheritance +

The wikipage input value "List of figures:

  • Figure 2. The elementary classes of Fault in Avizienis et al. '"`UNIQfa9ca9ed8ad3a16a-nowiki-00000000-QINU`"' used in the ReSIST KB ontology.
  • Figure 3. Matrix representation of Fault in Avizienis et al. '"`UNIQfa9ca9ed8ad3a16a-nowiki-00000001-QINU`"' used in the ReSIST KB ontology." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  +,

The given value "List of figures:

  • Figure 2. The elementary classes of Fault in Avizienis et al. '"`UNIQfa9ca9ed8ad3a16a-nowiki-00000000-QINU`"' used in the ReSIST KB ontology.
  • Figure 3. Matrix representation of Fault in Avizienis et al. '"`UNIQfa9ca9ed8ad3a16a-nowiki-00000001-QINU`"' used in the ReSIST KB ontology." contains strip markers and therefore it cannot be parsed sufficiently.
  +
View Inheritance +

The wikipage input value "Figure above in particular, shows a matrix representation of all types of faults which may affect a system during its life. Implicitly, the figure reveals several alternative criteria for the classification of faults:

  • A first criterion can be derived from the left column of the matrix (listing the basic view points from Figure 2: Development/Operational Faults, Internal/External Faults and so on). This column represents the values of the eight basic viewpoints which lead to the elementary fault classes.
  • A second criterion can be abstracted from the bottom row (listing numbers 1 to 31). This row represents the 31 likely combinations of fault classes out of the 256 possible.
  • A third criterion is implicit at the top row, representing the three major partially overlapping groupings of faults: Development, Physical and Interaction.
  • A fourth criterion can be seen at the bottom row, labeled Examples, containing nine illustrative examples of fault classes." 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.