Re: Best practice for data encoding?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 6/6/06, Hallam-Baker, Phillip <pbaker@xxxxxxxxxxxx> wrote:

At this point XML is not a bad choice for data encoding. I would like to see the baroque SGML
legacy abandonded (in particular eliminate DTDs entirely). XML is not a perfect choice but is is
not a bad one and done right can be efficient.

JSON <http://www.json.org> seems like a better fit for the use cases
discussed here. You get better data types, retain convenient ASCII
notation for unicode characters, and lose lots of XML baggage.

draft-crockford-jsonorg-json-04.txt is in the RFC queue, headed for
informational status.

--

Robert Sayre

_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]