<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2722" name=GENERATOR></HEAD>
<BODY>
<DIV>
<DIV><FONT face=Arial size=2><SPAN class=576531417-24052006><SPAN
class=329372515-15032007>Here is some interesting background/debunking on the
myth of JSON compactness vs. XML verbosity. </SPAN></SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=576531417-24052006><SPAN
class=329372515-15032007>This is an excerpt from an email I sent to a colleague
early last year:</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=576531417-24052006><SPAN
class=329372515-15032007>===============================================================================</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006></SPAN></FONT> </DIV>
<DIV><SPAN class=576531417-24052006><FONT face=Arial size=2>I went to the json
"see for yourself" page: </FONT><A title=http://www.json.org/example.html
href="BLOCKED::http://www.json.org/example.html"><FONT face=Arial
size=2>http://www.json.org/example.html</FONT></A><FONT face=Arial
size=2> to compare the Json equivalent of XML.</FONT></SPAN></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=576531417-24052006>I copied each of the
examples into notepad and wrote down the size-on disk:</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=576531417-24052006>json size
(bytes) XML size
(bytes) (json size)/(XML
size)</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006>===================================================</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006>604
630
95%</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006>252
221 114%</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006>630
656
96%</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006>3554 10708 33%</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006>898 1150
78%</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=576531417-24052006>AVG (json size)/(XML
size)</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006>=====================</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006>83.2%</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=576531417-24052006>Based on an average
size compaction to 83.2% of the XML size. Also, if you look at the 4th example
they give (line 4 of the table above), they did a Json version of web.xml. Now
web.xml is a notoriously bad XML design. It basically doesn't use ANY
attributes, so you get pretty nasty tag bloat. So if we drop the 4th comparison,
as being kinda silly, we get an average compaction to 95.4% of the original
size. Is saving 4.5% really a big advantage?</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=576531417-24052006>I also saw several
statements on the json web page that I would put in the "wacky" bin. This may
just be personal preference, but I found the XML documents much easier to read
than their json equivalents. The Json looks, to me, like "code", kinda like a
snippet of PERL or something.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006><geeky></SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=576531417-24052006>Anyway, it
seems clear that being able to easily marshal an object representation of your
data makes it much easier to develop software in any programming language. But
it seems to me that json is munging this idea up with the wire format, which to
me are orthogonal concerns.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006></geeky></SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=576531417-24052006></SPAN></FONT> </DIV></DIV>
<DIV align=left>
<P class=MsoNormal align=left><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Geoff Hendrey</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Software Architect<BR><B><SPAN
style="FONT-WEIGHT: bold">deCarta</SPAN></B><BR>Four <?XML:NAMESPACE PREFIX = U1
/><U1:STREET u2:st="on"><U1:ADDRESS u2:st="on"><?xml:namespace prefix = ns0 ns =
"urn:schemas-microsoft-com:office:smarttags" /><ns0:Street w:insAuthor="brent"
w:insDate="2007-02-05T19:53:00Z" w:endInsAuthor="brent"
w:endInsDate="2007-02-05T19:53:00Z"><ns0:address w:insAuthor="brent"
w:insDate="2007-02-05T19:53:00Z" w:endInsAuthor="brent"
w:endInsDate="2007-02-05T19:53:00Z"><?xml:namespace prefix = st1 ns =
"urn:schemas-microsoft-com:office:smarttags" /><st1:Street
w:st="on"><st1:address w:st="on">North Second
Street</U1:ADDRESS></U1:STREET></st1:address></st1:Street></ns0:address></ns0:Street>,
<U1:ADDRESS u2:st="on"><U1:STREET u2:st="on"><ns0:address w:insAuthor="brent"
w:insDate="2007-02-05T19:53:00Z" w:endInsAuthor="brent"
w:endInsDate="2007-02-05T19:53:00Z"><ns0:Street w:insAuthor="brent"
w:insDate="2007-02-05T19:53:00Z" w:endInsAuthor="brent"
w:endInsDate="2007-02-05T19:53:00Z"><st1:address w:st="on"><st1:Street
w:st="on">Suite</U1:STREET></st1:Street></ns0:Street></st1:address></ns0:address>
950<BR><ns0:place w:insAuthor="brent" w:insDate="2007-02-05T19:53:00Z"
w:endInsAuthor="brent" w:endInsDate="2007-02-05T19:53:00Z"><U1:PLACE
u2:st="on"><U1:CITY u2:st="on"><ns0:City w:insAuthor="brent"
w:insDate="2007-02-05T19:53:00Z" w:endInsAuthor="brent"
w:endInsDate="2007-02-05T19:53:00Z">San Jose</ns0:City></U1:PLACE></U1:CITY>,
<U1:STATE u2:st="on"><ns0:State w:insAuthor="brent"
w:insDate="2007-02-05T19:53:00Z" w:endInsAuthor="brent"
w:endInsDate="2007-02-05T19:53:00Z">CA</U1:STATE></ns0:State>
<U1:POSTALCODE u2:st="on"><ns0:PostalCode w:insAuthor="brent"
w:insDate="2007-02-05T19:53:00Z" w:endInsAuthor="brent"
w:endInsDate="2007-02-05T19:53:00Z">95113</ns0:PostalCode></U1:POSTALCODE></ns0:place><BR>office
408.625.3522<BR></SPAN></FONT><A title=http://www.decarta.com/
href="blocked::http://www.decarta.com"><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">www.decarta.com</SPAN></FONT></A><?xml:namespace
prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p></P>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"> </SPAN><o:p></o:p></FONT></P></U1:ADDRESS></DIV>
<DIV> </DIV></BODY></HTML>