Currently users are expected to supply their own copy of WordNet. It would be
more convenient if we could package WordNet so that the integration is
seamless. The WordNet licence appears to permit such use and redistribution.
However, the extJWNL library we use requires a configuration file where the
path to the WordNet installation is specified. Richard says we can write an
Ant script to fetch WordNet and dynamically generate the configuration file
containing the correct path. This is mostly Greek to me as I don't know
anything about Ant.
One issue we may need to address: How do we handle the fact that there are
seven different published versions of WordNet (1.6, 1.7. 1.7.1, 2.0, 2.1, 3.0,
and 3.1) plus at least one more which was never officially published but is
used in a popular Senseval task (1.7pre)? Each version is about 40 MB in size.
Original issue reported on code.google.com by tristan.miller@nothingisreal.com on 11 Jul 2013 at 10:55
Original issue reported on code.google.com by
tristan.miller@nothingisreal.com
on 11 Jul 2013 at 10:55