[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:all-tabpanel ] Ralf Handl updated ODATA-820: ----------------------------- Proposal: Define term to advertise indexability Define URL convention for indexing, paren-style for "classic" URL convention and path-style for key-as-segment URL convention, starting with 0 for the first entry - path-to-collection(42) - path-to-collection/42 Remove restriction for containment navigation properties in collections complex types in section 7.1.5 of the CSDL spec as we then have canonical URLs for the containing collection item. was: Define term to advertise indexability Define URL convention for indexing, paren-style for "classic" URL convention and path-style for key-as-segment URL convention, starting with 0 for the first entry - path-to-collection(42) - path-to-collection/42 > 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 > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]