TABLE OF CONTENTS This appendix describes the protocol bindings for HELD. Two bindings are included: an HTTP binding that uses a web services form, and a BEEP binding that can be used for more permanent client/server connections.
This section defines an HTTP (see Reference 1) binding for the HELD protocol, which all conforming implementations must support. This binding takes the form of a Web Service (WS) that can be described by the Web Services Description Language (WSDL) document that is included in this section.
The three request messages are carried in this binding as the body of an HTTP POST request. The MIME type of both request and response bodies should be application / xml, except that a PIDF-LO document should have the MIME type application / pidf+xml.
The LIS should populate the HTTP headers so that they are consistent with the contents of the message. In particular, the Expires and cache control headers should be used to control the caching of any PIDF-LO document. The HTTP status code should have the same first digit as any contextResponse or error body included, and it should indicate a 2xx series response when a PIDF-LO document is included.
This binding also includes a default behavior, which is triggered by a GET request, or a POST with no request body. If either of these queries is received, the LIS must attempt to provide a PIDF-LO document, as if the request was a location request.
This binding must use...
