Advertising Support for Status Logging
7.3.2.4.4 Advertising Supported Operation Encodings
Requirement http:www.opengis.netspecSPS2.0reqGetCapabilitiesResponsesupportedEncodings REQ 42. SPS servers shall specify the supported encodings for HTTP POST based transfer of operation requests. Specifically, an ows:Constraint element shall be included with PostEncoding as the value of the name attribute supporting a the value “SOAP” to indicate that SOAP encoding is allowed, as specified in clause 8. b the value “XML” to indicate that XML encoding is allowed without SOAP message encapsulation.7.3.2.4.5 Advertising Other Operation Metadata
In addition to the optional values listed in Table 23, there are many optional values of the name attributes and value elements in the OperationsMetadata section. Most of these attributes and elements are for recording the domains of various parameters and quantities. EXAMPLE 1 The domain of the exceptionCode parameter can record all the codes implemented for each operation by that specific server. Similarly, each of the GetCapabilities operation optional request parameters can have its domain recorded. EXAMPLE 2 The domain of the Sections parameter in the GetCapabilities operation request can record all the sections implemented by that specific server. Copyright © 2011 Open Geospatial Consortium 597.3.2.4.6 Advertising Supported Conformance Classes
Requirement http:www.opengis.netspecSPS2.0reqGetCapabilitiesResponseconformanceClass REQ 43. Any SPS service shall document in its capabilities document the supported conformance classes. The identifier a URI of each supported conformance class shall be listed as a value of the profile property of the ServiceIdentification section.7.3.2.5 Exceptions
Requirement http:www.opengis.netspecSPS2.0reqGetCapabilitiesResponseexception REQ 44. When an SPS server encounters an error while performing a GetCapabilities operation, it shall return an exception message as specified in clause 7.2. If the GetCapabilities request contained the Sections parameter with value notifications but that value is not listed by the service for the Sections parameter because the service does not implement publishsubscribe functionality then an InvalidParameterValue exception with locator Sections or sections is returned.7.3.2.6 Examples
Clause 9.6 provides example XML instances for the GetCapabilities operation request and response.7.3.3 Contents Package
7.3.3.1 Introduction
This package contains the data types used to provide metadata about the sensors provided by an SPS and the supported data encodings. In order to reduce the size of the Capabilities document by reducing the amount of redundant information in the contents section, the property inheritance mechanism defined in clause 22 of [OGC 09-001] is used.7.3.3.2 Data Types
The conceptual model of the Contents package is shown in the following UML diagram.Parts
» OGC® Sensor Planning Service Implementation Standard
» Abstract Submitting organizations OGC® Sensor Planning Service Implementation Standard
» Specification identifier Conformance Classes
» Abbreviated terms OGC® Sensor Planning Service Implementation Standard
» Data dictionary tables Classes imported from other specifications with predefined XML encoding
» Namespace Conventions OGC® Sensor Planning Service Implementation Standard
» Introduction OGC® Sensor Planning Service Implementation Standard
» Client Server Interaction OGC® Sensor Planning Service Implementation Standard
» Introduction Task – Concept and Handling
» Tasking Parameters Tasking requests
» Reserving a Task State Handling
» Status Reporting OGC® Sensor Planning Service Implementation Standard
» Levels of Abstraction – SPS Chains
» Asynchronous Communication Information Access
» Interface Overview OGC® Sensor Planning Service Implementation Standard
» SPS Exceptions OGC® Sensor Planning Service Implementation Standard
» Introduction Data Types GetCapabilities Operation
» Operation Request – GetCapabilities GetCapabilities Operation
» OperationsMetadata section standard contents Advertising Implemented Operations
» Advertising Support for Status Logging
» Introduction Data Types Contents Package
» SPSContents SensorOffering Contents Package
» Data Types Operation Request - DescribeTasking
» Introduction Data Types Submit Operation
» Operation Request - Submit Operation Response - SubmitResponse
» Data Types GetStatus Operation
» Operation Request - GetStatus
» Operation Response - GetStatusResponse
» Data Types Operation Request – GetTask
» Operation Response – GetTaskResponse GetTask Operation
» Reference group usage Introduction
» Operation Response - DescribeResultAccessResponse AvailableOrNot
» DataAvailable DataNotAvailable UnavailableCode DescribeResultAccess Operation
» Introduction Data Types Reserve Operation
» Operation Request - Reserve Operation Response - ReservationReport
» Introduction Data Types Confirm Operation
» Operation Response - ConfirmResponse
» Introduction Data Types GetFeasibility Operation
» Operation Request - GetFeasibility
» Operation Response - GetFeasibilityResponse
» Data Types Operation Request - Update
» Operation Response - UpdateResponse
» Introduction Data Types Cancel Operation
» Operation Response - CancelResponse Exceptions
» Optional Parameters SPS tasking parameters representation
» SPS Events OGC® Sensor Planning Service Implementation Standard
» Channel based filteringSPS notification topics
» Introduction Action URIs OGC® Sensor Planning Service Implementation Standard
» actio OGC® Sensor Planning Service Implementation Standard
» Realization of PublishSubscribe OGC® Sensor Planning Service Implementation Standard
» Realization of Asynchronous RequestResponse
» Retrieving the Capabilities Document
» Getting Result Access Information for a Procedure
» Getting the Tasking Parameter Description
» Determining the Feasibility of a Tasking Request
» Task Submission Scheduling a Task Submit Reserve
» Reserving a Task Scheduling a Task Submit Reserve
» Automatic Reservation Expiration Scheduling a Task Submit Reserve
» Task Failure Scheduling a Task Submit Reserve
» Final Response Not Provided Before Latest Response Time
» Final Response is Provided Before Latest Response Time
» Task Completion Scheduling a Task Submit Reserve
» Getting Result Access Information for a Task
» Service Exceptions SPS Examples Scenario
» Notifications SPS Examples Scenario
» Using WS-Addressing SPS Examples Scenario
» Scheduled State InExecution State
» Reserved State Tasking Request Choice
» Diagrams Tasking Request State Machine
» Accepted State ChoiceA ChoiceB
» Invalid version number Common Request Response Handling
» Exception Appropriateness Exception Model Compliancy
» GetCapabilities operation facet validity Indicate support of SWE Common Encodings
» Mandatory Operations Service Metadata
» DescribeTasking operation facet validity
» Provide name for tasking parameter component
» Tasking Parameter Description Model Validity
» Tasking Parameter Usage Tasking request expiration
» GetStatus operation facet validity
» GetTask operation facet validity
» Handling requests for already deleted status information
» State handling State information storage
» Successful task submission Submit
» Identifiers for references and reference groups
» Referencing task data Result Handling
» Capability Test Conformance Class – State Logger
» GetStatus with since parameter Status history provisioning
» Capability Test Conformance Class – Reservation Manager
» Operations listed in Capabilities
» Cancel operation facet validity
» Capability Test Conformance Class – Task Updater
» Handling of updatable DataArray Handling of updatable DataRecord DataChoice
» Handling update not supported for a given procedure New identifier assignment
» State transition resulting of task update
» Operation listed in Capabilities
» SPS event encoding SPS event publication
» Capability Test Conformance Class – Channel Based PubSub
» Support of Topic Dialect Topic Set Contents
» XML Encoding Validity XML Validation Exception Reporting
Show more