Michael Baessler wrote:
Michael Baessler wrote:
Adam Lally wrote:
On Jan 7, 2008 6:56 AM, Michael Baessler <[EMAIL PROTECTED]>
wrote:
I tried to figure out how the ResultSpecification handling in
uima-core
works with all side effects to check how it can be done
to detect when a ResultSpec h
LeHouillier, Frank D. wrote:
We have an annotator that wraps a black box information extraction
component that can return objects of a variety of types. We check the
result specification to see if the object is something we want to output
based the actual string of the name of the type. If you
Adam Lally wrote:
On Jan 24, 2008 9:51 AM, Michael Baessler <[EMAIL PROTECTED]> wrote:
Without looking at the code, I didn't understand why this is a
consequence of the behavior you described above. I thought you said
"and if the type has subtypes, it adds those too"? Anyway, I
definitely t
All,
I am the technical lead of the Automated Metadata Population Service
(AMPS) working group. AMPS is a US Department of Defense (DoD) and
Intelligence Community effort to create a Defense Discovery Metadata
Standard (DDMS)-compliant metadata population web service that many
Federal Governmen
Hi,
is it correct that the code fragment below throws and NPE if one of the
array elements is null and the array is converted to a StringArray?
ArrayFS fsArrayFS = cas.createArrayFS(3);
fsArrayFS.set(0, cas.getDocumentAnnotation());
fsArrayFS.set(1, cas.getDocumentAnnotation());
We have an annotator that wraps a black box information extraction
component that can return objects of a variety of types. We check the
result specification to see if the object is something we want to output
based the actual string of the name of the type. If you take away the
compiled version
The implementation for checking if a feature is in the result spec does
the following:
If the result-spec is not "compiled", it says the feature is present if
it specifically put in, or if its type has the allAnnotatorFeatures flag
set.
If the result-spec is "compiled", it says the feature i
The code which checks if a type or feature is in a result spec, for a
particular language, always includes generalizing the language specifier
by dropping the part beyond the first "-". For example, "en-us" and
"en-uk" are simplified to en. Because of this, I'm thinking of
shrinking the resul
