Hi Pablo, Good you are confused about my comments. I'll try to explain my reasoning.
> Much more work, but possibly much more user friendly, would be to add an > > annotator controller mechanism with RPC support around cassis, and add > > delta-CAS support to cassis serialization. > > > > I found this part really confusing, I don't understand why you are bringing > dkpro-cassis into the discussion. I have in mind that python is a popular language for analytic processing, or for being a front end for such processing. Perhaps these analytics could benefit from using a CAS for all the things a CAS is good for, including interchange with other UIMA analytics. Python programmers have long complained about the non-Pythonic nature of the swig-based interface to a CAS, and my assumption is that the cassis interface would be preferred. > I'm also thinking node.js and PHP are suitable targets, both > languages I'm involved in NLP efforts [1][2]). > As far as I understand, PHP and node.js are not used for deep analytics, but they are popular for client interfaces and traditional backend services. It would be awkward for PHP clients to use a CAS interface. Makes more sense for a PHP client to have a much simpler, likely custom interface to a CAS-based analytic, perhaps using a PHP to CAS translator on the analysis service, and for that the SWIG interface to uima-cpp makes sense. I'll be happy to learn how wrong I am :) Eddie
