Problems in the application of Resolution for Assembly 57 to theSpecification - Proposed editorial fixes

[Mike Edwards <mike_edwards@uk.ibm.com>]

Folks,

Assembly 57 is the issue that decided
that any <binding/> on a <reference/> MUST identify a target
service either via @uri or via binding-specific
mechanisms.

This essentially outlaws the use of
the reference @target attribute with any <binding/> child elements
on the same reference.

It also implies that there is no choosing
between multiple <binding/> child elements, since they all
apply, once they identify a target.

Considering  sca-assembly-1.1-spec-cd01-rev3.doc

Section 5.3.1:

- does not reflect Issue 57 at all.
- the following changes are necessary:

1. Remove lines 866 - 868
(this situation can never occur - if
there is an @target attribute then there can't be any <binding/>
subelement)

2. Change lines 856 - 858
(required to state that <binding/>
subelements cannot exist alongside an @target attribute)

If a reference has a value specified for
one or more target services in its @target attribute,

there MUST NOT be any child <binding/> elements declared for that reference. [ASM50026]

Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  
Email:  mike_edwards@uk.ibm.com

---

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