Issue 65: Constraining Type talks about non-optional references but does not define what they are - Updated proposal

["Mark Combellack" <mcombellack@avaya.com>]

Following on from the discussions on the conference call yesterday, here is an updated proposal for Issue 65.

http://www.osoa.org/jira/browse/ASSEMBLY-65

 

 

Original Description of the Issue (from the JIRA)

 

Constraining Type talks about non-optional references but does not define what they are.

 

(References taken from SCA Assembly Specification Committee Draft 01 with RFC 2119 updates (dated 2008-04-22))

 

Page 62: Lines 2150 – 2153                    (page 66: Lines 2281 – 2284 in CD01 Rev 1)

2150 An

2151 implementation may contain additional services, additional optional references and additional

2152 optional properties, but cannot contain additional non-optional references or additional non

2153 optional properties (a non-optional property is one with no default value applied).

 

The above text talks about non-optional references and non-optional properties. It defines non-optional properties but does not define non-optional references.

 

 

 

Updated Proposal

 

Add the following sentence before “a non-optional property is one” on line 2284 in CD01 Rev 1 to add a description of non-optional references.

 

"A non-optional reference is a reference with a multiplicity of 1..1 or 1..N."

 

 

 

Thanks,

 

Mark

Mark Combellack| Software Developer| Avaya | Eastern Business Park | St. Mellons | Cardiff | CF3 5EA | Voice: +44 (0) 29 2081 7624 | mcombellack@avaya.com