Okay. I guess I'd like to more or less go in and blast things apart, so anything like that should go in before. Feel free to make progress on those for now, and I'll get to coding later this month, probably.
I also agree that we can break with the old model format. In that regard, we should look at this: http://en.wikipedia.org/wiki/Predictive_Model_Markup_Language (I haven't had a chance to review that yet, myself.) Jason On Tue, May 3, 2011 at 3:16 AM, Jörn Kottmann <[email protected]> wrote: > On 5/3/11 4:25 AM, Jason Baldridge wrote: > >> Sounds good. I'd like to start working on this after our spring semester >> has >> ended (two more weeks). -Jason >> >> > There are also a few changes we could just do on the current implementation > without > the API redesign, for example I would like contribute my multi threaded GIS > training > changes, refactoring the code to inline instance variables, introduce the > progress > monitoring, etc. > > An advantage of doing these things before we release a new API is that we > then have one > more try to fix things which might turn out to not be as well as we > expected them. > > Anyway I created a new wiki space, so we can go ahead and sketch down the > new API: > https://cwiki.apache.org/confluence/display/OPENNLP/Maxent+Refactoring > > Jörn > > -- Jason Baldridge Assistant Professor, Department of Linguistics The University of Texas at Austin http://www.jasonbaldridge.com http://twitter.com/jasonbaldridge
