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) Define meaning of collection-valued structural properties to be ordered "List" or "Array"

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

Ralf Handl commented on ODATA-346:

We came across this problem when designing vocabularies. Many terms are collection-valued or have collection-valued properties, and the sequence in which the values are specified in annotations is significant. 

Being forced to use structured types with an artificial sequence number will unnecessarily complicate the annotations.

So we either need a special List(...) type modifier (potentially only allowed within terms and complex types used in terms) or a Core annotation that can be applied to collection-values and expresses the "List" semantics.

Of course client libraries MUST preserve the order of these "Lists".

> 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


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