[OASIS Issue Tracker] (ODATA-1028) 4.3.4: clarify relative URLs when a type-cast segment is present

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

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

Ralf Handl commented on ODATA-1028:
-----------------------------------

Just realized that 4.3.4 contradicts 4.4, http://docs.oasis-open.org/odata/odata/v4.01/csprd01/part2-url-conventions/odata-v4.01-csprd01-part2-url-conventions.html#_Toc470093604:

The entity-id specified by $id may be expressed absolute or relative to the request URL.

So we have two different resolution mechanisms for the $id system query option:
- relative to the service root for paths containing /$entity
- relative to the request URL for paths ending in /$ref

This is less than consistent.

> 4.3.4: clarify relative URLs when a type-cast segment is present
> ----------------------------------------------------------------
>
>                 Key: ODATA-1028
>                 URL: https://issues.oasis-open.org/browse/ODATA-1028
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData URL Conventions
>    Affects Versions: V4.0_ERRATA03
>         Environment: Proposed
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>             Fix For: V4.01_CSD02
>
>
> 4.3.4 Resolving an Entity-Id states that 
> The entity-id may be expressed as an absolute IRI or relative to the service root URL.
> Example 23: request the entity representation for an entity-id
> http://host/service/$entity?$id=Products(0)
> This was correct until we introduced type-cast segments after $entity with ODATA-528. 
> Now relative URLs should rather be relative to the request URL, as in all other places.



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