This has been brought up in various proposal discussions (e.g. https://github.com/expath/xpath-ng/pull/2#issuecomment-436232134) regarding compatibility of the proposals with the current XPath and XQuery grammars, and the various extensions (Full Text, Updating, Scripting).
At a minimum, this should provide an xpath and an xquery ebnf grammar file, and tools to verify that (as a separate project).
Should this also include full text (xpath and xquery variants), updating (xquery), and scripting (xquery) grammars?
Some options:
Reuse the tools used by the W3C WG to verify the grammar.
Use the parser that is used by the xquerydoc tool that generates an xquery parser in xquery from an ebnf.
Use some other parser generation tools (Java based?).
This has been brought up in various proposal discussions (e.g. https://github.com/expath/xpath-ng/pull/2#issuecomment-436232134) regarding compatibility of the proposals with the current XPath and XQuery grammars, and the various extensions (Full Text, Updating, Scripting).
At a minimum, this should provide an xpath and an xquery ebnf grammar file, and tools to verify that (as a separate project).
Should this also include full text (xpath and xquery variants), updating (xquery), and scripting (xquery) grammars?
Some options: