There are some divergences between the GO & Monarch API.
Some can be resolved (e.g. adding parameters to the slimmer route), but some will need more discussions (e.g. implementation specific documentation for each route)
Example: new route created to fullfil the ribbon data model
Some parameters (e.g. ecodes or cross_aspect or exclude_PB) are required and allows to filter the annotations retrieved by evidence code, excluding or not direct annotation to protein binding and allowing the mapping of annotations to different aspects (e.g. BP term through the mapping of a MF term and using a cross-aspect relationship).
It would be nice to have similar parameters for the slimmer route so that they send the same data (ribbon route being the summary, slimmer route for the association table).
This will be solved on the fork of the GO API, but will need to be merged sometime back to the main repo.
There are some divergences between the GO & Monarch API.
Some can be resolved (e.g. adding parameters to the slimmer route), but some will need more discussions (e.g. implementation specific documentation for each route)
Example: new route created to fullfil the ribbon data model
Some parameters (e.g. ecodes or cross_aspect or exclude_PB) are required and allows to filter the annotations retrieved by evidence code, excluding or not direct annotation to protein binding and allowing the mapping of annotations to different aspects (e.g. BP term through the mapping of a MF term and using a cross-aspect relationship).
It would be nice to have similar parameters for the slimmer route so that they send the same data (ribbon route being the summary, slimmer route for the association table).
This will be solved on the fork of the GO API, but will need to be merged sometime back to the main repo.