[OASIS Issue Tracker] Created: (ODATA-185) Nullable attribute should be required to be false for collection valued navigation properties.

Nullable attribute should be required to be false for collection valued navigation properties.
----------------------------------------------------------------------------------------------

                 Key: ODATA-185
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-185
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: OData CSDL v1.0
         Environment: [Proposed]
            Reporter: Michael Pizzo
            Assignee: Michael Pizzo
            Priority: Minor


ODATA-24 simplified relationships by moving association information into the navigation property. In doing so, cardinality was represented by the type of the navigation property being either a single entity or a collection of entities. For a single entity, optionality of the entity (i.e., 0 or 1) is represented by a nullable attribute (whose default is false).

For navigation properties that return collections of entities, nullable=true doesn't make sense; the collection always exists, it may just be empty. Thus, collection-valued navigation properties should either:
1) always specify nullable=false 
2) explicitly prohibit specifying nullable=true, or
3) disallow the nullable attribute

Note that there is precedence for the set of valid attributes depending on the type (i.e., in specifying property facets).

-- 
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