[OASIS Issue Tracker] (ODATA-799) Define Key-As-Segment URL convention for resource paths

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

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

Michael Pizzo commented on ODATA-799:
-------------------------------------

Proposal is to define a precedence that would say that, if a function "Model.TopSelling()" is defined, it would be invoked. Services are encouraged not to allow key values that conflict with defined actions/functions.

I would propose that we not try to extend key-as-segment to multi-part keys. If you have multi-part keys you fall back to the parens syntax.

Would also recommend services continue to support the parens syntax in addition to the key-as-segment.

> 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
>         Environment: Simplified Syntax
>            Reporter: Ralf Handl
>            Assignee: Michael Pizzo
>              Labels: AdoptionBlocker
>             Fix For: V4.01_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
> - bound actions/functions on entity-set level
> - context URLs for contained entities which include the key
> - relative context URLs
> Consider notation that allows context URLs to be relative to the service root.



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