Thilo Goetz wrote:
So here's what I would do:
- No view API in UIMA 2.x. Possibly change the view/sofa related APIs
in a manner indicated above (CAS getView(String viewName) -> void
setView(String viewName) etc). I would find that much more intuitive,
but I'm not hopeful that other people on this list will.
- Start discussing UIMA 3 now. Take a clean slate approach, consider
how we want to handle indexing in the future. Have a couple of beta
releases to get feedback from users.
- Support both UIMA 2 and 3 in parallel, for as long as necessary.
Consider interoperability, possibly in the same JVM.
I really think that the CAS/view redesign proposal as it currently
stands will make things even worse, and that it should be reconsidered.
Till now I only read the posts to the CAS/CasView discussion and tried
to understand the details, sometimes without success :-) I think this
also depends on may current knowledge and I have to do my homeworks to
contribute to that discussion.
My current point of view, as far as I understand the discussion is that
we do not really have a consent on the CAS/CasView architecture. So I
like the suggestions to start this discussion again for UIMA 3 and do
things step by step. This would help me and maybe others (if we find
some contributors after the release) to contribute to the discussion.
This suggestions seems also more reasonably when thinking about the
first UIMA release with code freeze in about two weeks to get out a
stable version of UIMA.
Just my point of view.
-- Michael
