[Bug 2523] xqx: pathExpr and stepExpr

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2523





------- Additional Comments From davidc@nag.co.uk  2005-12-17 23:22 -------
(In reply to comment #1)
> Thanks very much for your comment.  As it happens, this same error was also
> reported to me through a private communication from somebody else. 
> 
> The solution that I devised would result in an XML Schema element definition
> that looks like the following.  The relevant change is to make the element
> xpathAxis optional and remove the now-redundant elements nameText and
> Wildcard. 

It's very inconsistent to have the axis specifier optional in this position.
omitting the axis here is the abbreviated xpath syntax for child:: and every
other part of the abbreviated xpath syntax (@, and //) is not reflected in
Xqueryx, but the expanded form is used instead. Why not here?


In your later reply you made two comments that I don't understand at all, sorry.

> e.g., child::, equivalent to /). 

whether the steps are separated by / or // has no effect on the axis specifier:
in both cases it is either given explictly or defaults to child::

> And starting a relativePathExpr with an xpathAxis was just a
> bit strange (to me, at least)!

Every relativepathexpr surely has to begin with an axis specifier (defaulted to
child:: if not explict) it is the axis that gives the "relation" of the relative
path. (well filter expressions are technachily also relative xpath but they 
are catered for in the xqueryx stepExpr with the filterexpr clause which doesn't
require an axis specifier,which is in agreement with the xquery grammar, there
is no need to have any special argExpr clause at the level of pathexpr

Also it wasn't clear to me whether you meant that you were agreeing to dropping
the argExpr clause from pathExpr.

David (slightly confused:-)

Received on Saturday, 17 December 2005 23:22:20 UTC