Closed Tpt closed 8 years ago
Good point, I will have a look in the next few days.
I just started to have a look, sorry for the delay. This will be a more tedious work than I thought, since there has been changes in the library output format, and new grammatical dependencies are used (which obviously break our code...).
An example of the changes that occurred with the new version of CoreNLP.
This parse tree is obtained with the CoreNLP from 29/01/2015 (the one currently used in production) :
This parse tree is obtained with the CoreNLP from 09/12/2015 (the one we would like to use) :
These particular changes should not be a big issue.
Another example which would be trickier to solve.
Parse tree obtained with CoreNLP from 29/01/2015.
Parse tree obtained with CoreNLP from 09/12/2015.
Yet another example.
Parse tree obtained with CoreNLP from 29/01/2015.
Parse tree obtained with CoreNLP from 09/12/2015.
CoreNLP has now an HTTP API. it would be nice to use it in order to have a more modular architecture and avoid the dependence on a CoreNLP Python wrapper.
API doc: https://stanfordnlp.github.io/CoreNLP/corenlp-server.html