aeb-dev / netSchematron

1 stars 0 forks source link

A more advanced parser should be implemented #3

Open aeb-dev opened 6 years ago

aeb-dev commented 6 years ago

The current parser mechanism is not reliable, a more generic and advanced a parse technique should be used based on the grammar in the following link: https://www.w3.org/TR/xpath-31/#id-grammar

aeb-dev commented 6 years ago

Since we have the grammar, I think the best option is to use a lexical parser. I have found similar projects but none of them uses a lexical parser.

aeb-dev commented 6 years ago

here is a list of available tools for such task: https://github.com/maxtoroq/dotnet-xml#xpath-xquery-and-xslt

https://github.com/StefH/XPath2.Net or https://github.com/semyonc/xpath2 (I think one is fork of the other) is the most suitable example, but it lacks the lexical analyzer as our project does.

aeb-dev commented 5 years ago

https://github.com/b3b00/csly this project seems good enough for our approach