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 documentation from the semantic relations #33

Closed
fcbond opened this issue May 13, 2018 · 11 comments
Closed

Add documentation from the semantic relations #33

fcbond opened this issue May 13, 2018 · 11 comments
Assignees

Comments

@fcbond
Copy link
Member

fcbond commented May 13, 2018

It would be good to use the names, short descriptions and possibly link to the semrel documentation.

  1. We need to have the semrel documentation in github
  2. It should be visible somewhere (in GWA or OMW (or both)) so we can link to it
@arademaker
Copy link
Member

Added @viguardieiro

@fcbond
Copy link
Member Author

fcbond commented Feb 25, 2019

Currently the sense-level symbol dictionary is inlined in the omw_concept.html template:

 {% set sl2sym = {1:'⇔', 4:'⊞', 5:'⊳'}  %}

We only have symbols for antonym, pertainym, and derivation. This should be replaced and extended by the docs.

@goodmami
Copy link
Member

goodmami commented Mar 6, 2019

Documentation is live: https://globalwordnet.github.io/gwadoc/

But it still needs work to be filled in, and currently there is no way to select a different language (although we need more data in other languages for that to be relevant).

@goodmami
Copy link
Member

@fcbond pertainym and derivation are not described in gwadoc. Neither is participle (which is mentioned in OMW's srel.tab). I thought I had heard that pertainym was superseded by another relation, like also or other or something, but now I don't see any record of that, so perhaps I imagined it. So what is the current status of these 3 relations?

@fcbond
Copy link
Member Author

fcbond commented Mar 28, 2019 via email

@goodmami
Copy link
Member

goodmami commented Apr 3, 2019

So to be clear, this is the list of sense-sense relations?

  • antonym
  • also
  • also_sees
  • participle
  • pertainym
  • derivation
  • domain_topic
  • has_domain_topic
  • topic_domains
  • domain_region
  • has_domain_region
  • region_domains
  • exemplifies
  • is_exemplified_by
  • usage_domains
  • similar
  • other
  • syntactic_marker
  • verb_groups

And maybe also several more from #63 ?

What about sense-synset relations?

@fcbond
Copy link
Member Author

fcbond commented Apr 3, 2019 via email

@goodmami
Copy link
Member

goodmami commented Apr 3, 2019

Ok

and I guess 'other', just in case?

How about we leave it out and add it if there's a need. It's not hard to add another relation to gwadoc; it's harder to recognize that one is unnecessary.

@fcbond
Copy link
Member Author

fcbond commented Apr 3, 2019 via email

@goodmami
Copy link
Member

goodmami commented Apr 4, 2019

I began adding these to gwadoc under a separate namespace (e.g., sense_sense_rels.antonym) but realized that the flat list we defined does not fit in the hierarchy we have for synset_synset_relations. E.g., we'd have to include constitutive, other, and domain for them to fit somewhere (and define new branches for the sense-only relations). But maybe if they are in a separate namespace they fit in a different hierarchy? But also how do we deal with reverse relations?

It makes me wonder, again, why we need to keep these in separate namespaces at all, instead of just putting some form.sense_sense=True, form.synset_synset=True flags to show their applicability. Do we expect project names to vary depending on the source or target type of a relation? For things like examples, can't we just annotate them to indicate which kind it is an example of (e.g., "this is a sense--synset example for relation x")?

fcbond added a commit that referenced this issue Apr 21, 2019
@fcbond fcbond closed this as completed Apr 25, 2019
@fcbond
Copy link
Member Author

fcbond commented Apr 25, 2019

I think this is done for now.

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

No branches or pull requests

3 participants