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] Commented: (ODATA-342) Can we relax the requirement of int64 numbers being represented as strings in the JSON Format for integer numbers that don't lose precision in ECMAScript when represented as numbers?


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

Stefan Drees commented on ODATA-342:
------------------------------------

Just as an update: Following the formation of the IETF JSON WG there is some discussion on what to change and what to keep while augmenting the JSON RFC to a STD (to break the cyclic reference that seems to have started between the current JSON RFC pointing to ECMAScript, and some edition of ECMAScript pointing to the JSON RFC as normative reference).

One point is enforcing the ECMAScript limitiations of IEEE754 floating point or not onto the format. See eg. http://www.ietf.org/mail-archive/web/json/current/msg00299.html for the as of now latest mail in this thread.

As long as the JSON rep of numbers remains unbounded, this issue (ODATA-342) may well remain closed.

> Can we relax the requirement of int64 numbers being represented as strings in the JSON Format for integer numbers that don't lose precision in ECMAScript when represented as numbers?
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-342
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-342
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format
>    Affects Versions: V4.0_WD01
>         Environment: [Applied]
>            Reporter: Hubert Heijkers
>            Priority: Minor
>             Fix For: V4.0_WD01
>
>
> The current JSON Format specification requires all Int64 numbers to be represented as strings because of the limitation of numbers in JavaScript were these numbers get stored as 64-bit binary format IEEE values and therefore lose precision past 15 digits. However numbers up to that point could still be represented as numbers.

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

        


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