11 Shared aspects
11.1 Introduction
This clause specifies aspects of the SPS Service behavior that are shared by several operations.
11.2 Shared operation parameters
This clause specifies some of the parameters used by multiple operations specified in the following clauses. The parameter names, meanings, data types, and multiplicity shall be
as specified in Table 1.
Table 1 — Definitions of some operation request and response parameters
Name Definition
Data type and value Multiplicity and use
InputDescriptor Defines the input
required to task a sensor complex type
- notificationTarget
Defines the WNS that has to be used to notify
the client about the request results
complex type -
11.2.1 InputDescriptor
The InputDescriptor defines the input a client has to provide to task an asset. The following UML model and the following figure provide an overview of the
InputDescriptor.
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
39
Figure 9: InputDescriptor in UML notation
InputDescriptor: Attributes An InputDescriptor contains the mandatory attributes “parameterID” which will be used
to reference a specific parameter in other requests, e.g. Submit. The “use” attribute defines if the parameter must or shall be provided by the client. It enumerates the strings
“optional” and “required”. If required, a Submit, Update or GetFeasibility request will not be validated as true if this parameter is missing. The third attribute “updateable” is
optional and defines if a parameter can be updated by subsequent UpdateRequest requests.
InputDescriptor: Elements The InputDescriptor defines four elements: Three optional elements and one mandatory.
The three optional elements can be used to provide further description about this InputDescriptor gml:description, allow the presetting of possible values restriction
e.g. “yes, no” or “day, night” or “1, 2, 3”, and define the cardinality of possible input
40
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
elements cardinality. Cardinality is restricted to positive integers excluding zero and the string value “unbounded”.
The data structure of the input elements that shall be provided by the client is defined in the mandatory “definition” element. This element serves as an entry point to parsers to
find the data block definition that has to be matched by the input data. It is followed by either a swe:DataDefinition element see SWECommon for further information, a
“taskMessageDefinition” element which is a link to an external definition of the data block or a GeometryDefinition or TemporalDefinition. The latter two are of type QName
and are restricted to the GML elements gml:Point, gml:Line, gml:Polygon or gml:TimeInstant and gml:TimePeriod respectively. It is assumed that clients “know” how
to encode those basic elements.
Figure 10: InputDescriptor Element in XMLSpy notation
11.2.2 InputParameter
Kategori