ISSUE 16: Component URI is not well described --- Proposal for Binding URIs

I took an action at the Assembly F2F
to produce a proposal for how binding URIs would be handled with the proposed
new approach to infoset and alias URIs.  Here is that proposal.

Bindings can specify a uri attribute.
 This attribute does not contribute to the infoset URI that is derived
from the component/service/binding name combination, or to any aliases
defined for this infoset URI.  If the uri attribute is present on
a binding element, it may be used by the binding to derive an endpoint
URI.

The rules for deriving endpoint URIs
are binding-specific and are defined in the appropriate binding specifications.
 Endpoint URIs may be derived from the infoset URI (or any aliases
that are defined), the binding URI, or some combination of these.

For binding.sca, the rules are as follows.
 If the binding uri attribute is specified on a reference, it identifies
the target service in the SCA domain by specifying either the service's
infoset URI or an alias for the infoset URI.  If the binding uri attribute
is specified on a service, it is ignored.

    Simon

Simon C. Nash, IBM Distinguished Engineer

Member of the IBM Academy of Technology

Tel. +44-1962-815156  Fax +44-1962-818999

Unless stated otherwise above:

IBM United Kingdom Limited - Registered in England and Wales with number
741598. 

Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU