On Fri, Dec 30, 2022 at 5:56 AM Richard Eckart de Castilho <r...@apache.org> wrote:
> On 29. Dec 2022, at 13:38, Richard Eckart de Castilho <r...@apache.org> > wrote: > > > > == Component concept > > > > The Python annotation with component metadata on the analysis engine > class looks interesting. I wonder if you need the indexes though. Can you > not work simply with the built-in annotation index? > > If pipelines in Python be a thing, my intuition is that it would be > sensible to implement this as a dedicated module covering a component > lifecycle API. > I'm sorry, I don't understand this bit. > In particular, I think this module should be separate from another module > implementing the CAS data structure. Consider for example using the same > component lifecycle API but with different implementations of CAS (e.g. > UIMA-CPP CAS or Cassis) - of course that would suggest that UIMA-CPP and > Cassis should share at least a common subset of their API. > My thoughts were that Cassis could co-exist with a UIMA-CPP backed Python module and make use of it (for fast serialization, for instance) if available. That type of stuff is easy to do in Python (check whether an import is available and use it). But my goals for a UIMA-CPP backed Python module are much broader than your stated goals for Cassis. > Does that make sense? > I feel I'm missing something. I thought the question is whether to keep UIMA-CPP and whether somebody will want to maintain it. I brought up the Python discussion to justify keeping UIMA-CPP and I'm making good progress on bringing the code up-to-date (will send that in a separate email). P
