<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6001.18203" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=746513710-27032009><FONT face=Arial
color=#0000ff size=2> > </FONT></SPAN>Because a recommendation
needs a long time to be published, as soon as I will write my own XRX
application, I will add to my XML script engine "tXs" (something in between
XProc and the XSLT machine shown at XML Prague) my own XML notation for XQuery.
I will publish it then...<BR><SPAN class=746513710-27032009><FONT face=Arial
color=#0000ff size=2> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=746513710-27032009><FONT face=Arial
color=#0000ff size=2>Perhaps this should be a project for EXQuery. I suspect
your chances of getting everyone to accept your design are much better if you
have a forum for consultation rather than trying to present it as a fait
accompli - even if you do a magnificent job of the design, other people might
have different use cases.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=746513710-27032009></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=746513710-27032009><FONT face=Arial
color=#0000ff size=2>I think there are three possible styles of XML
representation:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=746513710-27032009></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=746513710-27032009><FONT face=Arial
color=#0000ff size=2>(a) one that looks as much as possible like current
human-readable XQuery. This is largely a question of changing the rules for
escaping of special characters such as the "<" and "<<" operators, and
preventing people writing non-XML things like <e att="{<e
att="{"3"}"/>}"/> which are currently legal but rather
useless.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=746513710-27032009></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=746513710-27032009><FONT face=Arial
color=#0000ff size=2>(b) one that uses a bit more XML markup, e.g. giving
an alternative XML-based syntax for prolog declarations like "import schema" and
for function signatures.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=746513710-27032009></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=746513710-27032009><FONT face=Arial
color=#0000ff size=2>(c) the full (non-human-readable) fine-grained XQueryX
syntax.</FONT></SPAN></DIV>
<DIV><SPAN class=746513710-27032009><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=746513710-27032009><FONT face=Arial color=#0000ff size=2>Since
we already have (c), I think the main requirement is probably for something like
(a) (though (b) would give benefits if people want a compromise between
human-readability and software-readability).</FONT></SPAN></DIV>
<DIV><SPAN class=746513710-27032009><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=746513710-27032009><FONT face=Arial color=#0000ff size=2>One of
the challenges is in defining how the in-scope namespaces from the containing
XML document should affect the static context of the query.</FONT></SPAN></DIV>
<DIV><SPAN class=746513710-27032009><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=746513710-27032009><FONT face=Arial color=#0000ff
size=2>Michael Kay</FONT></SPAN></DIV>
<DIV><SPAN class=746513710-27032009><FONT face=Arial color=#0000ff size=2><A
href="http://www.saxonica.com/">http://www.saxonica.com/</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><BR></DIV></BODY></HTML>