Jörn Kottmann wrote:
Does the community wish to have more discussion about this before I call for the vote?


I think there are still open questions which should be answered before a new vote.

I would like to know if we merge with the Cas Editor, does this makes sense for us ?
I think having an ability to edit a CAS (that could be switched off for safety reasons) would be a good addition to the CAS Viewer.

I think the (initial, target) users of these technologies may be different, and have different wants/needs. The CAS Editor I think was initially thought of as being used by people to manually annotate a CAS (for instance, preparing training data), and has various other elements added beyond simple CAS element updating, making it more a complete application.

The CAS Viewer is targeted I think at being a re-usable Eclipse view / plugin, to be embedded when it is useful, in other applications.

In my opinion this means technically that the Cas Viewer uses multiple views like the Cas Editor. Do we want this ? There is still a discussion about this in another thread.

Who will work on the code once it is in the sandbox ?
Generally, in Apache, anyone with an "itch to scratch" can work on anything. In this particular case, I would encourage both Tong and Jörn to work on these, with an eye toward their user communities, and find ways to share as much as seems useful; I would like to see both projects move forward. I think that user feedback will eventually be useful in guiding where more merging might go.

What are our plans for eclipse ui tooling ? How should it be ?
We did have earlier an intentional approach to providing both Eclipse-based tooling and (for the user population not using Eclipse) basic Swing-based (or even command-line-based) tooling. I don't think we've formulated an over-arching big plan for Apache UIMA open source Eclipse tooling. I think that is waiting for someone to step forward and lead such an effort.

I would love to see more work here, especially in areas around solving common NLP tasks, so that our community of users (including potential users now using other "platforms") would find it easier to create interesting UIMA-based applications or components.
-Marshall

Reply via email to