Introduction Best Practices | OGC

30 Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved. • to provide a common way to encapsulate messages and add the metadata needed to automatically process the message content. In the following we are going to describe these schema elements.

8.2 Message parameters

First of all, we introduce common message container elements. These elements contain the XML encoded message while providing a minimum of metadata, which enables the receiver to process the message automatically. We recommend using these message containers whenever exchanging messages between OGC services with or without a WNS in the middle.

8.2.1 NotificationMessage

The NotificationMessage should be used for one-way communication. Figure 18: NotificationMessage in XMLSpy notation The parameters of the response are described in the following table. Copyright © 2006 Open Geospatial Consortium, Inc. All Rights Reserved. 31 Table 18: Parameters in a NotificationMessage Names a Definition Data type and values Multiplicity and use ServiceDescri ption Contains metadata enabling the receiver of the message to automatically process the message. The ServiceType should contain the OGC abbreviation for the service that sent the message, e.g. “SPS” or “SAS”. The ServiceTypeVersion shall indicate the specification version of the sending service e.g. “1.0.0” or “1.1.0”. The ServiceURL shall contain the URL of the sending service. Complex: • ServiceType: XML token • ServiceTypeVersion: XML token • ServiceURL: XML anyURI One mandatory Payload Contains the actual message. The structure of this message has to be described in the specification of the message originating service. Any XML element belonging to any namespace. One mandatory a The name capitalization rules being used here are specified in Subclause 11.6.2 of [OGC 05-008].

8.2.2 CommunicationMessage

The CommunicationMessage should be used for two-way-communication. Whenever a reply for a message is needed the sender should make use of the CommunicationMessage . The receiver should know what kind of reply message is expected, create the according ReplyMessage see clause 8.2.3 and send it back to the given CallbackURL . Whether two-way-communication is supported by a service or not depends on the specification of that service. Although a WNS can be used to deliver the CommunicationMessage , the ReplyMessage has to be sent via HTTP Post directly to the given CallbackURL .