PREFIX rdf: PREFIX rdfs: PREFIX xsd: a rdfs:Class ; rdfs:label "Measure" ; rdfs:comment """Scaled number\r \r This is an abstract class, which should be substituted by a suitable concrete representation of a measure or quantity at run-tme. \r \r oml:SimpleMeasure \r qudt:QuantityValue \r DUL:Region \r \r are candidates. """ . a rdfs:Class ; rdfs:label "Simple measure (quantity)" ; rdfs:comment "Simple implementation of a scaled number as an (amount, unit) pair" ; rdfs:subClassOf . a rdf:Property ; rdfs:label "numeric amount value" ; rdfs:domain ; rdfs:range xsd:double . a rdf:Property ; rdfs:comment "Unit of measure or scale" ; rdfs:range . a rdfs:Class ; rdfs:label "Temporal Observation"@en ; rdfs:comment "Observation whose result is a temporal object, such as a time instant or period" ; rdfs:subClassOf . a rdf:Property ; rdfs:label "observed property"@en ; rdfs:comment """The association Phenomenon shall link the OM_Observation to the GF_PropertyType for which the OM_Observation:result (7.2.2.9) provides an estimate of its value. The property type has the role observedProperty with respect to the observation.\r \r The observed property shall be a phenomenon associated with the feature-of-interest.\r \r An observed property may be, but need not be, modelled as a property (in the sense of the General Feature Model) in a formal application schema that defines the type of the feature-of-interest.\r \r An instance of GF_PropertyType shall describe a property that is either assignable or observable (7.1.2), such as “temperature”, “height”, “colour”, “material”. A property type may be an operation or function such as a spatiotemporal coverage. Property-type definitions may be organized into a hierarchy or ontology and managed in a register and catalogued to support discovery functions. The observed property supports semantic or thematic classification of observations, which is useful for discovery and data fusion.\r \r NOTE In general, the value of a specific observedProperty can be associated with different feature types in different observations, thus allowing the results of observations made in different projects or campaigns, and even from different disciplines, to be combined when required. A property-type register used in observations is most useful if each property type is not tied to a single feature type, or if equivalence relationships between similar property types from different feature types are provided.""" ; rdfs:range . a rdf:Property ; rdfs:label "phenomenon time"@en ; rdfs:comment """The attribute phenomenonTime:TM_Object shall describe the time that the result (7.2.2.9) applies to the property of the feature-of-interest (7.2.2.7). This is often the time of interaction by a sampling procedure (9.1.3) or observation procedure (7.2.2.10) with a real-world feature.\r \r NOTE The phenomenonTime is the temporal parameter normally used in geospatial analysis of the result.\r \r If the observedProperty of an observation is ‘occurrence time’ then the result should be the same as the phenomenonTime.""" ; rdfs:range . a rdf:Property ; rdfs:label "observation procedure"@en ; rdfs:comment """The association ProcessUsed shall link the OM_Observation to the OM_Process (7.2.3) used to generate the result. The process has the role procedure with respect to the observation. A process might be responsible for more than one generatedObservation.\r \r The OM_Process shall be suitable for the observed property. As a corollary, details of the observed property are constrained by the procedure used.\r \r EXAMPLE Observed radiance wavelength is determined by the response characteristics of the sensor.\r \r A description of the observation procedure provides or implies an indication of the reliability or quality of the observation result.""" ; rdfs:range . a rdf:Property ; rdfs:label "result time"@en ; rdfs:comment """The attribute resultTime:TM_Instant shall describe the time when the result became available, typically when the procedure (7.2.2.10) associated with the observation was completed. For some observations, this is identical to the phenomenonTime. However, there are important cases where they differ.\r \r EXAMPLE 1 Where a measurement is made on a specimen in a laboratory, the phenomenonTime is the time the specimen was retrieved from its host, while the resultTime is the time the laboratory procedure was applied.\r \r EXAMPLE 2 The resultTime also supports disambiguation of repeat measurements made of the same property of a feature using the same procedure.\r \r EXAMPLE 3 Where sensor observation results are post-processed, the resultTime is the post-processing time, while the phenomenonTime is the time of initial interaction with the world.\r \r EXAMPLE 4 Simulations can estimate the values for phenomena in the future or past. The phenomenonTime is the time that the result applies to, while the resultTime is the time that the simulation was executed.""" ; rdfs:range xsd:dateTime . a rdf:Property ; rdfs:label "is member of" ; rdfs:range . a rdf:Property ; rdfs:label "feature of interest"@en ; rdfs:comment "Links the Observation to the Feature that is the ultimate subject of the observation and carries the observed property. This feature is the real-world object whose properties are under observation. An observation instance serves as a propertyValueProvider for its feature-of-interest." ; rdfs:range . a rdf:Property ; rdfs:label "sampling strategy"@en ; rdfs:comment "Links to a feature intended to sample the real-world object, as described in Clause 9 of ISO 19156:2011. " ; rdfs:range . a rdf:Property ; rdfs:label "observation context"@en ; rdfs:comment """link to related observation\r \r The first half of the property named 'relatedObservation' in the UML model. (The rule for implementing association classes needs clarification.)""" ; rdfs:range . a rdf:Property ; rdfs:label "observation result"@en ; rdfs:comment """The association Range shall link the OM_Observation to the value generated by the procedure. The value has the role result with respect to the observation. The type of the result is shown as “Any”, since it may represent the value of any feature property.\r \r NOTE 1 OGC SWE Common [20] provides a model suitable for describing many kinds of observation results.\r \r The type of the observation result shall be consistent with the observed property, and the scale or scope for the value shall be consistent with the quantity or category type. If the observed property (7.2.2.8) is a spatial operation or function, the type of the result may be a coverage.\r \r NOTE 2 In some contexts, particularly in earth and environmental sciences, the term “observation” is used to refer to the result itself.""" ; rdfs:domain ; rdfs:range , , , , , . a rdfs:Class ; rdfs:label "Observation context"@en ; rdfs:comment """Some observations depend on other observations to provide context which is important, sometimes essential, in understanding the result. These dependencies are stronger than mere spatio-temporal coincidences, requiring explicit representation. If present, the association class class ObservationContext (Figure 2) shall link a OM_Observation to another OM_Observation, with the role name relatedObservation for the target. It shall support one attribute.\r \r EXAMPLES\tSome examples include the conditions associated with experimental replicates (e.g., experimental plots and treatments used), biotic factors (e.g., ecological community), interactions among features (e.g., predator-prey), or other temporary relationships occurring at the time of observation that are are not inherent to the observed features themselves (i.e., they change over time), or the related observation may provide input to a process that generates a new result.\r This association complements the Intention association which describes relationships between a sampling feature and domain features.""" . a rdf:Property ; rdfs:label "role"@en ; rdfs:comment "role of related observation with respect to the observation of interest" ; rdfs:domain ; rdfs:range . a rdf:Property ; rdfs:label "related observation"@en ; rdfs:range . a rdfs:Class ; rdfs:label "Truth Observation"@en ; rdfs:comment "Observation whose result is either true or false" ; rdfs:subClassOf . a rdfs:Class ; rdfs:label "Observation"@en ; rdfs:comment """An observation is an act associated with a discrete time instant or period through which a number, term or other symbol is assigned to a phenomenon [2]. It involves application of a specified procedure, such as a sensor, instrument, algorithm or process chain. The procedure may be applied in-situ, remotely, or ex-situ with respect to the sampling location. The result of an observation is an estimate of the value of a property of some feature. Use of a common model allows observation data using different procedures to be combined unambiguously.\r \r The observation itself is also a feature, since it has properties and identity.\r \r Observation details are important for data discovery and for data quality estimation.\r \r The observation could be considered to carry metadata about an instance of a property (of the feature of interest). This property-value metadata complements the dataset and feature metadata that have been conventionally considered (e.g. ISO 19115).\r \r The values for the properties 'procedure', 'featureOfInterest', 'observedProperty', 'phenomenonTime', 'resultTime' may be inherited from a container resource.""" . a rdfs:Class ; rdfs:label "Geometry Observation"@en ; rdfs:comment "Observation whose result is a geometry object, such as a point, curve, surface or solid" ; rdfs:subClassOf . a rdfs:Class ; rdfs:label "Temporal object" ; rdfs:comment """Temporal geometry or topology, collection or complex. \r \r Temporal object has properties relating to time only.""" . a rdfs:Class ; rdfs:label "Truth object" ; rdfs:comment "Object to wrap a truth value" . a rdf:Property ; rdfs:label "Truth value" ; rdfs:range xsd:boolean . a rdfs:Class ; rdfs:label "Observation agent"@en ; rdfs:comment "Agent, device, sensor, software, protocol, computational method, algorithm or plan responsible for generating an observation result. Input may be a sensor stimulus, or the output from a previous process." . a rdfs:Class ; rdfs:label "Measurement"@en , "Mesure"@fr ; rdfs:comment "Observation whose result is a scaled number" ; rdfs:subClassOf . a rdfs:Class ; rdfs:label "Collection of observations"@en ; rdfs:comment """A collection of observations. \r \r The collection may be homogeneous in one or more of the feature-of-interest, observed-property, procedures, phenomenon-time or result-time. If only one value for any of these properties is provided on the collection, then it may be inferred to be a common (default) value for all the member observations, unless locally overridden.""" . a rdf:Property ; rdfs:label "has member" ; rdfs:domain ; rdfs:range xsd:string . a rdfs:Class ; rdfs:label "Observation process"@en ; rdfs:comment "Agent, device, sensor, software, protocol, computational method, algorithm or plan responsible for generating an observation result. Input may be a sensor stimulus, or the output from a previous process." . a rdfs:Class ; rdfs:comment "An unconstrained type or object" . a rdfs:Class ; rdfs:label "Geometry object" ; rdfs:comment "This stub is included in the om: ontology to support references to geometry as the result of a GeometryObservation. An existing OWL class that represents the notion of a geometry may be asserted to be a sub-class of this stub, without requiring use of a specific representation of Geometry in the context of observations instance." . a rdfs:Class ; rdfs:label "Count object" ; rdfs:comment "Object to wrap a count value" . a rdf:Property ; rdfs:label "Count value" ; rdfs:range xsd:integer . a rdfs:Class ; rdfs:label "Count Observation"@en ; rdfs:comment "Observation whose result is an integer" ; rdfs:subClassOf .