SANY D2.3.4 Specification of the Sensor Service Architecture V3 Doc.V3.1
Copyright © 2007-2009 SANY Consortium Page 167 of 233
reasons, extensions to existing OGC SWE services shall be specified according to the OGC Web Services Platform.
9.2.1 Specification of the SensorSA W3C Web Services Platform
The SensorSA W3C Web Services Platform is an instance of the W3C Web Services Architecture W3C, 2004. It comprises of a well-defined selection of standards and
specifications related to and defined by the W3C Web Services Architecture. It allows the specification of W3C Web Services in relation to the requirements of the SensorSA.
W3C Web Services offer the following options regarding the transport protocol, the request and response schema and the protocol bindings:
Topic Options
Transport HTTP
Request XML SOAP Message
Response XML SOAP Message
Protocol binding SOAP HTTP POST
Table 9-2: Options for the SensorSA W3C Web Service Platform
Since the KVP encoding used by OGC Web Services and also to a certain extent by RESTful Web Services may be encoded in XML and wrapped by a SOAP message, the
SensorSA W3C Web Services Platform is the premier choice for the obligatory core platform. The SensorSA W3C Web Services Platform is characterized by the following SOA-RM
properties:
-
Platform Name The name of the platform is
“SensorSA W3C Web Services Platform” following the Web Service infrastructure as defined by the W3C specifications W3C, 2004.
-
Reference Model The SensorSA W3C Web Services Platform is based on the W3C Web Services
Architecture W3C, 2004.
-
Interface Language The formal language that is used to define the SOA-RM Service Interfaces is the Web
Service Description Language WSDL, Version 1.1 W3C, 2001. Note: If required and supported by the tools used, WSDL 2.0 W3C, 2007 may also be
used.
-
Execution Context The execution context of the SensorSA W3C Web Services Platform is defined by the
SANY D2.3.4 Specification of the Sensor Service Architecture V3 Doc.V3.1
Copyright © 2007-2009 SANY Consortium Page 168 of 233
following properties: Transport Protocol and Message Format:
SOAP 1.2 HTTP binding as defined in SOAP Part 1: Message Framework, Version 1.2
W3C, 2003 and Hypertext Transfer Protocol HTTP, Version 1.1 W3C, 2006. The message style that shall be used is documentliteral non-
wrapped since it is the most widely accepted and interoperable message style. Security
The common security aspects of the different SensorSA Service Platforms are discussed in section 9.3.1. The following aspects, however, are specific to the
SensorSA W3C Web Services Platform: Session Information: The transport of session information may be accomplished
by using platform specific mechanisms, such as the inclusion of a session key in the SOAP header.
Encryption: Optional encryption of SOAP messages shall be accomplished by Web Services Security: 4 SOAP Message Security 1.1 OASIS, 2006.
-
Schema Language The general schema language used to define the SOA-RM Information Models is the
eXtensible Markup Language XML 1.0 XML, 2006. Section 9.3.2 will list further XML-based schema and modelling languages.
-
Information Model Constraints There are currently no immediate constraints on information models themselves.
9.2.2 Specification of the SensorSA OGC Web Services Platform
