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

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

Ralf Handl updated ODATA-346:
-----------------------------

        Summary: Order of child elements of <edm:Collection> is significant  (was: Define meaning of collection-valued structural properties to be ordered "List" or "Array")
       Proposal: See summary: order is significant and MUST be preserved by client libraries  (was: See summary: order is significant and MUST be preserved by servers and client libraries)
    Component/s: OData CSDL
                     (was: OData Protocol )
    Description: 
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.

  was:Currently we do not specify whether collections of primitive or complex type are "ordered" or "unordered", i.e. whether the client can rely on the server to preserve the order of values as specified in a PUT request to that property, and whether client libraries have to pick an "ordered" collection construct.


Reduced scope to annotations in CSDL documents.

MAY need to be extended to instance annotations in Atom and JSON.

> Order of child elements of <edm:Collection> is significant
> ----------------------------------------------------------
>
>                 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
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_WD01
>
>
> 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