On Thu, May 14, 2009 at 8:56 AM, Thilo Goetz <[email protected]> wrote:
> Steven Bethard wrote:
>> On Thu, May 14, 2009 at 6:29 AM, Thilo Goetz <[email protected]> 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. See, for
>> example line 184 of:
>>
>> http://code.google.com/p/cleartk/source/browse/trunk/src/org/cleartk/token/TokenAnnotator.java
>>
>> The components are still just as reusable and pluggable. See, for example:
>>
>> http://code.google.com/p/cleartk/source/browse/trunk/src/org/cleartk/example/pos/BuildTestExamplePosModel.java
>> http://code.google.com/p/cleartk/source/browse/trunk/src/org/cleartk/example/pos/RunExamplePOSAnnotator.java
>>
>> And of course, anyone who wants to use our components through XML
>> descriptors can easily write their own.
>>
>> 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?
>
> In my opinion, having to write your own descriptor to an annotator
> that you're not familiar with (and don't necessarily want to become
> familiar with) makes reuse harder.

Sorry, I didn't understand this answer to the "transparent
remotability" question. What part of the "transparent remotability" in
UIMA is not accessible through Java code?

I agree that writing a descriptor for a component you're unfamiliar
with could be daunting, but my experience so far with other peoples'
descriptors was that I didn't really understand what the various
parameters were supposed to be without looking at the code anyway. I
contend that either way, this is a documentation problem. ;-)

Steve
-- 
I'm not *in*-sane. Indeed, I am so far *out* of sane that you appear a
tiny blip on the distant coast of sanity.
        --- Bucky Katt, Get Fuzzy

Reply via email to