By: Michael Schøler

Michael Schøler — Sat, 13 Mar 2010 11:24:12 +0000

I’m not sure what the intent of your blog post is. Clearly

mappings between XML and JSON exists (I’m pretty sure some

geek out there has done a language equivalence proof, at

least to some extent) and as you state multiple

converters/conventions exist. I don’t agree that there are

too many ways out there.

There are many ways to do XML to JSON (and visa versa)

because there are many reasons to do so. Some reasons deal

with huge amounts of data, rendering client side

conversion too slow, some deal with small data amounts

clearly favouring a clientside/javascript implementation.

One has to remember that XML and JSON however deal with

two very distinct areas of interest. XML is very good to

handle document structures and JSON is great for dealing

with data structures. I find XML to JSON particularly

interesting with regards to data structures.

So, in my oppinion, the exchangeability from XML to JSON is useful and definetly here to stay.

Microsoft Visual Studio has the capability to serialize

all objects to XML and JSON (natively supported) – or any

other custom format that would be able to map from a

serializeable object.

us/library/system.runtime.serialization.json.datacontractj

sonserializer.aspx

So going from eg. a C# object to either XML or JSON and

then back to the original C# object is possible.

For an example, see:

Best regards,
Michael

Comments on: David Pollak (from Lift): “There’s no way to convert from XML to JSON because XML contains sequences not expressible in JSON”