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

[David Lee <dlee@calldei.com>]

I would find it humors, if it were not so true, so I find it sad that the people writing this actually belive it.

That the JSON representation of numbers is sufficient for data interchange ... 
-->  Simple integers like anything greater then 2^53 cannot be represented in JSON.   Those are *common numbers* ... simply cannot be represented as JSON

That dates and date/times are not important enough to be intrinsic
--> Dates are not interchangeable ... something as 'simple' as a date or date-time has to be invented and agreed on both sides.

How many "simple" data structures in the last 50 years have we interchanged that didnt include dates or largish numbers.

The lack of intrinsic representations for 64 bit numbers (the common in computing nowadays) and dates ... cannot be claimed to solve interchange issues.
( without a layer above where you define how to represent such things as strings etc ... )

Thats my take.
Sorry JSON ... simple you may be... but so is text.   Both are useful for some things.

A useful and comprehensive interchange standard ? ... not for my data ...



----------------------------------------
David A. Lee
dlee@calldei.com
http://www.xmlsh.org

-----Original Message-----
From: Costello, Roger L. [mailto:costello@mitre.org] 
Sent: Thursday, October 17, 2013 7:50 AM
To: xml-dev@lists.xml.org
Subject: [xml-dev] The JSON Data Interchange Format (ECMA standard, October 2013)

Hi Folks,

ECMA has just published: The JSON Data Interchange Format [1].

The specification is 5 pages long. In those 5 pages there are lots of large drawings. 

Here are some interesting snippets:

	JSON is a lightweight, text-based, 
	language-independent data interchange 
	format. It was derived from the ECMAScript 
	programming language, but is programming 
	language independent.

	JSON is a text format that facilitates structured 
	data interchange between all programming 
	languages. 

	Because it is so simple, it is not expected 
	that the JSON grammar will ever change. 
	This gives JSON, as a foundational notation, 
	tremendous stability. 

	It is expected that other standards will refer 
	to this one... Such standards may require 
	specific behaviours. JSON itself specifies no 
	behaviour.

	JSON was inspired by the object literals of 
	JavaScript.
	
	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.

/Roger

[1] http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf


_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php