Create a new release with some improvements (1.5)

[fcbond]

• remove synsets with deprecated ilis (move translations from superseded concepts)
  • take from merges in oewn
  • identify British (and other variants), e.g. moke British informal for donkey; look also at Domain–Region: united_kingdom (and other countries)
  • add new omw formatted wordnets?
  • merge with TUFS data https://github.com/fcbond/tufs @ArthurBond
  • add new MCR data from @ekaf #25

[fcbond]

We could go two ways with synsets like moke "British informal for donkey"

1. link it with ir_synonym and make sure both sides have the same translations
2. merge, and mark the senses with the dialect and register tags
   • so moke is in donkey but marked with Domain-Region united_kingdom and exemplifies informal

[ekaf]

take from merges in oewn

@fcbond, this sounds ambiguous, and may not be optimal: merges are relative to a target English Wordnet version, so you would for ex. pick either OEWN 2021 or 2022, and then deal with different merges in later OEWN versions? It might be better not to handle the merges in OMW-data: NLTK now handles OMW merges seamlessly with any OEWN version, and @goodmami might eventually consider a similar approach in Wn for solving the related issue https://github.com/goodmami/wn/issues/179

[arademaker]

merge, and mark the senses with the dialect and register tags so moke is in donkey but marked with Domain-Region united_kingdom and exemplifies informal

I prefer this option

[goodmami]

Also consider fixing #32 for this release.

@goodmami might eventually consider a similar approach in Wn for solving the related issue https://github.com/goodmami/wn/issues/179

The issue is no longer fresh in my mind, but I don't think I was planning on making any significant changes to Wn. More likely I would suggest some documentation about how to deal with such merges, such as using the code snippet I wrote in that issue. But I should first check out how it was handled in the NLTK.