> _indexed indicates that the FS is indexed in one or more views.
>
> "_indexed=0" means that the FS is indexed in view 0, a.k.a. the base
> CAS. SofaFS are the only FS indexed in view 0, which is just there for
> internal bookkeeping.
Ok. I was under the impression that base cas's didn't have indexes,
since its getIndexRepository returns null, but I now see that it may
keep internal indexes. For the sake of my implementation, though, I
can ignore _indexed when it's zero.
> Yes, any view with no sofa should have it's FS added to the
> _InitialView index.
Ok. A related question -- will an xmi file ever contain more than one
view with the same sofa (or with no sofa)? E.g., something like
this:?
<cas:View sofa="1" members="2 3 4"/>
<cas:View sofa="1" members="5 6 7"/>
> > - I assume that the "size" attribs in the XCAS files are not
> > specifying a feature value, [...]
>
> "size" is a feature of an array FS. I believe the number of data
> elements should always match the specified size. Do you have a counter
> example?
It seems odd to say that it's a "feature" of an array FS -- that
implies to me that something like the following should work:
my_array_fs.getIntValue("size")
Presumably that's not what you mean. I don't have any examples of
xcas files where the XML element for an array has a size attribute
that is not equal to the number of children it has; but it was natural
to wonder if such a case would be considered valid xcas (in which case
I need to know how to interpret it) or invalid xcas (in which case
it's redundant information, and I can ignore the size attribute).
> The "v1" XCAS files are from pre-Apache v1.x UIMA code. In v2 the sofa
> feature in annotations is a reference. The purpose of these files was
> to test continued backward compatibility for older XCAS files. You
> should ignore those files.
Ok.
Thanks,
-Edward
