Dirk Roorda

When I think of it, it should definitely be possible, but there will be an addtional restriction: * the stuff between the parent and the quantifier may not contain names...

Internally a template is translated into a set of query nodes and query edges, without specific order. That query graph gets executed. At the point of execution there is no...

I think the way forward is to let quantifiers quantify not a single parent but a complete subtemplate. The subtemplate must be marked in case if it is more than...

``` ---t1 w1:word < w2:word --- % other parts of the template t1 /without/ w1 < word pdp=prep < w2 /-/ ```

So: named subtemplates. If the quantifier follows the subtemplate immediately, no naming is needed.

But wait, the subtemplates might become nested: if they contain quantifiers themselves. So we need a slightly different bracketing syntax: ``` {t1 w1:word < w2:word } % other parts of...

But in this case we may also say ``` { w1:word < w2:word } /without/ w1 < word pdp=prep < w2 /-/ ```

`{` and `}` should occur on a line on their own, the position in the line does not matter.

MQL makes you think about your data as a tree. TF search is more conducive to graph thinking, so I am a bit wary about blocks. Named templates might be...

``` /all/ w1:word < w2:word /without/ w1 < word pdp=prep < w2 /-/ ```