I haven't thought this through yet, but here's how I see indexes and
their relation to views right now. Let me know if this agrees with your
views, or how it differs.
The index repository is a set of indexes, at least right now. All it
can do is to give you indexes. The index repository of
On 12/21/06, Thilo Goetz [EMAIL PROTECTED] wrote:
I haven't thought this through yet, but here's how I see indexes and
their relation to views right now. Let me know if this agrees with your
views, or how it differs.
The index repository is a set of indexes, at least right now. All it
can do
All the code is owned by my employer Calcucare GmbH
(www.calcucare.com). I think we have to sign the CCLA too.
CCLA and ICLA are now signed and send via facsimile.
How show we proceed now ?
I can prepare the code at sourceforge for moving to apache this would
be:
+ changing the license
Adam Lally wrote:
Thilo's stuff snipped
I think this basically makes sense. I want to clarify though, that
what we *do* currently have different indexes for each view (for
example each view has its own annotation index, which holds the
annotations relating to that view's sofa). This is done by
On 12/21/06, Thilo Goetz [EMAIL PROTECTED] wrote:
The idea is that a CAS has a current view (best term I can think of
for it right now). Any methods on the CAS that are view-oriented will
apply to the current view. This includes but is not limited to:
getSofa()
getDocumentText()
Adam Lally wrote:
On 12/21/06, Thilo Goetz [EMAIL PROTECTED] wrote:
I didn't mean to suggest to have duplicate indexes. What I meant to say
was, each view should have its own annotation index. In the CAS, each
of these annotation indexes can be accessed separately. In fact, I
think this is
[ http://issues.apache.org/jira/browse/UIMA-135?page=all ]
Adam Lally closed UIMA-135.
---
Resolution: Fixed
Changed entity view mode to use a user-supplied EntityResolver object, rather
than depend on an IBM-specific typesystem.
Remove Entity View mode from
Re: Need for Global indexes
Adam Lally wrote:
snip
Moreover, I think the reverse direction should be true -- indexing an
FS in a view's index repository DOES add it (at least conceptually) to
indexes that apply to the CAS as a whole. I liked this latter idea
because it provided a way to
