Specification identifier Conformance Classes

Copyright © 2011 Open Geospatial Consortium 3 Table 1 — SPS Conformance Classes Conformance class name Conformance class identifier Operation andor behavior Core http:www.opengis.netsp ecSPS2.0confCore The server implements the GetCapabilities, DescribeTasking, Submit, GetStatus, GetTask and DescribeResultAccess operations as defined by this standard as well as the conformance classes that this conformance class depends upon see Figure 1. State Logger http:www.opengis.netsp ecSPS2.0confStateLo gger The server implements state logger functionality as defined by this standard as well as the conformance classes that this conformance class depends upon see Figure 1. Feasibility Controller http:www.opengis.netsp ecSPS2.0confFeasibil ityController The server implements the GetFeasibility operation as well as the conformance classes that this conformance class depends upon see Figure 1. Reservation Manager http:www.opengis.netsp ecSPS2.0confReserva tionManager The server implements the Reserve and Confirm operations as well as the conformance classes that this conformance class depends upon see Figure 1. Task Updater http:www.opengis.netsp ecSPS2.0confTaskUp dater The server implements the Update operation as well as the conformance classes that this conformance class depends upon see Figure 1. Task Canceller http:www.opengis.netsp ecSPS2.0confTaskCa nceller The server implements the Cancel operation as well as the conformance classes that this conformance class depends upon see Figure 1. Basic PubSub http:www.opengis.netsp ecSPS2.0confBasicPu bSub The server implements publishsubscribe functionality and publish SPS events as defined in this standard as well as the conformance classes that this conformance class depends upon see Figure 1. ChannelBased PubSub http:www.opengis.netsp ecSPS2.0confChannel BasedPubSub The server implements publishsubscribe functionality and publish SPS events on the SPS channelstopics as defined by this standard as well as the conformance classes that this conformance class depends upon see Figure 1. XML Encoding http:www.opengis.netsp ecSPS2.0confXMLEn coding The server encodes the data types from the conceptual model in XML as defined by this standard as well as the conformance classes that this conformance class depends upon see Figure 1. SOAP http:www.opengis.netsp ecSPS2.0confSOAP The server implements the SOAP binding as defined in this standard as well as the conformance classes that this conformance class depends upon see Figure 1. 4 Co Figure 1 - SPS Conformance Classes and their dependencies 3 Normative references The following normative documents contain provisions that, through reference in this text, constitute provisions of this document. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. For undated references, the latest edition of the normative document referred to applies. ISO 19105:2000, Geographic information — Conformance and Testing ISO 19108:2002, Geographic information — Temporal schema ISO 19136:2007, Geographic information -- Geography Markup Language GML see also: OpenGIS® Encoding Standard Geography Markup Language, OGC document 07-036 ISO DIS 19156:2010, Geographic information — Observations and Measurements OGC 06-121r3, OpenGIS ® Web Services Common Specification NOTE This OWS Common Specification contains a list of normative references that are also applicable to this Implementation Standard. pyright © 2011 Open Geospatial Consortium Copyright © 2011 Open Geospatial Consortium 5 OpenGIS ® Encoding Standard, SWE Common Data Model, OGC document number 08- 094 OpenGIS ® Implementation Standard, SWE Service Model, OGC document number 09- 001 NOTE This SWE Service Model standard contains a list of normative references that are also applicable to this Implementation Standard. In addition to this document, this standard includes several normative XML Schema Document files as specified in Annex B. 6 Copyright © 2011 Open Geospatial Consortium 4 Terms and definitions For the purposes of this standard, the terms and definitions specified in clause 4 of [OGC 06-121r3] shall apply, as well as the terms and definitions specified in clause 4 of [09- 001]. In addition, the following terms and definitions apply. 4.1 Asset synonyms: sensor, simulation an available means of collecting information 4.2 Asset Management System synonyms: acquisition system, asset support system system for controlling the effective utilization of an asset 4.3 Collection act of gathering information NOTE In the context of SPS, the term is usually perceived having the process of gathering information in mind. Another interpretation is the aggregation of the results of one or more collection processes. 4.4 Requirement something that is necessary in advance 4.5 Simulation use of models to investigate time dependent processes 4.6 Task conceptual resource that represents a SPS assignment. It includes the possibly empty set of tasking parameters. 4.7 Tasking parameterizing an asset; can be done by sending one or more tasking requests 4.8 Tasking request request with certain tasking semantics that contains tasking parameters NOTE In the context of SPS, the GetFeasibility, Reserve, Submit and Update requests are tasking requests. 4.9 Tasking Parameter parameter that has an influence on the parameterization of an asset Copyright © 2011 Open Geospatial Consortium 7 5 Conventions

5.1 Abbreviated terms

Most of the abbreviated terms listed in Subclause 5.1 of the OWS Common Implementation Specification [OGC 06-121r3] apply to this document, plus the following abbreviated terms. AOI Area Of Interest FES Filter Encoding Specification AM Asset Management OM Observation and Measurement SensorML Sensor Model Language SOS Sensor Observation Service SPS Sensor Planning Service SWE Sensor Web Enablement SWE Common SWE Common Data Model SWES SWE Service Model WCS Web Coverage Service WMS Web Map Service WNS Web Notification Service 8 Copyright © 2011 Open Geospatial Consortium

5.2 UML notation

Diagrams that appear in this standard are presented using the Unified Modeling Language UML static structure diagram, as described in Subclause 5.2 of [OGC 06-121r3]. NOTE Packages and data types from foreign namespaces or data types from packages other than the one under consideration are shown with grey background unless they are given only as types of attributes from classes in the model defined in this specification. Interfaces are shown with light turquoise background.

5.3 Platform-neutral and platform-specific standards

For compliance with Clause 10 of OGC Topic 12 and ISO 19119, this standard follows the pattern defined in subclause 5.4 of [OGC 06-121r3]. That is, model elements are specified in platform-neutral fashion first, using tables that serve as data dictionaries for the UML model see clause 5.4 of this document. Platform-specific encodings of these model elements are provided in separate clauses or documents. The XML Schema encoding has automatically been generated using the rules defined in clause 24 of [OGC 09-001]. This document specifies platform-specific encodings appropriate for a SOAPWSDL operation binding. However, the model as well as its XML Schema encoding and other data can be used by other bindings as well, like RESTful or POX Plain Old XML over HTTP using XML or KVP encoding.

5.4 Data dictionary tables

The UML model data dictionary is specified herein in a series of tables. The contents of the columns in these tables are described in table 1 of [OGC 06-121r3]. The contents of these data dictionary tables are normative, including any table footnotes.

5.5 Classes imported from other specifications with predefined XML encoding

This specification uses an automatic mapping approach from the UML model to the XML Schema encoding. The approach is described in chapter 24 of [OGC 09-001]. As shown in Figure 13, this standard uses types defined by other standards. For the mapping to XML Schema, the implementation instructions listed in table D.2 of [OGC 07-036] are used together with the instructions listed in Table 2, Table 3 and Table 4 in this standard and Table 4 from [OGC 09-001]. For an explanation of the table columns, see clause D.2.1 in OGC 07-036.