...
(Unlikely) Making the element of the "stream" be a new CAS - replacement for CAS Multipliers. Seems like the wrong granularity... Maybe best to let Java evolve this for a few more releases.
Additional capabilities
Integration with popular no-sql
stores for results and downstream processing
Improvements in debugging
Ability to specify "capture" of intermediate CAS results at specific points in the pipeline, integrated with JMX (Some of this has already been done as part of UIMA-AS, but should be put into the core)
CAS differencing
Custom UIMA JMX console
Other changes
Integrate key ideas from uimaFIT
...
Judicious substitution of other packages for hand-built code
There's a plus and a minus for this - plus: we get better tested, better function (perhaps), better performance for some typical capabilities (e.g., parsing XML to/from Java Objects). Minus - it make the code depend on these other packages. Also, if it's working fine now, there's little motivation to invest in changing it.
Some areas to consider:
XML parsing and writing for descriptors - use JAXB or Jackson (already used for JSON support)