Philippe Poulard wrote:
[ Au fait, salut Philippe ;-) ]
> >>file('file:///c:/xslts_1_0_0/TestInputs')//*[@extension='xsl']
> >>or whatever à la XPath ?
> > Saxon's syntax is an "à la XPath" syntax, isn't it?
> 'file:///c:/xslts_1_0_0/TestInputs?select=*.xsl;recurse=yes'
> this part is not, comparing to what I proposed
Mmh. Saxon uses a standard XPath function that takes a URI as
parameter. I don't see what is not "à la XPath". You use an unknown
function. They smell equally XPath IMHO.
BTW, how do you specify to recurse or not? And to validate or not?
And how do you get the actual content of the files? Are they
encapsulated directly in the result of file() (I hope they are not), or
do you need a second function (something like open-file())?
But your approach is interesting, IMHO, with optional arguments to
specify switches, and assuming it returns only file infos, not actual
content.
Maybe an idea to start an EXPath library, defining extension
functions to be implemented by various XPath, XQuery and/or XSLT
engines?
Regards,
--drkm
p4.vert.ukl.yahoo.com uncompressed/chunked Mon Aug 28 14:13:40 GMT 2006
___________________________________________________________________________
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet !
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences.
http://fr.answers.yahoo.com
