W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2002

RE: xpath 2

From: Kay, Michael <Michael.Kay@softwareag.com>
Date: Thu, 25 Jul 2002 14:58:51 +0200
Message-ID: <DFF2AC9E3583D511A21F0008C7E621060453DA27@daemsg02.software-ag.de>
To: 'DPawson@rnib.org.uk' <DPawson@rnib.org.uk>, 'public-qt-comments@w3.org' <public-qt-comments@w3.org>

> The only example of distinct-values appears to be targetted at
> the query users.

I'm having difficulty understanding why you think this, Dave. Is it
because the result of the expression (in the XPath book, section 2.8)
has been shown with a particular serialization that might be more
familiar to XQuery users?

The problem of course is that XPath itself has no way of serializing a
sequence of elements, so the result of this expression can only be
described by inventing some notation. There might be a case for showing
examples of XPath as used in an XSLT context, but we've never done that
in the past (XPath 1.0 has no references to XSLT).

The example itself is actually rather artificial: in practice both
XQuery and XSLT users would construct a tree rather than a sequence
with the results, but tree construction is outside the scope of XPath
which is why the example has been done in this way. To be honest, I'm
not sure it belongs in this section of the document at all.

Michael Kay
>
>
> for $a in distinct-values(//author)
> return ($a,
>         for $b in //book[$b/author = $a]
>         return $b/title)
>
>
> As a minimum, please provide examples for *both* user groups,
> unless the query group have totally taken over the WD?
>
> regards
> DaveP
> AC RNIB.
>
>
>
> ************snip here**************
>
> -
>
> NOTICE: The information contained in this email and any
> attachments is
> confidential and may be legally privileged. If you are not the
> intended recipient you are hereby notified that you must not use,
> disclose, distribute, copy, print or rely on this email's content. If
> you are not the intended recipient, please notify the sender
> immediately and then delete the email and any attachments from your
> system.
>
> RNIB has made strenuous efforts to ensure that emails and any
> attachments generated by its staff are free from viruses. However, it
> cannot accept any responsibility for any viruses which are
> transmitted. We therefore recommend you scan all attachments.
>
> Please note that the statements and views expressed in this email
> and any attachments are those of the author and do not necessarily
> represent those of RNIB.
>
> RNIB Registered Charity Number: 226227
>
> Website: http://www.rnib.org.uk
>
Received on Thursday, 25 July 2002 09:02:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:56:43 UTC