[OASIS Issue Tracker] Created: (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?

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

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
         Environment: [Proposed]
            Reporter: Hubert Heijkers
            Priority: Minor


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