On 03.04.2015, at 22:51, Marshall Schor <[email protected]> wrote:

> It may be good to open a "Brainstorming" Jira, and attach the code you're
> thinking of donating, so that people could study it and have a more concrete
> idea about this.
> 
> If it eventually gets accepted, we would also need a Software Grant for this, 
> I
> think, due to the size. 

I was my impression in the past, that UIMA-Core has always valued compatibility 
very high, even to the point of adding switches to re-enabled buggy/undesired 
behavior in case somebody depended on it. Changing the implementation of the 
CAS is probably the most radical idea I've seen so far in this project. In 
principle, I very much like seeing UIMA to evolve, but I do wonder how such a 
radical change is imagined to be undertaken.

I'm aware that there are various levels of compatibility. My impression so far 
was that source-compatibility was typically not sufficient in the past. 

Are we going to slay the holy cow of compatibility now and if yes at which 
levels? 

Is there some willingness now to consider setting up a road-map for a UIMA-Core 
version 3?

What does such a change mean to the various sub-projects (DUCC, UIMA-AS, RUTA, 
uimaFIT)? 

Personally, I'd be curious to see how much of e.g. DKPro Core or WebAnno breaks 
with such a new implementation. I imagine quite a lot since I've become quite 
fond of binary serialization and internal API usage lately (in some cases I 
might be able to switch to official low-level CAS API...). Although I'm very 
much for evolution and adopting newer technologies, I'm afraid testing this 
(and potentially fixing stuff) will be quite time intensive. Given that in my 
context, most of the benefits are not very relevant so far, such testing would 
only make sense to me if it was part of a larger strategic change - and I think 
that a properly licensed contribution would be pretty much a pre-requisite to 
even look at it in detail.

Marshall, Eddie, and Nick do you have some vision of a strategic UIMA roadmap 
that you can share with us?

Cheers,

-- Richard

Reply via email to