Dear all,
for the "XQuery Implementation Paradigms" workshop at Dagstuhl (Nov. 19-22) (cf., http://www.dagstuhl.de/programm/kalender/semhp/?semnr=06472), we're looking for XQuery 'Hard Nuts to Crack' (see below for details).
Hence, if you have encountered any such 'Hard Nuts' --- with MonetDB/XQuery or elsewhere ---, please let us now "ASAP", at least before Nov 19.
Please accompany our Hard Nuts with a brief statement what makes the Nut hard.
Thank you very much in advance!
Stefan
========
*** XQuery 'Hard Nuts to Crack'
Most of us have stumbled across a certain XQuery expression or construct that performs (un)expectedly bad or exposes a subtlety of the language specification. We want to employ such 'XQuery Hard Nuts to Crack' during the seminar to identify interesting, yet dark, corners of the language and its implementation.
We would like to ask you to contribute your tough queries to the seminar.
To clarify, an XQuery Hard Nut is
- a specific query expression that is supposedly tricky or hard to evaluate (maybe when applied to a specific XML instance), or - a specific XQuery or XQuery Update construct (or combination of constructs) that is hard to support in general.
A good XQuery Hard Nut is compact, precise, and to the point.
We'll try to have the Hard Nuts cracked by the participants of the "XQuery Implementation Paradigms" workshop (resp. their XQuery systems), and let you know about the results.
We imagine that here and there some Hard Nut aspect might also make a valuable contribution for a forthcoming definition of a new XQuery benchmark that we plan to tackle during the workshop.
========