SensorML OGC 12-000
Copyright © 2014 Open Geospatial Consortium
103
swe:elementType swe:encoding
swe:TextEncoding blockSeparator
= 10;
tokenSeparator =
, swe:encoding
swe:values 10.0,73 17.5,89.5 20.0,94.0 30.,95.5 40.0,96.0 50.0,96.0 100.0,94.0
swe:values swe:DataArray
sml:parameter sml:ParameterList
sml:parameters
8.1.4.5.1 Data Component Union
The DataComponentOrObservable group provides three choices to serve as process inputs, outputs, and parameters. These include swe:AbstractDataComponent,
sml:ObservableProperty, and sml:DataInterface. These will each be discussed further in the following sections.
The XML snippet defining the DataComponentOrObservable group is given below:
group name
= DataComponentOrObservable
choice element
ref =
swe:AbstractDataComponent annotation
documentation A single digital number DN or aggregate of DNs that represent the value of some property.
Single data components can be of type Quantity, Count, Category, Boolean, Text, or Time; these can be aggregated in records, arrays, vector, and matrices.
documentation annotation
element element
ref =
sml:ObservableProperty annotation
documentation A physical property of the environment that can be observed by an appropriate detector e.g.
temperature, pressure, etc.; Typically,an ObservableProperty serves as the input of a detector and the output of an actuator.
documentation annotation
element element
ref =
sml:DataInterface annotation
documentation A data interface serves as an intermediary between the pure digital domain and the physical
domain where DN are encoded into a format and perhaps transmitted through physical connections using some well-defined protocol. The DataInterface element allows one to define
the components, semantics, encoding, connections, and protocol at an input, output, or parameter port.
documentation annotation
element choice
group complexType
name =
DataComponentOrObservablePropertyType sequence
minOccurs =
group ref
= sml:DataComponentOrObservable
sequence attributeGroup
ref =
swe:AssociationAttributeGroup complexType
Copyright © 2014 Open Geospatial Consortium
104
8.1.4.5.2 ObservableProperty
The ObservableProperty element is an XML encoding of the model defined in Clause 7.2.1 and discussed more in Clause 7.2.3.1. The ObservableProperty is used to represent
an observable property or state in the environment. It is often used as an input field e.g. stimulus for a detector or the output field e.g. action of an actuator.
The XML snippet defining ObservableProperty and its associated complex types is shown below:
element name
= ObservableProperty
type =
sml:ObservablePropertyType substitutionGroup
= swe:AbstractSWEIdentifiable
annotation documentation
A physical property that can be observed and possibly measured e.g. temperature, color, position. An ObservableProperty has unambiguous definition, but does not have units of measure.
documentation annotation
element complexType
name =
ObservablePropertyType complexContent
extension base
= swe:AbstractSWEIdentifiableType
attribute name
= definition
type =
anyURI use
= required
extension complexContent
complexType complexType
name =
ObservablePropertyPropertyType sequence
minOccurs =
element ref
= sml:ObservableProperty
sequence attributeGroup
ref =
swe:AssociationAttributeGroup complexType
The ObservableProperty element requires a URL as the value of its definition attribute, which should resolve to a definition for the observable within an online dictionary or
ontology.
Requirement
http:www.opengis.netspecsensorml2.0reqxmlcore-processobservable-definition
Req 58. The ObservableProperty element shall include the definition attribute that shall take as its value, a resolvable URL referencing the definition of the
observable within an online dictionary or ontology.
An minimal example of the use of ObservableProperty as a value for an input property is given below:
sml:input name
= temperature
sml:ObservableProperty definition
= http:sensorml.comontswepropertyAtmosphericTemperature
sml:input
SensorML OGC 12-000
Copyright © 2014 Open Geospatial Consortium
105
8.1.4.5.3 SWE Common Data