86
Copyright © 2013 Open Geospatial Consortium. SWIM-SC-0020
SWIM services SHALL provide an interface that supports one or more of
the following message format, message protocol, and transport
protocol combinations:
G-over-HTTPHTTPS G -over-HTTPHTTPS, inclusive of
the Representative State Transfer REST interface pattern
G-over-JMS G -over-JMS
OGC Standards Perspective - Fully Compliant
XML-over-HTTP is the most commonly supported
formatprotocoltransport combination. Exchanging web service messages via
JMS should also be possible using the W3C SOAP JMS binding.
Product Implementation Perspective – Fully Compliant Each of the providers
supports at least one of the combinations and could support more if required.
SWIM-SC-0021 SWIM services MAY use HTTPS or
TLS as the transport protocol in place of HTTP or TCP for service interface
interactions. OGC Standards Perspective - Fully
Compliant OGC services are usual web services and
thus all components should be able at least with minor modifications to support
HTTPSTLS. Product Implementation Perspective -
Fully Compliant Security is generally implemented by OGC
services at the HTTPS, SOAP, REST layers as a common practice.
4.2.3 SOAP Message Processing
SWIM-SC-0030 SOAP Messages in the SWIM
environment SHALL be processed using the FUSE Service Framework
library. OGC Standards Perspective - Fully
Compliant Product Implementation Perspective -
Provisionally Compliant We have results from previous studies
see OWS-7 Engineering Report that tested the deployment of OGC compliant
web services in a FUSE environment with the service deployed as a web application.
Revamping the implementation of the service itself should be possible if the
product was really required to use the FUSE libraries.
4.2.4 SOAP Messaging WS-I Compliance
SWIM-SC-0040 SWIM Service endpoints
SHALL meet the messaging compliance
requirements of the SWIM Interoperability Basic Profile a SWIM-
annotated version of the Web Services Interoperability Basic Profile,
Section 3.
OGC Standards Perspective - Fully Compliant
OGC web service standards appear to be compatible with the WS-I Basic Profile and
also the SWIM-annotated WS-I Basic Profile.
Product Implementation Perspective - Provisionally Compliant
If required for the implementation, this requirement can be satisfied within the
OGC standards set.
Copyright © 2013 Open Geospatial Consortium.
87
4.2.5 Binary Attachments in SOAP Messages
SWIM-SC-0045 Any binary attachment that is sent
with a SOAP message SHALL be attached and processed using the
Message Transmission Optimization Mechanism MTOM, in accordance
with the SWIM Governance Plan. OGC Standards Perspective - Fully
Compliant This requirement does not appear to
conflict with OGC standards and practices. The OGC OWS 5 SOAPWSDL Common
Engineering Report Public Engineering Report recommends the use of MTOM in a
SOAP binding to transfer large binary data.
Product Implementation Perspective - Provisionally Compliant
MTOM is not being used for any of the OWS-9 components but could be used as
an implementation choice if required.
4.2.6 Data Retrieval Protocol
SWIM-SC-0048 Service providers MAY use transport
protocols and message formats other than those defined in SWIM-SC-0020
for binary and large file data delivery and retrieval. For example: FTP,
SMTP, or SCP may be applied to delivery large binary files. The
alternate protocol SHALL NOT be used for service requests or
notifications, but MAY be used for content delivery.
OGC Standards Perspective - Fully Compliant
Product Implementation Perspective - Provisionally Compliant
The WPS Schema supports this requirement by pointing to the binary file
image location. If required for the implementation, this requirement can be
satisfied within the OGC standards set.
4.2.7 JMS Provider Standardization
