Hello!

I would like to develop a generic PEAR Wrapper application that reads in a
CAS Xmi and populates it with Features from a  PEAR. So, this is what it
will do:

1.input a cas xmi generated by a separate (but static) CPE
2.input a PEAR xmi descriptor after it is installed (or even a whole
PEAR).  The PEAR will not always be the same.
3.run the PEAR's analytics on the cas xmi
4.output an updated cas xmi

I have been able to use the documentAnalyzer in the uima tools to run
PEARs, and that works fine for reading in raw text, the same for the
runAE.sh tool.  However, I run into typing issue when I try to run a cas
xmi, which I believe to be caused by not inputing the initial CPE type
descriptor

Below is I what I'm thinking I will need.  Could anyone comment if they see
some kind of glaring hole, or perhaps a more efficient approach?

1. Type Descriptor from initial CPE
2. The expanded PEAR's descriptor xml
3. A Collection Reader which performs CAS xmi deserialization
4. Something ( another AE ? ) which executes the PEARs analytics
5. Final AE to act as a XMI Writer.


Any input would be much appreciated! Thank you!

Neal

Reply via email to