On Sun, 18 May 2008 07:52:35 -0600, Jesper Tverskov <jesper(_at_)tverskov(_dot_)dk>
wrote:
property names in JSON could begin with characters not allowed as
first character in XML like "$" (used by Goggle) and "@", and "#" used
by article.
This list also includes numbers, so while a sequence of numbers e.g. (1,
2, 3) is valid as far as XSLT is concerned (and therefore a JSON array
could easily be converted to a valid sequence), it would be invalid to do
something like <array><1/><2/><3/></array>, though as per Robert's
suggestion, you could do something like
<array><i>1</i><i>2</i><i>3</i></array>. Of course, if the entire point
is to enabled to traverse a JSON document in the same way you would
traverse an XML document (a.k.a XPath), then, once again, it seems to me
the real problem to solve here is how do we go about traversing a JSON
document with XPath instead of how do we convert JSON to XML and back
again.
--
/M:D
M. David Peterson
Co-Founder & Chief Architect, 3rd&Urban, LLC
Email: m(_dot_)david(_at_)3rdandUrban(_dot_)com |
m(_dot_)david(_at_)amp(_dot_)fm
Mobile: (206) 999-0588
http://3rdandUrban.com | http://amp.fm |
http://www.oreillynet.com/pub/au/2354
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--