[OASIS Issue Tracker] Updated: (ODATA-459) State consequences of using IRIs that are not URLs

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

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

Ralf Handl updated ODATA-459:
-----------------------------

    Proposal: 
Using an IRI that is not a URL as an entity-id requires to have in addition an edit link or read link. Even if the edit link is the standard encoded version of the IRI, they are treated as different and need to be represented separately in JSON

The client must be prepared to accept any IRI but that services must use URIs in 4.0 since we have no lossless representation of an IRI in the entity-id header.

  was:Using an IRI that is not a URL as an entity-id requires to have in addition an edit link or read link. Even if the edit link is the standard encoded version of the IRI, they are treated as different and need to be represented separately in JSON


> State consequences of using IRIs that are not URLs
> --------------------------------------------------
>
>                 Key: ODATA-459
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-459
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format, OData Protocol 
>    Affects Versions: V4.0_CSD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_CSD02
>
>


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