[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-799) Define Key-As-Segment URL convention for resource paths
[ https://issues.oasis-open.org/browse/ODATA-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59674#comment-59674 ] Ralf Handl commented on ODATA-799: ---------------------------------- Bound functions on entity sets pose a problem: GET /Categories/Model.TopSelling(Year=2015) With paren-key syntax this calls the bound function Model.TopSelling with parameter Year=2015. With key-as-segment this could also retrieve the category with key 'Model.TopSelling(Year=2015)' > Define Key-As-Segment URL convention for resource paths > ------------------------------------------------------- > > Key: ODATA-799 > URL: https://issues.oasis-open.org/browse/ODATA-799 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData URL Conventions > Affects Versions: V4.0_ERRATA02 > Reporter: Ralf Handl > Labels: AdoptionBlocker > Fix For: V4.1_WD01 > > > Typical web APIs use path segments for key access to collection elements: > ~/Users > ~/Users/42 > Specify how such a URL convention would look like, considering > - multi-part keys > - the Edm primitive type system -- 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]