Link Details

Link 30381 thumbnail
User 199012 avatar

By dulanov
via blogs.sun.com
Published: Jul 16 2007 / 15:25

JSON shows its greatest weakness. Yes the little semantics JSON datastructures have makes them easy to work with. One knows how to interpret an array, how to interpret a number and how to interpret a boolean. But this is very minimal semantics. It is very much pre web semantics. It works as long as the client and the server, the publisher of the data and the consumer of the data are closely tied together. Why so? Because there is no use of URIs, Universal Names, in JSON. JSON has a provincial semantics. Compare to XML which gives a place for the concept of a namespace specified in terms of a URI.
  • 16
  • 0
  • 9216
  • 67

Comments

Add your comment
User 234827 avatar

jvwilge replied ago:

0 votes Vote down Vote up Reply

Of course JSON has many limitations, but who cares? You use JSON because you want a compact notation that can be used directly in Javascript. When you want to do more advanced stuff you use another notation, it's that simple and you don't need such a long article for it. I voted nothing, it's a well written article but a bit pointless.

User 231351 avatar

bblfish replied ago:

0 votes Vote down Vote up Reply

If you look at the debate on the RESTful web services mailing list it emerged from and that it links to, you will see that it is not perhaps so obvious to many people what the limitations of JSON are. Do you think it could replace XML for instance, as a data format? Why not? It is a lot easier to read and parse, no? What could be the problem with it?

User 400505 avatar

joelp replied ago:

0 votes Vote down Vote up Reply

Ha I have to say I agree with jvwilge, I couldn't care less about the limitations, it works perfectly well as providing a compact notation!

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (16)



Voters Against This Link (0)



    Play Framework
    Written by: Ryan Knight
    Featured Refcardz: Top Refcardz:
    1. Akka
    2. Design Patterns
    3. OO JS
    4. Cont. Delivery
    5. HTML5 Mobile
    1. Akka
    2. JUnit/EasyMock
    3. Java Performance
    4. REST
    5. Java