Feature #3191
Mis à jour par Matthieu Decorde il y a environ 3 ans
It is quite common that annotation engines expose themself with a REST API and return conllu result (TXT based)
1) see if we can findout a generic way to call REST command (targeted (atgeted engines are UDPipe, Talisman, Hops, ...)
2) retrieve result
3) re-align result using the XmlID= scheme
see details at
https://groupes.renater.fr/wiki/txm-info/public/specs_annotation_nlp_api?s[]=rest
https://groupes.renater.fr/wiki/txm-info/public/annotation/tal_udpipe?s[]=rest
note : an alternative way is to :
* export a TXM corpus via the export as conllu command
* apply a tool out of TXM
* import the conllu annotations with the import conllu annotations command
see also what is done in the eltec svn branch to call UDpipe tokenisation, tagger and parser
1) see if we can findout a generic way to call REST command (targeted (atgeted engines are UDPipe, Talisman, Hops, ...)
2) retrieve result
3) re-align result using the XmlID= scheme
see details at
https://groupes.renater.fr/wiki/txm-info/public/specs_annotation_nlp_api?s[]=rest
https://groupes.renater.fr/wiki/txm-info/public/annotation/tal_udpipe?s[]=rest
note : an alternative way is to :
* export a TXM corpus via the export as conllu command
* apply a tool out of TXM
* import the conllu annotations with the import conllu annotations command
see also what is done in the eltec svn branch to call UDpipe tokenisation, tagger and parser