On 12/11/06, Thilo Goetz <[EMAIL PROTECTED]> wrote:
The heap?  How does that come into the picture?


I just meant that the CAS is where the actual data (the FeatureStructures) live.

What about the type system?  Is that accessible from the CasView, or
just from the CAS?


Logically, the TypeSystem belongs to the CAS (all views share the same
type system).  But the CasView could certainly have a convenience
method for accessing it as well.


So the we have a meta-CAS that holds the type system info and all the
concrete CASes with the actual data.

I see there as being only one concrete CAS that contains all the data.
The CasViews just have different indexes over that data.  A single FS
could belong (i.e. be indexed in) more than one CasView.

Also if we serialize the analysis results I see that as serializing a
single CAS, even though there may be multiple views.  Single views
aren't easily serializable since references between FSs in different
views are allowed.

So really, what we call the
CasView I would call the CAS, and that other thing is a CAS container.
All CASes in the same container share the type system and can also share
FSs.
<snip/>
Or we could give up on the word CAS completely and introduce two new
ones.  That might be the least confusing.


Since we've already been using the term "view" in UIMA for a while (in
method names and documentation, even if not in the actual interface
name), I think it would be nice to try to make that terminology
continue to work.

-Adam

Reply via email to