vnadgir / dkpro-core-asl

Automatically exported from code.google.com/p/dkpro-core-asl
0 stars 0 forks source link

Add a dedicated DKPro POS-Tagging component based on DKPro-TC #611

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Add a flexible PoS Tagger that enables easy change of models including 
creating/using self-trained ones.

Original issue reported on code.google.com by Tobias.H...@gmail.com on 20 Apr 2015 at 3:43

GoogleCodeExporter commented 9 years ago
As far as I can see, the flextag module introduces a possible circular 
dependency between DKPro Core and DKPro TC. The only reason this circular 
dependency does not kick in right now is, that the module uses a release 
version of DKPro TC.

Are there any ideas if/how we can avoid having DKPro TC depend on Core depend 
on TC?

Original comment by richard.eckart on 21 Apr 2015 at 11:57

GoogleCodeExporter commented 9 years ago
I should ask differently: does anybody think this circular dependency is (or 
could be) a problem?

Original comment by richard.eckart on 21 Apr 2015 at 12:03

GoogleCodeExporter commented 9 years ago
I just checked: getting rid of DKPro Core dependencies in DKPro TC might not be 
an option, there are several core modules (incl. 
de.tudarmstadt.ukp.dkpro.core.io.bincas-asl, 
de.tudarmstadt.ukp.dkpro.core.api.metadata-asl) which are hard to avoid.

Original comment by daxenber...@gmail.com on 21 Apr 2015 at 1:50

GoogleCodeExporter commented 9 years ago
BinCas classes could be copied over to TC. But anyway, they are not required 
when *using* a model, they are part of the experimentation stuff. So they 
shouldn't be needed anyway. Same for metadata-asl.

Original comment by richard.eckart on 21 Apr 2015 at 2:03

GoogleCodeExporter commented 9 years ago
Ok, if we continue that way, maybe there is a chance to separate DKPro TC Core 
into 2 modules, and one which doesn't have any DKPro Core dependencies and can 
thus be reuse in DKPro Core itself.

Original comment by daxenber...@gmail.com on 21 Apr 2015 at 2:18

GoogleCodeExporter commented 9 years ago
The dependency first issue I noticed is that the SaveModelTask in TC uses 
Lucene 4.4.0 while DKpro still uses 3.0.3. Unless one sets lucene 4.4 
explicitly an exception is thrown when the saved model is loaded. (origin in 
this dependency mismatch)

A further thing is that I have to use the TC Snapshot 0.8 now due to bugfixes - 
is there a bug fix release of TC scheduled. 

Original comment by Tobias.H...@gmail.com on 22 Apr 2015 at 2:34

GoogleCodeExporter commented 9 years ago
Reg. DKPro TC release: the 0.8.0 release probably won't happen before we moved 
to GitHub. A bugfix release can be done anytime - if somebody volunteers to do 
so :)

Original comment by daxenber...@gmail.com on 22 Apr 2015 at 2:44