W3C home > Mailing lists > Public > www-ql@w3.org > April to June 2004

RE: top-level location-path context dependencies

From: Michael Rys <mrys@microsoft.com>
Date: Sat, 17 Apr 2004 22:50:05 -0700
Message-ID: <EB0A327048144442AFB15FCE18DC96C702A7D5D4@RED-MSG-31.redmond.corp.microsoft.com>
To: "Jason Hunter" <jhunter@acm.org>, "Howard Katz" <howardk@fatdog.com>
Cc: "Michael Kay" <mhk@mhk.me.uk>, <www-ql@w3.org>

This would not be backwards-compatible and have some interesting
side-effects. The easiest way is that you define your input document to
be always a document node which can contain more than one element node.
Then //foo would give you exactly what you would expect (if you start on
an element node, the result probably would not be what you expect if you
have a foo element on the top).

Also, you can set the context node to any node you want, as long as it
makes overall sense. 

Best regards
Michael

> -----Original Message-----
> From: www-ql-request@w3.org [mailto:www-ql-request@w3.org] On Behalf
Of
> Jason Hunter
> Sent: Saturday, April 17, 2004 3:30 PM
> To: Howard Katz
> Cc: Michael Kay; www-ql@w3.org
> Subject: Re: top-level location-path context dependencies
> 
> 
> Howard Katz wrote:
> > Any reason you couldn't set the context node to be *any* node within
a
> > particular document (altho it would likely be a very odd thing to
do)?
> 
> Why not allow it to be a *sequence* of nodes, is the better question.
> 
> It's much nicer if //foo would match all foo's within the default set
of
> documents.
> 
> -jh-
Received on Sunday, 18 April 2004 01:50:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 22 July 2006 00:10:19 GMT