[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: The JSON Data Interchange Format (ECMA standard,October 20

• From: David Lee <dlee@calldei.com>
• To: Michael Kay <mike@saxonica.com>
• Date: Thu, 17 Oct 2013 14:16:43 +0000

------------  Micheal
My reading is that the statement "JSON is based on a subset of ECMAScript " is a statement about the history and origins of the spec, and has no normative effect.

But perhaps this has caused confusion in the past and this is why the new ECMA 404 has a clarifying paragraph on the subject.

Michael Kay
Saxonica
-----------------------

Suppose I interpret it like you do (I dont but thats fine, its unclear).

What I read exactly is 

" JSON is agnostic about numbers. In any programming language, there can be a variety of number types of 
various capacities and complements, fixed or floating, binary or decimal. That can make interchange between 
different programming languages difficult. JSON instead offers only the representation of numbers that 
humans use: a sequence of digits. All programming languages know how to make sense of digit sequences 
even if they disagree on internal representations. That is enough to allow interchange."


I very simply, and strongly, disagree that the first sentences imply the last.
In fact I say they explicitly prove otherwise.    That simply avoiding the issue of representation
doesn't magically make it enough to "allow interchange".
Quite the opposite - by ignoring implementation and not saying anything about it ... 
any implementation can claim "JSON" compliance and not be able to interchange data with other implementations.

For example I dont happen to know of any "JSON" processors that can *actually* handle integers > 53 bits.
or have any defined way of interchanging such numbers.   Maybe some do, but if I want to have my app "allow interchange" with JSON ... the specs are not helping me.


And yes XML has similar problems but at least the specs attempt to address the issue instead of pretending it magically vanishes by ignoring it.

Thats my last rant ... I swear :)

-David

-----------------------------------------------------------------------------
David Lee
Lead Engineer
MarkLogic Corporation
dlee@marklogic.com
Phone: +1 812-482-5224
Cell:  +1 812-630-7622
www.marklogic.com

• Follow-Ups:
  • RE: The JSON Data Interchange Format (ECMA standard, October 2013)
    • From: Hermann Stamm-Wilbrandt <STAMMW@de.ibm.com>

• References:
  • The JSON Data Interchange Format (ECMA standard, October 2013)
    • From: "Costello, Roger L." <costello@mitre.org>
  • RE: The JSON Data Interchange Format (ECMA standard, October 2013)
    • From: David Lee <dlee@calldei.com>
  • Re: The JSON Data Interchange Format (ECMA standard, October 2013)
    • From: Michael Kay <mike@saxonica.com>
  • RE: The JSON Data Interchange Format (ECMA standard,October 2013)
    • From: David Lee <dlee@calldei.com>
  • Re: The JSON Data Interchange Format (ECMA standard, October 2013)
    • From: Michael Kay <mike@saxonica.com>