Joe Said:
> I would agree with Mike and say that for exhibit display
> purposes its best to go with simple and standard access. XML
> is good because almost anything can read it but it has to be
> well documented. I wouldn't go with JSON as it seems more
> complex than necessary.
JSON is targetted for use as a data-interchange format, for which it's
arguably better than XML. For exchange documents with inline markup
though, XML is better. JSON is also meant to be easier to parse using
Javascript, and can be called cross-site if you import it with its own
<script> tag, which gets around the Javascript same-source security
policy.
So it would probably depend on whether you're dealing with simple data
or documents, and how the data is likely to be consumed. It may be best
to do both (indeed, this is what the BBC is doing with its upcoming
schedule data API).
This e-mail and attachments are intended for the named addressee only and are confidential. If you have received this e-mail in error please notify the sender immediately, delete the message from your computer system and destroy any copies. Any views expressed in this message are those of the individual sender and may not reflect the views of the National Museum of Science & Industry. This email has been scanned for all viruses by the MessageLabs Email Security System.
**************************************************
For mcg information and to manage your subscription to the list, visit the website at http://www.museumscomputergroup.org.uk
**************************************************
|