W3C home > Mailing lists > Public > www-xml-linking-comments@w3.org > October to December 2000

Re: XPointer question - selecting locations from a location-set

From: Michael Dyck <MichaelDyck@home.com>
Date: Wed, 22 Nov 2000 21:52:40 -0800
Message-ID: <3A1CB0A8.FA4B2DF9@home.com>
To: Daniel.Veillard@w3.org
CC: www-xml-linking-comments@w3.org
Daniel Veillard wrote:
> 
> On Wed, Nov 22, 2000 at 01:23:09AM -0800, Michael Dyck wrote:
> > 
> > Jiri Jirat wrote:
> > > IMPORTANT: here, in this example, the location-set returned by
> > > "string-range(//*,'another')" consists just of ONE location.
> >
> > Actually, this raises an interesting point. The path-expression //*
> > selects all element nodes in the document tree, and in fact *two* of them
> > have "another" in their string-value: the second <BBB> element obviously,
> > but also the <AAA> element, whose string value is the concatenation of the
> > string-values of all text nodes in the document. So the string-range()
> > call finds two locations in //* that have a match for "another". But does
> > it return two range locations, or just one?  I'm pretty sure the answer is
> > one, but it's not immediately obvious from the XPointer spec.
> 
> right, 5.1 states:
> 
> "Thus, XPointer also defines location-set as a generalization of
>  XPath's node-set"
> 
> I think this should be added there.

Sorry, I don't understand how that would clarify things. (Actually, I'm
not precisely sure of what you're suggesting: what do you mean by "this"
and "there"?)

-Michael Dyck
Received on Thursday, 23 November 2000 00:53:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:39:41 GMT