OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-assembly message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [sca-assembly] [NEW ISSUE] Defintion of Composite ReferenceMultiplicity contains conflicting information


Looks good. One stumbling block that threw me initially was this line:

multiplicity : 0..1|1..1|0..n|1..n (0..1)

I initially read it to mean that the default for multiplicity was 0..1, when in fact the (0..1) notation is the cardinality of the attribute itself, not the default value of the attribute. Of course the problem with using words like optional and required to indicate attribute cardinality is that they are reserved RFC2119 words, so I have no other suggestions. Just want to make sure that others don't get tripped up also.


Dave Booz
STSM, BPM and SCA Architecture
Co-Chair OASIS SCA-Policy TC and SCA-J TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093
e-mail:booz@us.ibm.com

Inactive hide details for Mike Edwards ---01/13/2009 09:39:11 AM---Target:  sca-assembly-1.1-spec-cd01-rev8.pdf Raiser: Mike EdMike Edwards ---01/13/2009 09:39:11 AM---Target: sca-assembly-1.1-spec-cd01-rev8.pdf Raiser: Mike Edwards


From:

Mike Edwards <mike_edwards@uk.ibm.com>

To:

"OASIS Assembly" <sca-assembly@lists.oasis-open.org>

Date:

01/13/2009 09:39 AM

Subject:

[sca-assembly] [NEW ISSUE] Defintion of Composite Reference Multiplicity contains conflicting information






Target: sca-assembly-1.1-spec-cd01-rev8.pdf

Raiser: Mike Edwards

Description:

The description of the Composite Reference @multiplicity attribute between lines 1447-1460 conflicts
with both the pseudo-schema and the XSD for SCA Assembly.

The current text implies that the attribute is required (ie (1..1) ). The text does not describe a default
value when one is declared in the XSD.

Proposal:

Modify the text between 1447-1460 to read as follows:

multiplicity : 0..1|1..1|0..n|1..n (0..1)
- Defines the number of wires that can connect the reference to target services. The multiplicity can have the following values

o 0..1 – zero or one wire can have the reference as a source

o 1..1 – one wire can have the reference as a source

o 0..n - zero or more wires can have the reference as a source

o 1..n – one or more wires can have the reference as a source

The default value for the @multiplicity attribute is 1..1.

The value specified for the multiplicity attribute of a composite reference MUST be compatible with the multiplicity specified on each of the promoted component references, i.e. the multiplicity has to be equal or further restrict. So multiplicity 0..1 can be used where the promoted component reference has multiplicity 0..n, multiplicity 1..1 can be used where the promoted component reference has multiplicity 0..n or 1..n and multiplicity 1..n can be used where the promoted component reference has multiplicity 0..n., However, a composite reference of multiplicity 0..n or 1..n cannot be used to promote a component reference of multiplicity 0..1 or 1..1 respectively. [ASM60011]


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







[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]