uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eddie Epstein <eaepst...@gmail.com>
Subject Re: Requirements / Wish List for CAS Store? (Add on)
Date Wed, 09 Jan 2013 19:24:07 GMT
The Xmi serializer has the ability to maintain xmi:id's. This feature
is used by uima-as services. It works by storing a map of IDs when an
incoming XmiCas is deserialized and using that map when serializing
back the modified Cas. It should be straightforward to utilize this
feature with an application interfacing a Uima pipeline to a CAS


On Wed, Jan 9, 2013 at 9:32 AM, Richard Eckart de Castilho
<eckart@ukp.informatik.tu-darmstadt.de> wrote:
> As an add-on to my last post:
> In one project we rely on stable annotation IDs in the CAS. We
> currently use the CAS address for that, which limits us to the
> binary CAS serialization right now as addresses get re-written
> when using XMI, in particular after an annotation has been
> deleted.
> It would be nice if it was possible to reliably address individual
> annotations in the storage via some form of ID, possibly a
> composite ID made up from a CAS ID and an annotation ID within the
> CAS.
> Annotation IDs should remain stable after the annotation has been
> added. They should not change if more annotations are added or
> if annotations are removed.
> I am not sure how such a requirement could be carried over to the
> in-memory CAS structure. Asking for stable CAS addresses certainly
> is not sensible.
> Cheers,
> -- Richard
> --
> -------------------------------------------------------------------
> Richard Eckart de Castilho
> Technical Lead
> Ubiquitous Knowledge Processing Lab (UKP-TUD)
> FB 20 Computer Science Department
> Technische Universit├Ąt Darmstadt
> Hochschulstr. 10, D-64289 Darmstadt, Germany
> phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117
> eckart@ukp.informatik.tu-darmstadt.de
> www.ukp.tu-darmstadt.de
> Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de
> -------------------------------------------------------------------

View raw message