BINDINGS-23: Proposed resolution v3

Here is a further updated proposal for resolving BINDINGS-23, based
on the discussion on last week's call.  If this is adopted, it will
require adjustment to the wording for the BINDINGS-54 resolution.
The URI matching algorithm for wsdl.service and wsdl.port in the
BINDINGS-54 words would need to include similar words about portType
compatibility and SCA policy compatibility with the service or
reference.

Proposed changes for BINDINGS-23:

In the first bullet (Service) under the /binding.ws/@wsdlElement
description, replace the current text by the following:

  If the binding is for an SCA service, the SCA runtime MUST make
  available to the SCA service all the ports in the WSDL Service that
  . have portTypes which are compatible with the SCA service, and
  . are able to satisfy all the policy constraints of the SCA service.

  A WSDL portType is compatible with an SCA service if and only if
  it satisfies all of the following conditions:
  1. The SCA service interface is remotable.
  2. The operations on the portType are the same as the operations
     on the SCA service interface, with the same operation name,
     same input types (taking order as significant), same output types
     (taking order as significant), and same fault/exception types.
     If the SCA service interface is not a WSDL portType, it is
     mapped to a WSDL portType for the purposes of this comparison.
     The mapping is defined in the relevant SCA specification for the
     interface type.  If the interface cannot be mapped to WSDL, the
     SCA service is not compatible with the WSDL portType.
  3. WSDL 1.1 message parts can point to an XML Schema element
     declaration or an XML Schema type.  When determining compatibility
     between two WSDL operations, a message part that points to an
     XML Schema element is considered to be incompatible with a
     message part that points to an XML Schema type.
  4. If either the portType or the SCA service interface declares
     an SCA callback interface, then both the portType and the
     SCA service interface declare callback interfaces and these
     callback interfaces are compatible according to points
     1 through 3 above.
  The WSDL Service MUST have at least one port that is available to
  the SCA service.  The set of available ports represents a single
  SCA service binding, and the choice of which of the available ports
  are exposed as endpoints for the SCA service is implementation dependent.

  If the binding is for an SCA reference, the SCA runtime MUST make
  available to the SCA reference all the ports in the WSDL Service that
  . have portTypes which are compatible supersets of the SCA reference, and
  . are able to satisfy all the policy constraints of the SCA reference.

  The definition of compatible superset is that given in the
  SCA Assembly Model specification [SCA-Assembly].  The WSDL Service
  MUST have at least one port that is available to the SCA reference.
  The set of available ports represents a single SCA reference binding
  (i.e., it has multiplicity 1), and the choice of which of the
  available ports is used for each invocation through the SCA reference
  is implementation dependent.

In the second bullet (Port) under the /binding.ws/@wsdlElement
description, replace the first sentence of the current text by
the following:

  If the binding is for an SCA service, the portType associated with
  the port MUST be compatible with the SCA service interface, and the
  port MUST be able to satisfy all the policy constraints of the
  SCA service.  If the binding is for an SCA reference, the portType
  associated with the port MUST be a compatible superset of the
  SCA reference interface, and the port MUST be able to satisfy all
  the policy constraints of the SCA reference.

In the third bullet (Binding) under the /binding.ws/@wsdlElement
description, replace the first sentence of the current text by
the following:

  If the binding is for an SCA service, the portType associated with the
  WSDL binding MUST be compatible with the SCA service interface, and the
  port MUST be able to satisfy all the policy constraints of the
  SCA service.  If the binding is for an SCA reference, the portType
  associated with the WSDL binding MUST be a compatible superset of the
  SCA reference interface, and the port MUST be able to satisfy all the
  policy constraints of the SCA reference.

Simon