← Prev in month ← Prev in thread
Next in thread → Next in month →

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

From
OASIS Issues Tracker <>
Date
2013-04-16T10:42:59+00:00
ID
1912386454.1721366108963837.JavaMail.tomcat55@mw00
Thread
[OASIS Issue Tracker] Created: (ODATA-346) Define meaning of collection-valued structural properties to be ordered "List" or "Array"
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
← Prev in month ← Prev in thread
Next in thread → Next in month →