[ http://tools.oasis-open.org/issues/browse/ODATA-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralf Handl updated ODATA-346:
-----------------------------
Proposal:
"Client libraries MUST retain the order of objects within an array." in JSON, and "Client libraries MUST preserve elements in document order." for ATOM and XML/CSDL.
We don't impose any ordering constraints around xml attributes or name/value pairs within JSON objects.
We don't imply any *semantics* around the ordering of elements within a collection (i.e., that the order of complex types within a collection is meaningful and MUST be preserved by the service).
was:
"Client libraries MUST retain the order of objects within an array." in JSON, and "Client libraries MUST preserve elements in document order." for ATOM and XML/CSDL.
We don't impose any ordering constraints around xml attributes or JSON objects.
We don't imply any *semantics* around the ordering of elements within a collection (i.e., that the order of complex types within a collection is meaningful and MUST be preserved by the service).
> 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
