Comments on: To XML and Back: Using JSON in Android http://www.linux-mag.com/id/7717/ Open Source, Open Standards Fri, 10 May 2013 08:56:11 +0000 hourly 1 http://wordpress.org/?v=3.1 By: sahana http://www.linux-mag.com/id/7717/#comment-906623 sahana Fri, 26 Apr 2013 07:18:07 +0000 http://www.linux-mag.com/id/7717/#comment-906623 how to integrate forms in android how to integrate forms in android

]]> By: learn http://www.linux-mag.com/id/7717/#comment-151167 learn Sun, 19 Feb 2012 00:29:53 +0000 http://www.linux-mag.com/id/7717/#comment-151167 You are in reality a excellent webmaster. The web site loading speed is amazing. It seems that you're doing any unique trick. Also, The contents are masterwork. you have performed a great job in this matter! You are in reality a excellent webmaster. The web site loading speed is amazing. It seems that you’re doing any unique trick. Also, The contents are masterwork. you have performed a great job in this matter!

]]> By: Lazer http://www.linux-mag.com/id/7717/#comment-111009 Lazer Wed, 04 Jan 2012 10:25:08 +0000 http://www.linux-mag.com/id/7717/#comment-111009 the best thing about RESTful web services is that they are supposed to be free of any representation convention. So its possible to chose the most suitable format for any specific case on the fly (e.g. JSON for mobile apps and XML for business SOA environments..) the best thing about RESTful web services is that they are supposed to be free of any representation convention. So its possible to chose the most suitable format for any specific case on the fly (e.g. JSON for mobile apps and XML for business SOA environments..)

]]> By: otaibinm http://www.linux-mag.com/id/7717/#comment-8036 otaibinm Wed, 30 Nov -0001 00:00:00 +0000 http://www.linux-mag.com/id/7717/#comment-8036 <p>I am sorry but JSON is no way near competing with XML. XML is far superior to JSON!! I don\'t really know on what grounds is the author basing his conclusions! </p> I am sorry but JSON is no way near competing with XML. XML is far superior to JSON!! I don\’t really know on what grounds is the author basing his conclusions!

]]> By: fableson http://www.linux-mag.com/id/7717/#comment-8037 fableson Wed, 30 Nov -0001 00:00:00 +0000 http://www.linux-mag.com/id/7717/#comment-8037 <p>@otalbinm</p> <p>Thanks for your comment -- everyone is entitled to their opinion. Let\'s discuss -- what are your thoughts on why XML is superior? </p> <p>In my view, XML is a super-set of encodings in many respects -- but can be excessive in \"weight\" in typical, tag-heavy usage. JSON is a better fit for some places where CDATA elements are not needed, straight-forward structures are used (or somewhat complex, nested structures also ...), and where you have a JavaScript environment where you would like to \"eval()\" the data, thereby instantiating objects. This can be easier navigated than having to parse an XML structure. While it\'s not for every scenario and every use, JSON is versatile. The mere fact that it is showing up in additional places as alternatives to traditional API\'s is reason enough to give it some consideration.</p> <p>Frank </p> @otalbinm

Thanks for your comment — everyone is entitled to their opinion. Let\’s discuss — what are your thoughts on why XML is superior?

In my view, XML is a super-set of encodings in many respects — but can be excessive in \”weight\” in typical, tag-heavy usage. JSON is a better fit for some places where CDATA elements are not needed, straight-forward structures are used (or somewhat complex, nested structures also …), and where you have a JavaScript environment where you would like to \”eval()\” the data, thereby instantiating objects. This can be easier navigated than having to parse an XML structure. While it\’s not for every scenario and every use, JSON is versatile. The mere fact that it is showing up in additional places as alternatives to traditional API\’s is reason enough to give it some consideration.

Frank

]]> By: ddennedy http://www.linux-mag.com/id/7717/#comment-8038 ddennedy Wed, 30 Nov -0001 00:00:00 +0000 http://www.linux-mag.com/id/7717/#comment-8038 <p>Great. It appears the herd is deciding to trade off verbose, repetitive tags for this nasty morass of quotation marks, quote-escaping, matching braces and brackets, and stray commas. I thought it was bad practice to just eval it negating much of its convenience trump. I am taking a liking toward YAML Tiny for which I can write a parser and serializer where needed without taking a sabbatical. </p> Great. It appears the herd is deciding to trade off verbose, repetitive tags for this nasty morass of quotation marks, quote-escaping, matching braces and brackets, and stray commas. I thought it was bad practice to just eval it negating much of its convenience trump. I am taking a liking toward YAML Tiny for which I can write a parser and serializer where needed without taking a sabbatical.

]]> By: sebastian.ricaldoni http://www.linux-mag.com/id/7717/#comment-8039 sebastian.ricaldoni Wed, 30 Nov -0001 00:00:00 +0000 http://www.linux-mag.com/id/7717/#comment-8039 <p>I believe we are missing the point here. I don\'t think Frank is saying that XML should be erased from the map and replaced with JSON. IMHO JSON is yet another way of doing the same thing, which is, communicating. I agree that JSON will be more suitable than XML in certain scenarios. However, this doesn\'t imply that XML should disappear. On the contrary, XML is the natural evolution of proprietary communication protocols. At the end, I believe that as \'technology experts\' we should always keep our minds wide open to new suggestions and different approaches to accomplish the same thing.<br /> Regards,<br /> Sebastian </p> I believe we are missing the point here. I don\’t think Frank is saying that XML should be erased from the map and replaced with JSON. IMHO JSON is yet another way of doing the same thing, which is, communicating. I agree that JSON will be more suitable than XML in certain scenarios. However, this doesn\’t imply that XML should disappear. On the contrary, XML is the natural evolution of proprietary communication protocols. At the end, I believe that as \’technology experts\’ we should always keep our minds wide open to new suggestions and different approaches to accomplish the same thing.
Regards,
Sebastian

]]>