norman.walsh.name: Comments on /2004/05/19/xsltxqueryhttp://norman.walsh.name/2004/05/19/xsltxquery/comments.atom2012-02-13T08:36:11.404224ZComment 1 on /2004/05/19/xsltxqueryhttp://norman.walsh.name/2010/09/25/oauth#comment00012004-05-19T14:54:38Z2004-05-19T14:54:38ZMichael Rys

Hi Norm

My colleagues are aware that XPath 2.0 and XQuery 1.0 are very closely related. The point about XPath 2.0 is that it lacks certain capabilities that need to be provided by a host environment. Since XQuery provides XPath 2.0 plus more, there is currently no reason to implement XPath 2.0.

And I agree with you on XSLT 1.0 being the biggest competitor to XSLT 2.0 (and not XQuery 1.0). That's what my post is basically saying at the moment...

Comment 2 on /2004/05/19/xsltxqueryhttp://norman.walsh.name/2010/09/25/oauth#comment00022005-09-01T09:21:54Z2005-09-01T09:21:54ZWaelda39a3ee5e6b4b0d3255bfef95601890afd80709

How can I use XPATH 2.0   string functions from within an XSL file, and then apply this XSL file to a well formed XML document to see the result in IE.

When calling Most of XPATH 2.0 string functions from an XSL file, IE gives me an error saying that, for example, replace() is unknown function .. .

Thanks

Wael

Comment 3 on /2004/05/19/xsltxqueryhttp://norman.walsh.name/2010/09/25/oauth#comment00032005-09-07T16:31:37Z2005-09-07T16:31:37Zmamundda39a3ee5e6b4b0d3255bfef95601890afd80709

good points. i will say that, as someone committed to XSLT/XPath and to the .NET runtime, i ignored most of the blather about XQuery. I also was annoyed when MSFT made the commitment to XQuery over XSLT 2.0. IHMO, XQuery is really 'back-sliding' on the whole extensible model. it seems that MSFT's embrace of XQuery has more to do with thier long term strategy for C# (google c-omega for more on this) than any agruments about the merit or future of XSLT/XPath.

for now, i will be looking for a .NET plug-in for XSLT 2.0/Xpath 2.0 and will have to wait for MSFT to bring thier XML support up to speed again.