I think it would be very valuable to collect and write down a couple of user stories to see where people have problems using UIMA, and maybe also stories about how they would like to use it. We can also use these stories to make design decision for v3.
If people are just holding it wrong there is probably no reason to even make v3. Jörn On Thu, Jul 23, 2015 at 3:33 PM, Marshall Schor <[email protected]> wrote: > > > On 7/23/2015 8:55 AM, Richard Eckart de Castilho wrote: > > On 23.07.2015, at 14:43, Joern Kottmann <[email protected]> wrote: > > > >> One thing which must have been overlooked when UIMA was built is that > >> people (like me) have to write code which wants to interact with the CAS > >> but can't be an AE. In UIMA the CAS (either in memory, or serialized) > >> is difficult to > >> be used without implementing an AE. > > I'm not sure why you feel like that. E.g. in WebAnno (an annotation > editor > > that uses the CAS as its internal data model), create operate with the > CAS > > basically without any AEs. All editing operations are done directly on > the > > CAS which is loaded/saved directly using the UIMA API calls for binary > > serialization. > > One possible reason why people feel this way might be that we're missing > some > entertaining and compelling stories in multiple kinds of media that > explain how > to do the > kinds of things, easily, that people say are hard. For example, there's > little > written on the > new JSON serialization that gives lots of examples, including the > super-simple > varieties > that are possible (i.e. omitting the context info). Volunteers > wanted/needed to > write this! :-) > > -Marshall > > > > Basically, we are using the same API that we would be using in an AE, > but without > > the AE/pipelining stuff. It doesn't get any more difficult without the > AE - in fact > > some things become easier without AEs, readers, and consumers. > > > > I'm sure you must have something similar in the CAS Editor plugin in > Eclipse, no? > > > > -- Richard > >
