Open zesch opened 9 years ago
adding my notes from last week to this issue:
I looked into the LSR wrappers for WordNet, GermaNet, Wiktionary, and this all looks feasible, i.e. using the UBY API instead. Actually, this is an interesting exercise which might improve the UBY API ;) In most cases (not Wikipedia, GermaNet), LSR could then also use Uby databases packaged as Maven artifacts.
Replacing the wrappers with the UBY API consists of at least 3 steps:
note regarding the Uby - LSR mapping:
In Wikipedia, LSR defines article redirects to be synonyms;
the converter for Uby-Wikipedia sets the redirects to RELATED:
senseRelation.setRelName(ERelNameSemantics.RELATED);
senseRelation.setRelType(ERelTypeSemantics.association);
I am currently mapping LexsemResource to Uby, these are the notes (added iteratively):
Entity -> LexicalEntry (access to POS and senses)
regarding LexicalSemanticResource:
LexicalSemanticResource -> Lexicon (mostly) or Uby for cross-resource access
getResourceName(); -> Lexicon.getName()
Set
LexicalRelation -> SenseRelation, relation type as listed in ERelNameSemantics: antonymy, -> ANTONYM synonymy -> SYNONYM
SemanticRelation -> SenseRelation or SynsetRelation, relation type as listed in ERelNameSemantics: holonymy, -> HOLONYM, HOLONYMCOMPONENT, HOLONYMSUBSTANCE, HOLONYMMEMBER, HOLONYMPORTION, HOLONYMPART hypernymy, -> HYPERNYM, HYPERNYMINSTANCE hyponymy, -> HYPONYM, HYPONYMINSTANCE meronymy, -> MERONYM, MERONYMCOMPONENT, MERONYMSUBSTANCE, MERONYMMEMBER, MERONYMPORTION, MERONYMPART cohyponymy, -> there is no correspondence
It would be good to wrappers that use the Uby API instead of the native ones.