Comments on: Json.NET 1.1: Converting between XML and JSON

By: lb

lb — Mon, 24 Jul 2006 03:27:21 +0000

now if only SQL Server (et al.) had a built-in “ForJSON” that worked the same (only better) than “ForXML”

By: Christopher Steen

Christopher Steen — Fri, 21 Jul 2006 04:05:45 +0000

Link Listing – July 20, 2006

Announcing Teamprise 1.1 and Vault 3.5 [Via: ]
Creating Smaller Virtual Machines [Via: ]
Customizing…

By: James Newton-King

James Newton-King — Wed, 19 Jul 2006 21:03:16 +0000

Yes that could be a problem. The same issue also applies to single text nodes suddenly having additional content and no longer being a name/value against an element. I was thinking about having an overload to take a schema, which could then place nodes with the potential to have more than one in an array.

By: Simon Willison

Simon Willison — Wed, 19 Jul 2006 08:05:59 +0000

James’ conversion rules are pretty good, but there’s one edge case you need to stay aware of relating to the multiple-node-array thing. If you have a document which normally returns multiple nodes (say a set of tags) you might write code against the JSON conversion that expects an array – but this will break if only a single category is present in the XML as the convertor will not know to turn it in to an array. This can be quite a nasty gotcha if you aren’t expecting it.

By: Jason Haley

Jason Haley — Wed, 19 Jul 2006 02:39:52 +0000

Interesting Finds: July 18, 2006

By: James Newton-King

James Newton-King — Tue, 18 Jul 2006 20:54:35 +0000

These are the rules I came up with when converting XML to JSON. You can see some in the example above.
-
* Elements remain unchanged.
* Attributes are prefixed with an @.
* Single child text nodes are a value directly against an element, otherwise they are accessed via #text.
* The XML declaration and processing instructions are prefixed with ?.
* Character data, comments, whitespace and significate whitespace nodes are accessed via #cdata-section, #comment, #whitespace and #significate-whitespace respectively.
* Multiple nodes with the same name at the same level are grouped together into an array.
* Empty elements are null.
-
Unfortunately you lose some ordering information when multiple nodes of the same name are grouped together but apart from that the transition back and forth (including namespace data) is pretty good.

By: Michael Schwarz

Michael Schwarz — Tue, 18 Jul 2006 14:52:03 +0000

There is already another one here:

http://weblogs.asp.net/mschwarz/archive/2006/06/19/XML-_2D003E00_-JSON-Serialization.aspx

By: Michael

Michael — Tue, 18 Jul 2006 14:50:14 +0000

There is another XML JSON converter:

http://weblogs.asp.net/mschwarz/archive/2006/06/19/XML-_2D003E00_-JSON-Serialization.aspx