RE: top-level location-path context dependencies

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-