[OASIS Issue Tracker] (ODATA-600) Ensure future compatibility by reference to draft-bray-i-json-n (The I-JSON Message Format)

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

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

Ralf Handl updated ODATA-600:
-----------------------------

    Proposal: 
Refer to I-JSON in section on IEEE754compatible format parameter.

[I-JSON] Tim Bray, Ed., "The I-JSON Message Format" draft-bray-i-json-01, 06 January 2014
URL=http://tools.ietf.org/html/draft-bray-i-json-01

  was:
[I-JSON] Tim Bray, Ed., "The I-JSON Message Format" draft-bray-i-json-01, 06 January 2014
URL=http://tools.ietf.org/html/draft-bray-i-json-01


> Ensure future compatibility by reference to draft-bray-i-json-n (The I-JSON Message Format)
> -------------------------------------------------------------------------------------------
>
>                 Key: ODATA-600
>                 URL: https://tools.oasis-open.org/issues/browse/ODATA-600
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format
>    Affects Versions: V4.0_OS
>         Environment: [Proposed]
>            Reporter: Stefan Drees
>            Priority: Minor
>             Fix For: V4.0_ERRATA01
>
>
> To additionally safe guard against interoperability issues caused by the content updates to the JSON RFC (4627 obsoleted by 7159) lifting some restrictions, we should additionally reference the  internet draft draft-bray-i-json-01 (The I-JSON Message Format) which was added by members of the IETF JSON WG to exactly ensure this.



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