[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:all-tabpanel ]

Ralf Handl updated ODATA-799:
-----------------------------

    Description: 
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

  was:
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


> 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
>            Assignee: Ralf Handl
>              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



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