Closed GoogleCodeExporter closed 9 years ago
XMIReader and XMIWriter in cleartk-timeml write XMI files in locations specific
to the TempEval data format (using the URI fragment). They would have been
simplified if we had JCasUtil.readXMI and JCasUtil.writeXMI as suggested in
Issue 121.
Original comment by steven.b...@gmail.com
on 6 May 2012 at 6:30
DKPro Core has an XmiReader and XmiWriter supporting recursive reading and
writing of data (preserving the directory structure), and powerful Ant-like
patterns to include/exclude files. It can optionally compress the data, can
save the type system along with the XMI and can even read data from JARs or
from the classpath.
Original comment by richard.eckart
on 6 May 2012 at 9:32
Sounds like something that might be useful to add to uimaFIT. What does it do
with URI fragments?
Original comment by steven.b...@gmail.com
on 8 May 2012 at 8:54
I'd like to keep uimaFIT clean of readers/writers. Feel free to use DKPro Core.
We are continually improving it ;)
Some of the readers we have in DKPro support generating multiple CASes from a
single source document. These use the URI fragment to store a sub-document ID.
Writers usually write these as part of the target file name then.
Original comment by richard.eckart
on 8 May 2012 at 10:20
Btw. we are happily combining ClearTK with DKPro, in particular using the
ClearTK-ML stuff. Works very nice for us!
Original comment by richard.eckart
on 8 May 2012 at 10:21
Original comment by richard.eckart
on 7 Jan 2013 at 4:51
Closing as duplicate of issue 121.
Original comment by richard.eckart
on 25 Aug 2013 at 8:23
Original issue reported on code.google.com by
lee.becker
on 4 May 2012 at 11:55