[OASIS Issue Tracker] (ODATA-820) Allow indexing into collections

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/ODATA-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60763#comment-60763 ] 

Michael Pizzo commented on ODATA-820:
-------------------------------------

We can't assume a service can index into collections, we just want to provide a way for those that can to do so.
So, for example, we can only relax restriction on navigation properties on complex types within a collection *if* the service can index into that collection.
We need to define a vocabulary for clients to determine this.
Also need to clarify whether both key syntaxes are supported/allowed (in which case a client needs to know which the service supports -- same as key syntax? just support key-as-segment and try to minimalize the use of parens?)
Note this syntax can work with primitive or complex types, but not entity types (as there is already a syntax for indexing into them by key)


> Allow indexing into collections
> -------------------------------
>
>                 Key: ODATA-820
>                 URL: https://issues.oasis-open.org/browse/ODATA-820
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: New Feature
>          Components: OData URL Conventions, Vocabularies
>    Affects Versions: V4.0_ERRATA02
>         Environment: New Query Capabilities
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>              Labels: Extension, request_tc_discussion
>             Fix For: V4.01_WD01
>
>
> Allow indexing into collections.
> If servers can guarantee a stable order, they could advertise this via an annotation.
> This could be combined with ETags to identify the state the client is referring to.
> This might be combined with $orderby to let the client choose the order.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)