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

update predicate mapping to refer to qualified predicates for regulates #1491

Merged
merged 8 commits into from
Sep 23, 2024

Conversation

sierra-moxon
Copy link
Member

@sierra-moxon sierra-moxon commented Apr 16, 2024

fixes NCATSTranslator/Feedback#744
outstanding questions for discussion at DM call:

  • Should “object_aspect_qualifier=’activity_or_abundance’” be required?
  • Should “object_direction_qualifier=’downregulated’” or “object_direction_qualifier=’upregulated’” be required?
  • New associations help define these requirements, what does process regulates process association look like in light of the discussion above.

@mikebada
Copy link
Collaborator

For assertions of regulation (not upregulation/downregulation), the qualified predicate causes shouldn't be used (correct?), in which case the qualified predicate shouldn't be required, correct?

@sierra-moxon
Copy link
Member Author

sierra-moxon commented Apr 18, 2024

@mikebada - I wrote down in the notes that we wanted there to always be an aspect qualifier because we wanted folks to be able to search for activity or abundance qualifier and get back regulates? But then I got into a bit of a circle with causes activity or abundance.... (without a direction)

@mikebada
Copy link
Collaborator

OK, for regulation (not upregulation/downregulation), if we want there to be an aspect (specifically, activity or abundance), then I think that would require affects as the qualified predicate. So, can we say that the allowed values for the qualified predicate for this association type are either affects (for regulation) or causes (for upregulation/downregulation)?

@sierra-moxon sierra-moxon merged commit 03914a7 into master Sep 23, 2024
6 checks passed
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

Successfully merging this pull request may close these issues.

Incomplete population of qualifier patterns in qualified edges leads to incorrect composed edge labels
2 participants