OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

    [ http://tools.oasis-open.org/issues/browse/ODATA-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33417#action_33417 ] 

Martin Zurmuehl commented on ODATA-346:

This is a broader topic (not only bound to the collection element). Interesting article about the significance of the order of xml elements: http://www.ibm.com/developerworks/xml/library/x-eleord/index.html#N1009E

In that sense we should specify for OData that the document order (for atom, json, edmx/edm) MUST be preserved by client libraries, i.e the parse order and the document order MUST be identical. Why is that important?
We need it for edm:collection, edm:apply, edm:if, edm:[comparisonOperators], edm:And, edm:Or.
We need it for atom:feed in responses to a request with $orderby the order of the entries should be preserved .
Also for the JSON protocol the document order MUST be preserved.

Delta Responses: Here we state:" The results of a delta query are ordered by the service in such a way as to guarantee consistency when applied in the order provided"

Edm:enumtype is somehow special: if the value attribute is missing, we have this special rule how a client MUST calculate the missing value values. Here the sequence is also significant, if the result should be stable.
BTW: Is this rule helpful?

> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]