>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
