Cart
|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: XSLT functions for JSON
 XML with some additional restrictions is no longer "XML" and JSON with restrictions is no longer "JSON" -- it is as simple as that. You are changing the initial problem and solving another -- and this is not bad -- but do take care to rename the problem to the new one so not to confuse anyone that you're trying to do the impossible. Absolutely agree, Dimitre! Couple of questions that might help guide the overall conversation in a productive direction, and therefore towards a renaming of the problem at hand, * Is it worth the effort to find ways of transforming JSON into another serialization format and/or back into JSON (e.g. filtering) using XSLT? * Is this possible with XSLT 1.0, or is this strictly an XSLT 2.0-type solution? * Is it even possible with XSLT 2.0? * If it isn't possible, what pieces of RFC 4627 would need to be avoided to make it possible? * If these pieces were avoided in any given JSON file, would JSON still be of value? * In other words, just like I can avoid using DTD declarations in XML without losing any inherent value or real world applicability, could the same be said about the pieces of JSON that would need to be avoided to ensure compatibility with XSLT 2.0? * Does JSON have to be serialized into XML /before/ it can be transformed into something else via XSLT 2.0? I'm sure there are other questions that might help make this conversation more productive. Thoughts? -- /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 
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! 
Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
