You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ChM: Same issue holds for WordNet sense keys, which are currently described as
WordNet 3.0 part of speech and sense key
But should be
WordNet_3.0_eng_senseKey
(equivalent to synsetOffsets, pos tag is not necessary btw).
Implemented this for WordNet, but left it commented for now. We should check which implications this has on alignment imports!
JEK: I checked this quickly.
For WordNet, this does not have any implications since the alignments we currently import for WordNet refer to WordNet synsets, not senses. The import scripts therefore look up original synset IDs.
ChM: I think it is better to move this to the next release, since I have the feeling that this could generally break a lot of tiny things. We thought about revising the package and module structure for the next release. This means that all usage code must be modified anyway. So this seems to be a much better opportunity.
The text was updated successfully, but these errors were encountered:
The date information is missing in the ExternalSystem values in the current 0.6.0 versions of the Uby database
see: https://code.google.com/p/uby/wiki/UbyExternalSystemNaming
OmegaWiki_synTrans
OmegaWiki_definedMeaning
version=2010-01-03
ChM: Same issue holds for WordNet sense keys, which are currently described as
But should be
(equivalent to synsetOffsets, pos tag is not necessary btw).
Implemented this for WordNet, but left it commented for now. We should check which implications this has on alignment imports!
JEK: I checked this quickly.
For WordNet, this does not have any implications since the alignments we currently import for WordNet refer to WordNet synsets, not senses. The import scripts therefore look up original synset IDs.
ChM: I think it is better to move this to the next release, since I have the feeling that this could generally break a lot of tiny things. We thought about revising the package and module structure for the next release. This means that all usage code must be modified anyway. So this seems to be a much better opportunity.
The text was updated successfully, but these errors were encountered: