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: ISSUE 64: Specification inconsistent on whether a default value for Property on a Constraining Type is allowed or not.



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

On May 2, 2008, at 1:49 AM, Mark Combellack wrote:
> RAISER: Mark Combellack
>
> TARGET: SCA Assembly Specification
>
> DESCRIPTION:
>
> (References taken from SCA Assembly Specification Committee Draft 01  
> with RFC 2119 updates (dated 2008-04-22))
>
> The text on Page 61: Lines 2098 - 2101 says:
>
> 2098    The constrainingType is independent of
> 2099     any implementation. Since it is independent of an  
> implementation it cannot contain any
> 2100     implementation-specific configuration information or  
> defaults. Specifically, it cannot contain
> 2101     bindings, policySets, property values or default wiring  
> information.
>
> Bold added my be for emphasis
>
> Lines 2100 – 2101 say that a Constraining Type cannot provide any  
> property values.
>
>
> However, Page 61: Line 2134 lists a default-property-value in the XSD
>
> 2132     <property name="xs:NCName" (type="xs:QName" |  
> element="xs:QName")
> 2133                             many="xs:boolean"?  
> mustSupply="xs:boolean"?>*
> 2134                 default-property-value?
> 2135     </property>
>
>
> The text appears to be inconsistent with the XSD.
>
>
> PROPOSAL:
>
> Mark Combellack| Software Developer| Avaya | Eastern Business Park |  
> St. Mellons | Cardiff | CF3 5EA | Voice: +44 (0) 29 2081 7624 | mcombellack@avaya.com
>
>



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