[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: <quote>XSL is NOT easy</quote>

Subject: Re: <quote>XSL is NOT easy</quote>
From: "Dimitre Novatchev" <dnovatchev@xxxxxxxxx>
Date: Tue, 26 Jun 2007 22:59:47 -0700
Re:  <quote>XSL is NOT easy</quote>
http://personplacething.info/service/json-to-xml/?debug=true&uri=http://api.local.yahoo.com/MapsService/V1/trafficData?appid=EricBlogDemo&amp;city=Seattle&amp;state=wa&amp;output=json


Wow... It's very nice. And efficient, too.

Thank you.



--
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play



On 6/26/07, M. David Peterson <m.david@xxxxxxxxxxxxx> wrote:
On Tue, 26 Jun 2007 09:51:14 -0600, Dimitre Novatchev
<dnovatchev@xxxxxxxxx> wrote:

> Recently I reported to this list how easy it was to parse and convert
> JSON documents into XML ones using a general LR(1) parsing framework
> written entirely in XSLT 2.0.

And it was even easier to take the FXSL JSON-to-XML conversion/parsing
utility that I was able to turn it into a Saxon on .NET-drive web
service[1,2] in about 5 minutes.

http://personplacething.info/service/json-to-xml/?debug=true&uri=http://api.local.yahoo.com/MapsService/V1/trafficData?appid=EricBlogDemo&amp;city=Seattle&amp;state=wa&amp;output=json

[1]
http://extf.googlecode.com/svn/trunk/WebApp/service/json-to-xml/service.op
[2]
http://extf.googlecode.com/svn/trunk/WebApp/transform/model/json-to-xml.xslt

Such is the power of using well designed languages, language processors,
and associated extension libraries.

NOTE: I still need to write a proper query-string parser to specify
whether a query-string variable belongs to the service end point or a URI
specfied as a query string variable, so at the moment the query string
variables are hard coded into this demo.  But that is a specific issue
associated with using URI's, HTTP GET and query string variables, not with
XSLT 2.0/Saxon on .NET/FXSL.  You could just as easily use an XML payload
via either GET or POST and avoid tbis specific issue all together.

--
/M:D

M. David Peterson
http://mdavid.name | http://www.oreillynet.com/pub/au/2354 |
http://dev.aol.com/blog/3155

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.