[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XPath 2.0 - how much of XQuery should it include?

• To: michael.h.kay@n...
• Subject: Re: XPath 2.0 - how much of XQuery should it include?
• From: David Carlisle <davidc@n...>
• Date: Fri, 10 May 2002 16:16:29 +0100
• Cc: xml-dev@l...
• In-reply-to: <000701c1f834$2f6b6600$6501a8c0@pcukmka>(michael.h.kay@n...)
• References: <000701c1f834$2f6b6600$6501a8c0@pcukmka>

Mike,
I accept that it has to be an arbitrary choice but

 Drawing the line here
 puts sequence construction firmly on the XPath side of the boundary,
 because a sequence is a value.

But nodes are also values, so node construction also sits firmly
in XPath, but basically that says to junk XSLT and to use Xquery.

Looking at Xpath2 that is the distinct impression that is given, that
XSLT is being marginalised. Maybe that wasn't the intended impression
but it is no less real for that.

Sequences are the Xpath2 replacement for node sets, so if it makes sense
for XSLT to construct node sets it should make sense for it to construct
sequences.

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.

• Follow-Ups:
  • RE: XPath 2.0 - how much of XQuery should it include?
    • From: "Michael Kay" <michael.h.kay@n...>

• References:
  • RE: XPath 2.0 - how much of XQuery should it include?
    • From: "Michael Kay" <michael.h.kay@n...>

• Prev by Date: Stopping the SAX parser
• Next by Date: Re: The vision for XPath 2.0
• Previous by thread: RE: XPath 2.0 - how much of XQuery should it include?
• Next by thread: RE: XPath 2.0 - how much of XQuery should it include?
• Index(es):
  • Date
  • Thread