Adam Lally wrote:
On 12/13/06, Thilo Goetz [EMAIL PROTECTED] wrote:
I couldn't agree more (except for the default bag indexes). It makes no
sense at all that global indexes must be accessed via a particular view.
I can't tell what exactly you're agreeing to. Are you thinking that
anything
Adam Lally wrote:
...
Possible conclusion for the Java API: We should provide a way to get
all of the FS from the CAS and add new FS to the CAS, as part of the
Base CAS API. Note that we currently jump through hoops in XMI/XCAS
serialization because we don't have such access.
That's a basic
On 12/13/06, Thilo Goetz [EMAIL PROTECTED] wrote:
I couldn't agree more (except for the default bag indexes). It makes no
sense at all that global indexes must be accessed via a particular view.
I can't tell what exactly you're agreeing to. Are you thinking that
anything indexed in a view
On 12/12/06, Eddie Epstein [EMAIL PROTECTED] wrote:
Currently the base CAS and views have the same API set, the only
differences between the base CAS and all other views are:
- the base CAS has no index repository
- the base CAS has no Sofa
Given a base CAS it is possible to create FS,
Adam Lally wrote:
...
(2) It is confusing that an object of type CAS could be either a
base CAS or a view. A base CAS has several unsupported operations,
which throw exceptions if you call them. I cannot think of a rational
justification for this design other than backwards compatibility.
Most
On 12/12/06, Adam Lally [EMAIL PROTECTED] wrote:
Maybe someone can come up
with a brilliant idea about how we can fix this and still support
migration? That would be nice.
Here's a shot at a brilliant idea. Or it may be a stupid idea...
often it's a fine line between the two. :)
Create
[EMAIL PROTECTED] wrote:
Also, I'm still not sure how I feel about the zero-arg getView() -
what view does it get? What would the Javadoc for this method say?
-Adam
getView() returns either 1: a view specifically selected for this
component by Sofa mapping, or if no Sofa mapping 2: the
On 12/11/06, Thilo Goetz [EMAIL PROTECTED] wrote:
Also, I think it's premature to look to the OASIS work for guidance.
Let's follow our own good sense until the standard is at a stage where
we feel confident it won't change much.
I think that depends on the situation. Certainly, I would not
Please help me here, I'm not really up-to-date with the whole view/Sofa
concept. Can't we provide a process method that is fully backward
compatible, without having to call this? I think that would be the
preferable solution.
Also, I think it's premature to look to the OASIS work for
On 12/11/06, Thilo Goetz [EMAIL PROTECTED] wrote:
So what about Adam's suggestion to separate a CAS from a view? What
*is* the difference, conceptually?
A View has an index repository and a Sofa. (The Sofa may become
optional, but in the current impl. it is not.)
A CAS holds the analysis
Adam Lally wrote:
On 12/11/06, Thilo Goetz [EMAIL PROTECTED] wrote:
So what about Adam's suggestion to separate a CAS from a view? What
*is* the difference, conceptually?
A View has an index repository and a Sofa. (The Sofa may become
optional, but in the current impl. it is not.)
A CAS
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
Adam Lally wrote:
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.
From an interface point of view, does it matter? As I understand it,
you can neither
Adam Lally wrote:
From an interface point of view, does it matter? As I understand it,
you can neither create nor access FSs in the CasContainer (I'm just
calling it that to avoid confusion, not because I think that's a good
name). Or can you? What is the division of labor here?
What I
Will this change to user code be able to be done automatically by a
script? It seems like it might be a little ugly to do.
Yes, a single line inserted after process(inCas,...):
inCas = inCas.getView(); // automatically added by migration
Also it still very confusing that the CAS
On 12/8/06, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Yes, a single line inserted after process(inCas,...):
inCas = inCas.getView(); // automatically added by migration
I suppose that should work. It might be a bit ugly for multi-Sofa
annotators who expect inCas to refer to the Base CAS.
16 matches
Mail list logo
