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

regulation by pattern #12976

Open
dosumis opened this issue Jan 31, 2017 · 5 comments
Open

regulation by pattern #12976

dosumis opened this issue Jan 31, 2017 · 5 comments

Comments

@dosumis
Copy link
Contributor

dosumis commented Jan 31, 2017

"regulation of X by regulation of Y" terms follow a number of patterns,

e.g.

image

image

I think they should all follow the pattern:

'regulation of X' and regulates some Y

e.g.

image

The regulation of Y term is unnecessary as the pattern makes it an inferred superclass (see above).

@tberardini
Copy link
Contributor

Makes sense to me.

@tberardini tberardini assigned tberardini and dosumis and unassigned tberardini Feb 1, 2017
@dosumis dosumis removed their assignment Feb 2, 2017
@tberardini
Copy link
Contributor

Who would implement this pattern and fix existing terms? Can someone assess the scope by a clever query (terms and their current logical defs) and attach the results please? Perhaps not a manual, one-by-one job but done computationally?

@ukemi ukemi added this to Ontology meeting TBD in ontology weekly meetings Feb 7, 2017
@ukemi ukemi moved this from Ontology meeting TBD to Ontology Call February 9, 2017 in ontology weekly meetings Feb 7, 2017
@ukemi
Copy link
Contributor

ukemi commented Feb 8, 2017

This makes sense to me too. I thought this was what @tberardini , @cmungall and I had agreed on before. I wonder how the others crept in. I remember there was some question about directionality of the inferences when we discussed this before, ie there was an issue about which process was the regulator and which was the target, so we should look carefully at that again. @cmungall do you remember?

@ukemi ukemi moved this from Ontology Call February 9, 2017 to Ontology call February 16th 2017 in ontology weekly meetings Feb 14, 2017
@dosumis
Copy link
Contributor Author

dosumis commented Feb 23, 2017

  • TODO: Specify design pattern
  • TODO: Build a table to specify all terms that should follow the pattern.
    • TODO Find a list of terms to apply the pattern to. This probably needs to be done lexically (at least in part), by searching for 'regulation by' in the label.
  • Use table to automate retrofit (via SCOWL?)

(see #12995 for precedent)

@ukemi ukemi moved this from Ontology call March 31st 2017 to Ontology meeting TBD in ontology weekly meetings Apr 6, 2017
@pgaudet
Copy link
Contributor

pgaudet commented Jul 5, 2017

related to #13166

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
ontology weekly meetings
Ontology meeting TBD
Development

No branches or pull requests

4 participants