I have batch files for some of them, that I use to re-train and parse the data formats...
James On 12/2/2011 11:11 PM, Jason Baldridge wrote: > Yeah, I would not propose to go full-GATE style with this. I just meant it > would be easy to write little wrappers that could produce data for those > other packages that would make it easy to run them -- they wouldn't even > necessarily be included with the OpenNLP distro (for the obvious reason of > not being Apache-clean). > > Another way to look at this would be to have adaptors and command line > support for running OpenNLP on the data formats and such that those other > packages expect. > > On Fri, Dec 2, 2011 at 6:21 AM, Aliaksandr Autayeu > <[email protected]>wrote: > >> Nice idea! And I agree with Jörn that a good plugin strategy will be key to >> handling this with easy. An interesting task, actually. >> >> Another point is that this seems to move us towards a GATE-like way :) Just >> a little bit. And reminds me of a need to focus. >> >> Aliaksandr >> >> On Fri, Dec 2, 2011 at 10:37 AM, Jörn Kottmann <[email protected]> wrote: >> >>> On 12/2/11 6:20 AM, Jason Baldridge wrote: >>> >>>> I've only very quicky read through this, and don't have a strong opinion >>>> on >>>> whether to keep CLI as is or move it out. However, one interesting >>>> possibility with moving it out would be that we could provide interfaces >>>> to >>>> other packages, e.g. Stanford tools, Lingpipe, Mallet, etc, for >>>> performance >>>> comparisons. That would be useful for our purposes, and would be a >> useful >>>> capability for others (especially in research), and it is something we >>>> wouldn't want to have as part of the core library (obviously). >>>> >>> If you do that you get dependencies on all these tools. Some of the >>> mentioned >>> tools are not compatible with Apache license handling which makes it >>> impossible >>> for us to distribute them. >>> >>> Anyway it is a nice idea and I believe if you do that you should make one >>> small sub-project per project. If necessary you can place them at an >>> external >>> code hosting site. >>> >>> For this we need a good plugin strategy for our CLI tools, so that people >>> can >>> easily add their own tools. >>> >>> Jörn >>> >>> >>> > >
