RE: [xml-dev] Maximally Consumable Data

[Robert Koberg <rob@koberg.com>]

Hi,

In your article on JSON, you have a section "How is the Data in JSON
Extracted?" -- well you leave out the fact that it is simply a string
from some server. It has to be eval'd to become an object.

XML can be just a string that can be loaded into an XML Document. The
benefits of JSON, I see, is that is smaller, easier to load and easier
to work with. But, you have to 'eval' it making a potential security
threat. If you load XML and process it using DOM or with XSL, you don't
have a security issue (unless you are using it to create JS which you
will then eval...).

best,
-Rob


On Mon, 2008-04-07 at 07:01 -0400, Costello, Roger L. wrote:
> Hi Bryan,
> 
> Thanks for your excellent comments!
> 
> >>    * JSON Version: format your data using JSON. 
> >> That will make your data consumable by JavaScript 
> >> and Ajax applications.
> 
> > XML is generally consumable by the same environments 
> > that JSON is consumable by, furthermore both JSON and 
> > XML are hierarchical in nature.
> 
> I talk a bit about this in my article, "Why JSON is Important to You!"
> (http://www.xfront.com/json/).  Here's the relevant section:
> 
> But Ajax Applications Can Process Data Formatted as XML, so Why Bother
> With JSON?
> 
> If the data is formatted as XML then Ajax is limited to fetching data
> from the same domain (website) that the Ajax application came from.
> 
> If the data is formatted as JSON then Ajax can travel across domains.
> That is, Ajax can access data from anywhere. Think of the power of
> this: a single Ajax application, running in your browser, can reach out
> and grab data from an unlimited number of web services, and present it
> in your browser in a coherent fashion. Awesome!