Notions around issue 54 - close to a proposal

[Eric Johnson <eric@tibco.com>]

Staring at issue 54 for several hours, I came up with the following:

The URI(s) for a binding.ws element contained in an service element
SHOULD be determined by the first of these rules that is satisfied:
 1. If the @wsdlElement attribute is present
    1. and refers to a WSDL port element, use the address of the port
    2. and refers to a WSDL service element, use the address for each
port element that the service contains.
 2. If the endpointReference element is present, and has a wsa:Address
element with an absolute URI, use the wsa:Address element value
 3. If there is no endpointReference element
    1) if the @uri attribute is present on the binding.ws element, it
must be relative (Assembly section 9), and the actual URI should contain
the structural URI of the service plus the value of the @uri attribute.
    2) if the @uri attribute is absent, the actual binding URI should
contain the structural URI of the binding.
4. If there is an endpointReference element with a relative wsa:Address
element, compute the address as per #3, and combine the relative address
from wsa:Address with the result.

The URI for a binding.ws.element contained in a reference element SHOULD
be determined by the first of these rules that is satisfied:
 1. If the @wsdlElement attribute is present
   1. and refers to a WSDL port element, use the address of the port
 2. If the endpointReference element is present, and has a wsa:Address
element with an absolute URI, use the wsa:Address element value
 3. and the @uri is present on the binding.ws element, and it is
absolute, use the value of the @uri attribute
 4. and the @uri is present on the binding.ws element, and it is
relative, use the address determined by the targeted service

If this makes sense to people, I can finish up by adding in the
appropriate text about how the endpointReference reference parameters
should be used.

-Eric.