[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Issue Comment Edited: (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=33422#action_33422 ] Ralf Handl edited comment on ODATA-346 at 5/14/13 1:22 PM: ----------------------------------------------------------- We do have some situations in CSDL where the document order has semantics, e.g. for EnumType members that don't specify a Value attribute. They are numbered implicitly in document order, and this numbering is used for $orderby. Also for the <edm:If> expression the order of the two or three child elements has semantics: first is condition, second is "then", third is "else". Similar for <edm:Apply>: order of function parameters is significant for the predefined odata.concat function. Note: all these situations would be translated into JSON arrays by a typical XML-JSON translation, and these ARE ordered. was (Author: ralfhandl): We do have some situations in CSDL where the document order has semantics, e.g. for EnumType members that don't specify a Value attribute. They are numbered implicitly in document order, and this numbering is used for $orderby. Also for the <edm:If> expression the order of the two or three child elements has semantics: first is condition, second is "then", third is "else". Similar for <edm:Apply>: order of function parameters is significant for the predefined odata.concat function. > 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]