On Sun, 18 May 2008 08:54:01 -0600, Jesper Tverskov <jesper@xxxxxxxxxxx>
wrote:
Sounds nice, but I don't know what it means.
Simple enough: If the value of 'bar' is 'baz', then /foo/bar applied to
both an XML and JSON representation of any given data structure would
result in 'baz'.
Also: Traditional
functions could come in handy in all the cases where transformation
works right away.
Sure. I'm not suggesting don't create the functions. Just that
regardless of the functions, there will always be cases which there is no
possible way to convert from one format to another. As such, if the
desired result it to work with a data set regardless of its serialization,
why not attempt to create a standardized subset of JSON in which, when
adhered to, ensures that the same XPath applied to it will render to same
generalized result as it would when applied to its XML "equivalent".
Of course, just such an effort might prove to be impossible. But it's
worth thinking about none-the-less.
--
/M:D
M. David Peterson
Co-Founder & Chief Architect, 3rd&Urban, LLC
Email: m.david@xxxxxxxxxxxxxxx | m.david@xxxxxx
Mobile: (206) 999-0588
http://3rdandUrban.com | http://amp.fm |
http://www.oreillynet.com/pub/au/2354