Default parameter values SWE Common encoding

OGC 10-135 EO Satellite Tasking Extension for SPS swe:field name = FusionAccepted swe:Boolean definition = http:www.opengis.netdefpropertyOGC-EO0FusionAccepted optional = true swe:value true swe:value swe:Boolean swe:field In the example above, the default value for the FusionAccepted parameter is true. It means that if the client does not specify a value, the server will automatically apply the value true for this parameter.

7.1.2.1.2 Values of parameters embedded in tasking requests

Values of tasking parameters are encoded with any of the encoding defined in the SWE Common standard when embedded within a tasking request i.e. Submit, Update, GetFeasibility, Reserve, etc.. A compliant EO SPS service implementation shall support at least the XML encoding method identified by the corresponding URI defined in the SPS 2.0 standard. Requirement http:www.opengis.netspecEOSPS2.0reqcoretasking-params-xml-encoding Req 4. An EO SPS implementation shall support the XMLEncoding defined in clause 8.5 of [OGC 08‐094] “SWE Common Data Model 2.0 Encoding Standard” and pass the corresponding conformance tests. Please refer to [OGC 08-094] for details of the XML encoding rules. Annex C contains examples of tasking requests with the matching tasking parameters description. As required by the SPS interface standard [OGC 09-000], any invalid value for a tasking parameter i.e. not matching the parameter definitions provided in DescribeTaskingResponse shall result in an InvalidParameterException being sent back to the client.

7.1.2.2 ProgrammingRequest Class

7.1.2.2.1 Description

The ProgrammingRequest class is the root of the list of tasking parameters. It is abstract and cannot be instantiated. Instead, the CoverageProgrammingRequest class cf. §7.1.2.4 or the SwathProgrammingRequest class cf. §7.1.2.5 are used. Requirement http:www.opengis.netspecEOSPS2.0reqcoretasking-params-root Req 5. The root of the list of tasking parameters in DescribeTaskingResponse shall be a concrete instance of the ProgrammingRequest class. 22 Copyright © 2011 Open Geospatial Consortium EO Satellite Tasking Extension for SPS OGC 10-135

7.1.2.2.2 Data model

This abstract class contains two common parameter groups that are inherited by its descendants. These groups are represented by the QualityOfService and ValidationParameters classes, as shown in the UML diagram below: «DataType» ProgrammingRequest «DataType» QualityOfServ ice «DataType» Cov erageProgrammingRequest «DataType» ValidationParameters «DataType» Sw athProgrammingRequest +QualityOfService 0..1 +ValidationParameters 1.. Figure 1 – UML diagram of the ProgrammingRequest class Classes represented in this diagram are fully described in later sections: The class QualityOfService is specified in clause §7.1.2.3. The class CoverageProgrammingRequest is specified in clause §7.1.2.4. The class SwathProgrammingRequest is specified in clause §7.1.2.5. The class ValidationParameters is specified in clause §7.1.2.16.

7.1.2.3 QualityOfService Class

7.1.2.3.1 Description

This parameter group is used to specify the level of priority of the programming request. In general, the user should expect more reactivity from a ‘HIGH’ priority request than for a ‘STANDARD’ priority request. However, he will usually be charged more in order to obtain this high priority service. The exact meaning of the priority levels have to be agreed upon with the provider and are usually defined verbally in its terms of service. If the EO-SPS instance implements an authentication method, the internal priority level can be defined on a per user basis by associating it to the user account. Copyright © 2011 Open Geospatial Consortium 23