W3C home > Mailing lists > Public > www-tag@w3.org > March 2013

Re: Atom vs Polyglot

From: Eric J. Bowman <eric@bisonsystems.net>
Date: Mon, 25 Mar 2013 23:16:45 -0600
To: Larry Masinter <masinter@adobe.com>
Cc: "julian.reschke@gmx.de" <julian.reschke@gmx.de>, Noah Mendelsohn <nrm@arcanedomain.com>, Robin Berjon <robin@w3.org>, Alex Russell <slightlyoff@google.com>, "www-tag@w3.org List" <www-tag@w3.org>, Sam Ruby <rubys@intertwingly.net>, Henri Sivonen <hsivonen@iki.fi>, Jeni Tennison <jeni@jenitennison.com>, Maciej Stachowiak <mjs@apple.com>
Message-Id: <20130325231645.24d200fd4917a92e8bcf05f8@bisonsystems.net>
Larry Masinter wrote:
> I don't have any problem with ATOM today. However, I think the
> community is facing a transition from XML to JSON as a preferred
> method of language-independent exchange of structured data. If ATOM
> were to be designed today -- carrying metadata and control structures
> (about content) and also carrying marked up rich text, I'd look for a
> protocol that used JSON for the structured data and HTML for the
> marked up or active next.

And I'd look for something like XML Atom for archiving user-generated
content.  Decoding SGML-ancestry markup, particularly XML, will likely
be easily done in 50-75 years, the advantage of declarative code.  An
imperative Atom format carrying control structures about content,
becomes lost data over the long term if the interpreter is separated.

IOW, an XML parser will always be an XML parser and Atom ain't that
hard to figure out; but I expect what browsers do with any given JSON
Atom will always be in flux, with potential semantic loss over time due
to this API versioning not being tied to the data.  Any corruption in
an old-old Atom store would be readily apparent as malformed XML...

If my system benefits from using JSON Atom at the UI layer, I'd do it,
but the back-end storage is expected to last decades, and in my book
XML has the upper hand there.  I'm not as anti-JSON as I come across,
it's just pushback against the notion that JSON obsoletes XML, when I
see uses for both.  I've never understood the XML hate, I took to it
like a duck to water...

Received on Tuesday, 26 March 2013 05:17:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:54 UTC