[OASIS Issue Tracker] Commented: (ODATA-346) Define meaning of collection-valued structural properties to be ordered "List" or "Array"

[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:comment-tabpanel&focusedCommentId=33049#action_33049 ] 

Michael Pizzo commented on ODATA-346:
-------------------------------------

Requiring that the service preserve order is a significant burden that many services will not be able to support.  In OData V3 we always intended collection-valued properties to be unordered. I don't think clients can assume collection-valued properties are ordered.

> Define meaning of collection-valued structural properties to be ordered "List" or "Array"
> -----------------------------------------------------------------------------------------
>
>                 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 Protocol 
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_WD01
>
>
> 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.

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