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] (ODATA-820) Allow indexing into collections

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

Michael Pizzo commented on ODATA-820:

Applied to [URL], [Protocol] and [OData-CoreVoc].

Do we need to define a context URL for this?  For primitive types we can just use the context url for the type. For complex types we could do the same thing, but if the complex type contained a nav prop the context url wouldn't have a base for it.  Still, if we do introduce a new context url, it should probably only be returned for 4.01 requests (4.0 requests should just return the context url for the complex type).

> 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: Set Operations, New Query Capabilities
>            Reporter: Ralf Handl
>            Assignee: Michael Pizzo
>              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

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