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

Adding something like a SenseDefinition element to Sense? #65

Open
anasfkhan81 opened this issue Jul 6, 2022 · 5 comments
Open

Adding something like a SenseDefinition element to Sense? #65

anasfkhan81 opened this issue Jul 6, 2022 · 5 comments

Comments

@anasfkhan81
Copy link

anasfkhan81 commented Jul 6, 2022

Might seem redundant (given synset definition) but would be useful in the case where the definition is taken from a dictionary or some other pre-existing lexical resource (as is our case)

@fcbond
Copy link
Member

fcbond commented Jul 6, 2022 via email

@jmccrae
Copy link
Member

jmccrae commented Jul 6, 2022

I am not so sure, as it seems to go against the idea of WordNet of using synsets as the main conceptual modelling. I also feel that it would create a lot of confusion.

Another solution for @anasfkhan81 is to move all definitions to the synset and use the Dublin Core properties to indicate how they were extracted from the dictionary.

Are there any existing wordnets that model definitions at the sense level?

@fcbond
Copy link
Member

fcbond commented Jul 6, 2022 via email

@anasfkhan81
Copy link
Author

anasfkhan81 commented Jul 6, 2022

From Globalex I know dictionary definitions are also a big part of the Turkish KeNet (where they use them to carry out diachronic research on sense changes) and in general, in the case a WN has been bootstrapped or derived from another lexical resource I definitely think the original definitions should be accessible somehow (whether from Synset or Sense) especially in the case of (semi)-automatic deriviation. From this pov i think they would count as an auxiliary part of the sense layer of a WN rather than part of the main conceptual modelling which is as always determined by synsets, their definitions and inter-relations.

@goodmami
Copy link
Member

goodmami commented Jul 7, 2022

I'd agree with @jmccrae that definitions belong on synsets. A definition explains what something means and the synset is the locus of that conception. In contrast, we allow examples on senses because with an example you generally want to see the usage of a particular word with a given meaning (I'd even argue that examples should only appear on senses).

I appreciate the argument that the source material for a wordnet may be a dictionary where each word (and thus each synonym of some concept) has a definition, but I don't think a wordnet is necessarily a superset of a dictionary; i.e., that it should fully encode all information that a dictionary does. If it is important to capture the definitions of all the words, a synset definition with dc:source, as @jmccrae suggested, seems adequate.

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

4 participants