DescribeTasking request parameters DescribeTasking request KVP encoding DescribeTasking request XML encoding

13.2 DescribeTasking operation request

13.2.1 DescribeTasking request parameters

This table also specifies the UML model data type, source of values, and multiplicity of each listed parameter, plus the meaning to servers when each optional parameter is not included in the operation request. Table 8: Parameters in DescribeTasking operation request Name a Definition Data type and values Multiplicity and use service Service type identifier Character String type, not empty fixed: Value is OWS type abbreviation: SPS One mandatory request Operation name Character String type, not empty Value is operation name: DescribeTasking One mandatory version Specification version for operation Character String type, not empty Value is specified by each Implementation Specification and Schemas version One mandatory sensorID Defines sensor to be described xs:token type One to many mandatory a The name capitalization rules being used here are specified in Subclause 11.6.2 of [OGC 05-008]. NOTE 2 The data type of many parameters is specified as “Character String type, not empty”. In the XML Schema Documents specified herein, these parameters are encoded with the xsd:string type, which does NOT require that these strings not be empty. The “Multiplicity and use” columns in Table 7 through all tables specify the optionality of each listed parameter and data structure in the DescribeTasking operation request. Since all parameters and data structures are mandatory in the operation request, all parameters and data structures shall be implemented by all SPS clients, using a specified values. Similarly, all parameters and data structures shall be implemented by all SPS servers, checking that each request parameter is received with any specified values.

13.2.2 DescribeTasking request KVP encoding

KVP encoding not supported

13.2.3 DescribeTasking request XML encoding

All SPS servers shall implement HTTP POST transfer of the DescribeTasking operation request, using XML encoding only. The following figure and schema fragment specifies the contents and structure of a DescribeTasking operation request encoded in XML. Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved. 55 SPSOperation «Element» DescribeTasking + «Attribute» request: string + «Attribute» version: string + «Attribute» service: string = SPS + «Element» sensorID: token [1..] Figure 23: DescribeTasking in UML notation Figure 24: DescribeTakingRequest in XMLSpy notation EXAMPLE An example DescribeTasking operation request XML encoded for HTTP POST is: ?xml version=1.0 encoding=UTF-8? DescribeTasking xmlns = http:www.opengis.netsps service = SPS version = 1.0.0 sensorID urn:x-ogc:object:sensor:IFGI:AXISPTZ_C:1:ifgicam01 sensorI D DescribeTasking

13.3 DescribeTasking operation response