- From: David Carlisle <davidc@nag.co.uk>
- Date: Tue, 5 Feb 2002 16:22:57 GMT
- To: ALEX@SIRIUS.sirius-software.com
- CC: www-xpath-comments@w3.org, zarella@hmmci.com
> Also, maybe my internal parser isn't working right no, your parser is correct, I just can't type. Delete the "not" from my paragraph and reparse, sorry. > What do you mean "to key off the local name"? I mean that if you are doing *:set then you are querying all set elements in any namespace but in a namespace view of the world, such elements are no more related than, say, all elements beginning with "A". You can query either of those things already *[starts-with(name(),'A')] and *[local-name()='set'] There isn't an obvious reason why one needs to offer a *:set shortcut for the second query. > Anyway, I think it's important to keep in mind that XSLT doesn't "own" XPath > and that there are uses for XPath outside of XSLT -- MSXML and XQuery for > example. > ... > Just as a general comment I find the XSLT centeredness of the XPath discussion > a bit distressing in that it seems that the creeping procedurality and complexity > of XPath is largely being driven by XSLT Actually I'd say the opposite, the extra complexity has come about from incorporating large chunks of Xquery, and much of that isn't really desirable in XSLT, I'd much rather have seen sequence construction in XSLT rather than XPath for example. David _____________________________________________________________________ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Scanning Service. For further information visit http://www.star.net.uk/stats.asp or alternatively call Star Internet for details on the Virus Scanning Service.
Received on Tuesday, 5 February 2002 11:23:49 UTC