[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
RE: [xml-dev] Towards XML 2.0
- From: "David Lee" <dlee@calldei.com>
- To: "'Michael Kay'" <mike@saxonica.com>, <xml-dev@lists.xml.org>
- Date: Tue, 7 Dec 2010 19:09:23 -0500
What Mike said +1 ...
While I am not opposed to JSON ... but there is value in not having to
change data formats "though the piupe".
If the data is 100% JSON client & server there isnt much advantage a "simple
XML" except a checkbox.
But with the data I work with (and I think its not uncommon), the Server
side's data is very "enterprisy".
We vastly simplify it to send to the client. Right now at the very last
stage I'm transforming it to JSON.
But if I could leave it as XML as it goes over the wire, it's a big benefit.
The XML stack on the *server* is very powerful, and is not matched by JSON
tools.
If the data can 'stay XML All the way through' there's a lot of efficiency
to be gained, in processing tools, in languages, in experience sets etc.
I'd vastly prefer to simplify the XML as it goes out to the (in my case
mobile) clients into a 'minimum profile' and stil keep it XML then convert
it to JSON and back on the reverse. That's one less barrier to confusion.
Which brings up confusion.
*documenting* data formats is a big deal and a lot of work and hidden
expense (the expense being mostly mis-understanding the documentation). If
we can keep the documents (and the associated validation, like schemas etc)
to a single data format language theres a huge gain, even if the format is
"simple".
This is why I see a great value in a "mimimal XML" even if its no more
"powerful" then the equivilent JSON.
----------------------------------------
David A. Lee
dlee@calldei.com
http://www.xmlsh.org
-----Original Message-----
From: Michael Kay [mailto:mike@saxonica.com]
Sent: Tuesday, December 07, 2010 6:07 PM
To: xml-dev@lists.xml.org
Subject: Re: [xml-dev] Towards XML 2.0
> I think we need to focus on the greatest need. I considered
> responding to the earlier "hysteria" comment by saying that most folks
> on this thread, and certainly James Clark's post were not "running
> scared" of JSON. For my part, I embrace it, and I know quite a few
> others do who still want XML to be simplified.
>
I don't think it's a case of "running scared". I think it's a case of
trying to learn from JSON how much could be achieved with something much
simpler than we have today, but without losing the things we really
value about XML.
Michael Kay
Saxonica
_______________________________________________________________________
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
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]