RE: [XQueryX] The need of PathExpr as in simpleType

These are excellent questions, and I don't think it's possible to give you a satisfactory answer: you're right that this is a requirement worth looking at, and as far as I'm aware no-one is currently looking at it.

One point, however: path expressions in XQuery, and hence in XQueryX, are not a subset of XPath path expressions. For example, a/b[let $x:=@p return d[@q=$x]] is a valid path expression in XQuery but not in XPath.

Michael Kay
http://www.saxonica.com/

> -----Original Message-----
> From: public-qt-comments-request@w3.org 
> [mailto:public-qt-comments-request@w3.org] On Behalf Of Frank 
> Yung-Fong Tang
> Sent: 14 March 2005 21:38
> To: public-qt-comments@w3.org
> Subject: [XQueryX] The need of PathExpr as in simpleType
> 
> 
> 1. Currently, PathExpr is defined as a  complexType in
> http://www.w3.org/TR/xqueryx/  . Since both XML Schema (as in  key,
> keyref and uniques) and XSLT (as in pattern) also use XPath in
> attribute, it will be nice if XQuery WG can ALSO define a way to
> experss PathExpr as a simple type, either in XQueryX, or in other
> document, or both.
> 
> 2. In the XQueryX efforts, do we really need to experss the XQuery in
> a way that it tokenize every details, or should we consider a level in
> XQueryX to keep the PathExpr as a whole ?
> 
> I also think XML Schema should support a primitve type to hold XPath
> so XPath can be used by more W3C technology in the future with less
> interoperability issues. See my other posting.
> 
> -- 
> Frank Yung-Fong Tang
> ???
> Šýštém Årçhîtéçt
> 
>

Received on Tuesday, 15 March 2005 11:23:11 UTC