- From: Fabien Gandon <Fabien.Gandon@sophia.inria.fr>
- Date: Thu, 07 Aug 2008 09:29:10 +0200
- To: Ian Hickson <ian@hixie.ch>
- CC: Danny Ayers <danny.ayers@gmail.com>, public-grddl-comments@w3.org
Received on Thursday, 7 August 2008 07:29:54 UTC
Ian Hickson a écrit : > On Wed, 6 Aug 2008, Danny Ayers wrote: > >> One possible obstacle might be how to specify the purpose of the linked >> transformation. >> > > Isn't that what the keyword "transformation" does? It implies that the > resource is a GRDDL XSLT program, no? > Not necessarily in XSLT: "(...) each GRDDL transformation specifies a transformation property, a function from XPath document nodes to RDF graphs. This function need not be total; (...) Developers of transformations should make available representations in widely-supported formats. XSLT version 1 is the format most widely supported by GRDDL-aware agents as of this writing, though though XSLT2 deployment is increasing. While technically Javascript, C, or virtually any other programming language may be used to express transformations for GRDDL, XSLT is specifically designed to express XML to XML transformations and has some good safety characteristics; XQuery has similar characteristics to XSLT, though use of XQuery in GRDDL implementation is less widely deployed at the time of this writing. (...) Non-XSLT transforms may indicate the RDF graph in some other, unspecified, fashion." from section 6 "GRDDL Transformations" http://www.w3.org/TR/grddl/#txforms in Gleaning Resource Descriptions from Dialects of Languages (GRDDL) W3C Recommendation 11 September 2007 -- Fabien - http://ns.inria.fr/fabien.gandon/
Received on Thursday, 7 August 2008 07:29:54 UTC