-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments
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 ;) 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:
|
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 getEntity(String lexeme) -> uby.getLexicalEntries(lexeme, null, lexicon) LexicalRelation -> SenseRelation, relation type as listed in ERelNameSemantics: SemanticRelation -> SenseRelation or SynsetRelation, relation type as listed in ERelNameSemantics: |
It would be good to wrappers that use the Uby API instead of the native ones.
The text was updated successfully, but these errors were encountered: