Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add wrappers based on Uby #3

Open
zesch opened this issue Apr 7, 2015 · 4 comments
Open

Add wrappers based on Uby #3

zesch opened this issue Apr 7, 2015 · 4 comments

Comments

@zesch
Copy link
Member

zesch commented Apr 7, 2015

It would be good to wrappers that use the Uby API instead of the native ones.

@judithek
Copy link
Member

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:

  • some discussion in order to get the LSR - UBY mapping right
  • adapting the wrappers
  • testing the changes

@judithek
Copy link
Member

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);

@judithek
Copy link
Member

I am currently mapping LexsemResource to Uby, these are the notes (added iteratively):

Entity -> LexicalEntry (access to POS and senses)

@judithek
Copy link
Member

regarding LexicalSemanticResource:

LexicalSemanticResource -> Lexicon (mostly) or Uby for cross-resource access

getResourceName(); -> Lexicon.getName()

Set getEntity(String lexeme) -> uby.getLexicalEntries(lexeme, null, lexicon)
Set getEntity(String lexeme, PoS pos) -> uby.getLexicalEntries(lexeme, pos, lexicon)

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants