Full Text Grammar ambiguous?

[Christian Grün]

Martin,

thanks for the observation! This problem was recently posted in the
W3C's bugzilla system:

  http://www.w3.org/Bugs/Public/show_bug.cgi?id=7247

..and is currently discussed by the XQFT task force. A decision how to
solve to this issue will be posted at the same place in near future.

Hope this helps,
Christian

___________________________

Christian Gruen
Universitaet Konstanz
Department of Computer & Information Science
D-78457 Konstanz, Germany
Tel: +49 (0)7531/88-4449, Fax: +49 (0)7531/88-3577
http://www.inf.uni-konstanz.de/~gruen



On Sat, Sep 12, 2009 at 3:27 PM, Martin Probst <http://x-query.com/mailman/listinfo/talk> wrote:
> Hi all,
>
> maybe I'm just a bit late to the party, but is it possible that the
> full text grammar from XQFT makes the XQuery grammar ambiguous?
>
> Consider the expression:
>  element ftcontains { 'x' }
>
> As far as I can see, it's impossible to tell whether this should be
> parsed as an element constructor for the element named "ftcontains"
> with content 'x', or as a full text matching operation on a child axis
> selection for 'element' against the words 'x'.
>
> Is this a known issue? If yes, how should this be resolved?
>
> Martin
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk