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

No inverse relation for similar/near_synonym (i.e. near_antonym) #75

Open
simongray opened this issue Jun 14, 2021 · 3 comments
Open

No inverse relation for similar/near_synonym (i.e. near_antonym) #75

simongray opened this issue Jun 14, 2021 · 3 comments
Labels
enhancement New feature or request

Comments

@simongray
Copy link

I noticed that similar is basically the GWA name for the relation called near_synonym elsewhere.

However, what about near_antonym? I have multiple near_antonym relations in the old Danish wordnet dataset and I am not sure how to represent them when there's only similar/near_synonym.

There's a selection of antonym relations available in the form of...

  • Antonym (antonym)
  • Gradable Antonym (anto_gradable)
  • Simple Antonym (anto_simple)
  • Converse Antonym (anto_converse)

... but neither of them seem to describe near antonyms.

I guess the general antonym relation is most applicable, but I think using it would result in some information loss...? I would be grateful to hear any better suggestions you may have.

@jmccrae jmccrae added the enhancement New feature or request label Jun 14, 2021
@jmccrae
Copy link
Member

jmccrae commented Jun 14, 2021

Any relation can be specified by means of the other property and the type annotation.

This property could be added if other wordnet projects also require it.

@simongray
Copy link
Author

So other + type is how you are supposed to model "foreign" relations in WN-LMF, right?

From reading the example snippet it is not entirely clear to me how I would use it. The example has adc:type (does dc: refer to Dublin Core?), but the "emotion" relation type isn't mentioned anywhere else on the page so I'm a bit unsure what the example actually expresses. I guess "dc:type" is actually a relation name, but its namespace is somehow implied?

How would you express a foreign relation in WN-LMF that is explicit? Using a full URI?

Rght now I am modelling our data using RDF rathe than WN-LMF, but I want to match the relations in GWADOC as closely as possible. I guess in this case I should just express it with either our own custom relation or the EuroWordNet relation, rather than use other + type?

@jmccrae
Copy link
Member

jmccrae commented Jun 14, 2021

There isn't really an option to use an external URL in the LMF serialization of the schema. In RDF, you can just define your own relation of course.

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

No branches or pull requests

2 participants