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
SWIM-SC-0050 SWIM JMS message producers
SHALL use FUSE Message Broker as the JMS Provider for JMS destinations
OGC Standards Perspective - Fully Compliant
Product Implementation Perspective - Provisionally Compliant
JMS hasnt been widely implemented by the OGC community or its products due an
emphasis on broad interoperability through use of common protocols and simple
message exchange patterns. As requirements for JMS messages appear,
OGC participants products will evolve as needed.
SWIM-SC-0051 SWIM JMS clients MAY institute a
JMS bridge between FUSE Message Broker and the service provider’s
message-oriented-middleware MoM. Not Applicable to OGC standards
This requirement addresses the establishment of a communications link
between services.
SWIM-SC-0052 SWIM JMS Message Brokers SHALL
be configured to support the OpenWire protocol over TCP or SSL.
Not Applicable to OGC standards This is a requirement against the JMS
Message Broker and does not apply to OGC service components.
SWIM-SC-0053 SWIM JMS Message Brokers MAY be
configured to support the Simple Text Object Messaging Protocol STOMP
protocol over HTTP or HTTPS Not Applicable to OGC standards
This is a requirement against the JMS Message Broker and does not apply to
OGC service components.
88
Copyright © 2013 Open Geospatial Consortium.
4.2.8 JMS Destination Names
SWIM-SC-0055 JMS destination names SHALL
include the FAA Business Context Identifier FBCI of a SWIM-registered
namespace as the first prefix for the destination name, as described by
[STD063]. For example, the namespace:
urn:us:gov:dot:faa:AviationSafety may correspond to the JMS destination
name: “AviationSafety.topic.IncidentReports”.
OGC Standards Perspective - Fully Compliant
Product Implementation Perspective - Provisionally Compliant
If required for the implementation, this requirement can be satisfied within the
OGC standards set.
4.2.9 JMS Message Type
SWIM-SC-0060 Messages sent using JMS SHALL use
-: 2;9--:0 A?141 SOAP message format.
OGC Standards Perspective - Fully Compliant
With the W3C standard SOAP over Java Message Service 1.0 OGC based
?1B51??4;A80.1-.81;1D4-:31 more specifically: SOAP messages via
JMS. Product Implementation Perspective -
Provisionally Compliant If required for the implementation, this
requirement can be satisfied within the OGC standards set.
SWIM-SC-0061 -:0 91??-31?4--1
sent over JMS SHALL use the JMS TextMessage type.
OGC Standards Perspective - Fully Compliant
The W3C SOAP over Java Message Service 1.0 standard requires that
TextMessage is supported. It also lists some concerns but in general it looks that
with the W3C standard OGC based services are able to exchange SOAP
messages via JMS using the JMS TextMessage type.
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.
89
4.3 Registry Repository 4.3.1 Interface Discoverability
Kategori