3 Jun 15:19
Re: Parameters in uima descriptors
Steven Bethard wrote: > Steven Bethard wrote: >> On Thu, May 14, 2009 at 6:29 AM, Thilo Goetz <twgoetz@...> wrote: >>> I don't know the details of what you did, but it sounds to me like >>> you threw many advantages of UIMA (reusability, transparent remotability >>> etc.) right out of the window. >> I don't see why that would be the case. We're still creating >> AnalysisEngineDescriptions, just in Java code, not XML. > [snip] >> I haven't played around with "transparent remotability", but I can't >> see why using Java descriptors instead of XML descriptors would make >> that any harder. Maybe you can elaborate? > > I would like to hear an answer to this if anyone knows. Is there > something you can do with an XML descriptor that you can't do with an > AnalysisEngineDescription object? You can't do any of the things that our documentation says you can do with a descriptor. You can't read it, for example. > > Steve
Of course, the way you modify an AnalysisEngineDescription Java
object, and the way you modify an XML descriptor object are different.
> There was no proposal, really. The ClearTK folks said (if I understood
> them correctly) that they don't keep any descriptors on disk, but generated
> them dynamically at runtime. To which I replied that this essentially
> makes the components unusable to anybody else, since they're missing the
> descriptors. I'm still not sure though that there wasn't a misunderstanding
> on my part somewhere...
At the moment, we include XML descriptors for our components as well
as the AnalysisEngineDescriptor factory functions. But I'm still
unconvinced that not having those XML descriptors makes our components
"unusable". The UIMA framework APIs work on AnalysisEngineDescription
objects, so components that provide such objects are still fully
RSS Feed