[OASIS Issue Tracker] Updated: (ODATA-346) Order of child elements of <edm:Collection> MUST be preserved

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

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

Michael Pizzo updated ODATA-346:
--------------------------------

     Summary: Order of child elements of <edm:Collection> MUST be preserved  (was: Order of child elements of <edm:Collection> is significant)
    Proposal: See summary: order may be significant and MUST be preserved by client libraries  (was: See summary: order is significant and MUST be preserved by client libraries)

modified slightly; we shouldn't say that the order is significant (or not), just that it must be preserved by client libraries.

> Order of child elements of <edm:Collection> MUST be preserved
> -------------------------------------------------------------
>
>                 Key: ODATA-346
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-346
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL
>    Affects Versions: V4.0_WD01, V4.0_CSD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_CSD02
>
>
> Terms often require lists of primitive or complex values in which the order of entries is significant, e.g. when defining a leveled hierarchy for data aggregation.
> Making the order of child elements in a <Collection> element significant avoids the need of always using a complex type with a sequence property to express the order.

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