I imagine that the selection of for bindings can occasionally vary so much and might become so big that it would be needed to construct FLWOR expressions by more sophisticated data structures.
A for clause will take any sequence as the binding sequence,
How do you think about to take another look at the development challenges according to growing numbers of binding sequences and corresponding join conditions?
and the order of clauses in a FLOWR expression comes down to "ends with a return clause" for most practical purposes.
Thanks for your feedback.
Would you like to share any ideas for further extensions of the involved programming interfaces?
Regards, Markus