[OASIS Issue Tracker] Updated: (ODATA-543) Nullable attribute on collection property should specify whether collection can contain null values

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/ODATA-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-543:
--------------------------------

    Environment: [Proposed][Applied For Review]  (was: [Proposed])

> Nullable attribute on collection property should specify whether collection can contain null values
> ---------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-543
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-543
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Sub-task
>          Components: OData CSDL
>    Affects Versions: V4.0_CS01
>         Environment: [Proposed][Applied For Review]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_CSD03
>
>
> We currently state that the Nullable attribute is not allowed for collection-valued properties. Elsewhere we say that facets (such as maxlength, etc.) apply to the individual elements within a collection. It would be useful, and consistent, to say that the nullable attribute, when used on a collection-valued property, applies to elements in the collection and specifies whether the collection can contain nulls.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira