[OASIS Issue Tracker] Commented: (ODATA-378) Support relative IRIs for ids in JSON

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

    [ http://tools.oasis-open.org/issues/browse/ODATA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33353#action_33353 ] 

Ralf Handl commented on ODATA-378:
----------------------------------

We recently had discussions about relative URLs, especially in scenarios involving proxies. Making URLs relative to a header (most likely candidate: Content-Location) would simplify these scenarios.

As the odata.id currently doubles as the readLink and editLink, it would be desirable to extend the above rule to

URIs and IRIs are 
- relative to odata.metadata, if present
- relative to the Content-Location header, if present
- relative to the request URL as the last fallback

> Support relative IRIs for ids in JSON
> -------------------------------------
>
>                 Key: ODATA-378
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-378
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ATOM Format , OData JSON Format
>    Affects Versions: V4.0_CSD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_CSD02
>
>
> The id of an entity is defined to be an opaque IRI. 
> http://tools.ietf.org/html/rfc3987 defines IRI-references to be relative or absolute, but ATOM (http://tools.ietf.org/html/rfc4287#page-19) explicitly disallows the relative form.
> In JSON, we should support relative IRIs. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira