AI#0237 EndpointType ResponseLocation clarification

[Eric Tiffany <eric.tiffany@ieee-isto.org>]

Briefly, this issue arose because an implementer interpreted the metadata
spec to mean that ResponseLocation should only be omitted for the SOAP
binding, and that the ResponseLocation be specified in metadata for other
bindings.

Proposed text to resolve this AI:

At line 238 in Metadata we have now:

    The ResponseLocation attribute is used to enable different endpoints
    to be specified for receiving request and response messages associated
    with a protocol or profile, not as a means of load-balancing or
    redundancy (multiple elements of this type can be included for this
    purpose). When a role contains an element of this type pertaining to a
    protocol or profile for which only a single type of message (request
    or response) is applicable, then the ResponseLocation attribute is
    unused.

After this I propose adding the following:  "If the ResponseLocation
attribute is omitted, any response messages associated with a protocol or
profile may be assumed to be handled at the URI indicated by the Location
attribute."

ET 
-- 
____________________________________________________
Eric  Tiffany             |  eric@projectliberty.org
Interop Tech  Lead        |  +1 413-458-3743
Liberty Alliance          |  +1 413-627-1778 mobile