• From: Michael Kay <mike@s...>
• To: xml-dev@l...
• Date: Sun, 16 Oct 2011 18:36:59 +0100

 >A simple example I see in practice is using JSON strings to encode 
HTML because JSON itself cant do mixed content in a pretty way.

Of course one reason for using JSON is that (for bizarre reasons) 
browsers ignore the cross-site scripting rules when fetching JSON 
content, so it's a good way to get around unwanted security 
restrictions. That's not to imply that JSON doesn't have other benefits 
(notably the exact fit to the Javascript data model), but it probably 
explains why it's sometimes used for tasks for which it would appear 
badly suited.

Michael Kay
Saxonica

• References:
  • JSON query processing
    • From: Daniela Florescu <dflorescu@m...>
  • Re: JSON query processing
    • From: Liam R E Quin <liam@w...>
  • Re: JSON query processing
    • From: cbullard@h...
  • Re: JSON query processing
    • From: David Lee <dlee@c...>
  • Re: JSON query processing
    • From: cbullard@h...
  • Re: JSON query processing
    • From: David Lee <dlee@c...>
  • Re: JSON query processing
    • From: Chris Burdess <dog@b...>
  • RE: JSON query processing
    • From: "David Lee" <dlee@c...>
  • Re: JSON query processing
    • From: Alex Muir <alex.g.muir@g...>
  • RE: JSON query processing
    • From: "David Lee" <dlee@c...>