OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (ODATA-1056) Key-as-Segment with Referential Constraints

     [ https://issues.oasis-open.org/browse/ODATA-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-1056:

    Environment: Applied  (was: Proposed)

> Key-as-Segment with Referential Constraints
> -------------------------------------------
>                 Key: ODATA-1056
>                 URL: https://issues.oasis-open.org/browse/ODATA-1056
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: URL Conventions
>    Affects Versions: V4.01_CSD01
>         Environment: Applied
>            Reporter: Ralf Handl
>             Fix For: V4.01_CSD02
> Part 2 section 4.3.3 allows omitting key values that are implicitly specified by referential constraints to key values provided in previous path segments:
> https://host/service/Orders(1)/Items(OrderID=1,ItemNo=2)
> https://host/service/Orders(1)/Items(2)
> The shorter form is preferred for parentheses-key syntax, and both are allowed.
> We cannot give that choice for key-as-segment style because the number and order of path segments must be deterministic, so it is either
> https://host/service/Orders/1/Items/1/2
> or
> https://host/service/Orders/1/Items/2
> Shorter is better, so it must be the second.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]