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

[Scott Vorthmann <scottv@tibco.com>]

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

On May 2, 2008, at 1:57 AM, Mark Combellack wrote:
> RAISER: Mark Combellack
>
> TARGET: SCA Assembly Specification
>
> DESCRIPTION:
>
> 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
> 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.
>
>
> PROPOSAL:
>
> Replace the bracketed text on Page 62: Line 2153 with the following  
> text.
>
> “A non-optional reference is a reference with a multiplicity of 1..1  
> or 1..N. A non-optional property is a property with no default value  
> applied.”
>
> Mark Combellack| Software Developer| Avaya | Eastern Business Park |  
> St. Mellons | Cardiff | CF3 5EA | Voice: +44 (0) 29 2081 7624 | mcombellack@avaya.com