xii
Copyright © 2011 Open Geospatial Consortium.
v. Submitting organizations
The following organizations submitted this document to the Open Geospatial Consortium Inc.
a International Geospatial Services Institute GmbH iGSI b Spot Image, S.A.
c University of Muenster
vi. Document contributor contact points
All questions regarding this document should be directed to the editor or the contributors:
CONTACT COMPANY EMAIL
Johannes Echterhoff editor iGSI
johannes.echterhoffigsi.eu Ingo Simonis
iGSI ingo.simonisigsi.eu
Alexandre Robin Spot Image, S.A.
alexandre.robinspotimage.fr Arne Bröring
52°North broering52north.org
Christoph Stasch University of Muenster
staschcuni-muenster.de
Issues with standard Any issues in this standard are captured in the following format:
Issue Name : [Issue Name goes here.] Your Initials, Date
Issue Description: [Issue Description.]
Resolution: [Insert Resolution Details and History.] Your Initials, Date]
Copyright © 2011 Open Geospatial Consortium.
xiii
vii. Changes to the OGC Abstract Specification
The OpenGIS
®
Abstract Specification does not require changes to accommodate the technical contents of this document.
xiv
Copyright © 2011 Open Geospatial Consortium.
viii. Future work
This document is intended to provide data types and define mechanisms that can be reused by other OGC Sensor Web Enablement SWE implementation standards. Once
data types and mechanisms defined in this standard become usable in other OGC Web Services OWS in addition to the SWE standards, these types should be added to the
OWS Common standard and – having been added there – be removed in a future version of this standard. The notifications package see clause 8 is one possible candidate for
such a change.
In addition, further data types currently not contained in this specification that have been identified as being useful across SWE services and that are neither contained in this
specification nor of use for all OWS shall be added to future versions of this specification.
If new requirements arise that cause a modification of the functionality defined in this standard, either through extensions or profiles, then required conformance classes shall
also be defined. This could for example be a conformance class to augment the existing Sensor History Provider conformance class with the requirement that sensor descriptions
can only be retrieved for a specific point in time.
During the development of this specification, the OGC has changed its specification template and development policies. This specification reflects those changes as much as
possible, but full compliancy to the new OGC specification model needs to be achieved in future releases.
Copyright © 2011 Open Geospatial Consortium.
xv
Foreword
This is the first version of the standard defining data types that are common across SWE services. It does not replace any existing OGC standard in whole or in parts.
This standard uses data types defined by the W3C WS-Addressing and OASIS WS- Notification set of standards.
This document includes six annexes; Annexes A-D are normative, and Annexes E and F are informative.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium Inc. shall not be held
responsible for identifying any or all such patent rights.
Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be
aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.
xvi
Copyright © 2011 Open Geospatial Consortium.
Introduction
During the preparation of the second major version of the Sensor Planning Service SPS and Sensor Observation Service SOS, the OGC Members recognized that certain
interfaces and data types are common across SWE services. The DescribeSensor operation is the most prominent example for such an interface and according data types.
Common sense was that these types should be specified in a separate document that could then be referenced by all standards that reuse the defined types. While preparing both
SPS 2.0 and SOS 2.0, other data types with common use were identified, leading to the set of data type and interface definitions contained in this document.
This standard does not replace the OWS Common standard. This standard serves as the home for all data type and interface definitions that are common only to SWE services.
OpenGIS
®
Implementation Standard OGC 09-001
Copyright © 2011 Open Geospatial Consortium.
1
OpenGIS
®
SWE Service Model
1 Scope
This OGC
®
document specifies data types and interfaces common to Sensor Web services. It therefore serves as a baseline for the development of such services.
Specifically this standard: • Is applicable to all services that provide information from or about sensors;
• Is applicable for uses cases in which sensors need to be managed through service interfaces.
• Specifies how sensor descriptions can be accessed and managed; • Specifies how historical sensor descriptions can be accessed and managed;
• Establishes the means for inserting and deleting sensors through a common service interface.
• Specifies publishsubscribe functionality for Sensor Web services – through definition of recognizable event types, their encodings and association to
notification topics. • Gives guidelines for use of identifiers;
• Provides guidelines on creating an automatic mapping of the data types relevant in a service model from their UML representation to their XML Schema
encoding; • Defines the information required in a SOAP binding to realize the specified
service functionality. The SOAP binding specifies WS-Notification to realize PublishSubscribe service functionality
2
Copyright © 2011 Open Geospatial Consortium.
2 Conformance
2.1 Overview