Comments on: I don’t get it: XSLT, RDF, XQuery, XLinq http://parand.com/say/index.php/2005/12/23/i-dont-get-it-xslt-rdf-xquery/ Parand Tony Darugar: A Cruel and Petty Dictator Tue, 17 Jan 2012 23:10:42 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: Daniel Lemire http://parand.com/say/index.php/2005/12/23/i-dont-get-it-xslt-rdf-xquery/comment-page-1/#comment-2203 Daniel Lemire Tue, 27 Dec 2005 06:05:34 +0000 http://www.parand.com/say/index.php/2005/12/23/i-dont-get-it-xslt-rdf-xquery/#comment-2203 OH! And here's a blog post answering your post: http://www.daniel-lemire.com/blog/archives/2005/12/26/standard-deviations-i-don%e2%80%99t-get-it-xslt-rdf-xquery-xlinq/ OH! And here’s a blog post answering your post:

http://www.daniel-lemire.com/blog/archives/2005/12/26/standard-deviations-i-don%e2%80%99t-get-it-xslt-rdf-xquery-xlinq/

]]> By: Daniel Lemire http://parand.com/say/index.php/2005/12/23/i-dont-get-it-xslt-rdf-xquery/comment-page-1/#comment-2196 Daniel Lemire Tue, 27 Dec 2005 01:35:45 +0000 http://www.parand.com/say/index.php/2005/12/23/i-dont-get-it-xslt-rdf-xquery/#comment-2196 Why XSLT? XSLT processors should be fast and optimized for this very task. The language should be complete and optimized for this task. But these reasons are secondary, the main reason to use XSLT is that it is the standard way to do so. Instead of having to learn how to transform XML using various APIs, I can just learn XSLT and XSLT should be supported whereever I go. Note that wherever Firefox lives, there is good XSLT 1.0 processor! RDF: again, this is the standard way to express knowledge on the web. It clearly hasn't take up though, except for things like Dublin Core or Creative Commons. But Dublin Core and Creative Commons don't need RDF. And RDF doesn't need XML. And maybe we don't need RDF nor XML. But people use these things. But I don't know much about software supported RDF. I don't get XQuery myself. The main argument for XQuery seems to be that since XSLT is so hard, and the task for extracting data from XML is so common, we are going to use an SQL-like language. Seems to be this will soon be a solution in search of a problem. We will see. Until a solution is widespread enough, you should be careful. XLinq: I also don't see what is to be excited about. Worse: these things are not "standard" ways. They won't be there wherever you go. Why XSLT? XSLT processors should be fast and optimized for this very task. The language should be complete and optimized for this task. But these reasons are secondary, the main reason to use XSLT is that it is the standard way to do so. Instead of having to learn how to transform XML using various APIs, I can just learn XSLT and XSLT should be supported whereever I go. Note that wherever Firefox lives, there is good XSLT 1.0 processor!

RDF: again, this is the standard way to express knowledge on the web. It clearly hasn’t take up though, except for things like Dublin Core or Creative Commons. But Dublin Core and Creative Commons don’t need RDF. And RDF doesn’t need XML. And maybe we don’t need RDF nor XML. But people use these things. But I don’t know much about software supported RDF.

I don’t get XQuery myself. The main argument for XQuery seems to be that since XSLT is so hard, and the task for extracting data from XML is so common, we are going to use an SQL-like language. Seems to be this will soon be a solution in search of a problem. We will see. Until a solution is widespread enough, you should be careful.

XLinq: I also don’t see what is to be excited about. Worse: these things are not “standard” ways. They won’t be there wherever you go.

]]>