[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=63077#comment-63077 ] Ralf Handl commented on ODATA-820: ---------------------------------- Ad 1: if we see the context url as a pointer to structure information (spec text: " identifying the relevant portion of the metadata document") we don't need the index because the complex type name is sufficient. Side question: why did we include key property values in context URLs for contained entities? Ad 2: wouldn't want to forbid this, so ABNF should allow this URL pattern. > 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 (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]