-
Notifications
You must be signed in to change notification settings - Fork 2
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
KEGG beacon? #63
Comments
I don't really know. Who is asking for KEGG? @cmungall is, I believe, thinking that Rhea will sufficient cover the domain. |
Kegg has restrictive licensing. Be careful. Use reactome? |
For reactions yes. KEGG also has pathways
…On 25 Oct 2018, at 10:17, Richard Bruskiewich wrote:
I don't really know. Who is asking for KEGG?
@cmungall is, I believe, thinking that Rhea will sufficient cover the
domain.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#63 (comment)
|
Melissa suggests that Reactome would adequately suit our needs. Do we wrap Reactome as a beacon or is it adequately covered elsewhere? |
Looking at the licensing terms for KEGG, it seems like our use case is covered. On the other hand they charge $5,000 for organizational subscription. "Licensor grants [...] license to [...] provide a web-based service using KEGG FTP Data. [...] Your Product or Service must not allow Your users to obtain KEGG FTP Data, except in small quantities." https://www.bioinformatics.jp/docs/subscription_organizational.pdf |
Stefano, will the Reactome suffice? Or is KEGG essential? Reactome IP is apparently less onerous ... we could wrap their API (https://reactome.org/dev/content-service)... Oops, @mellybelly, KEGG has their tentacles in that: Finally, KEGG gene and pathway annotations, used to construct the Reactome Functional Interaction (FI) Network, are provided under license to OICR by Pathway Solutions, Inc. The Reactome FI Network data set is intended for use only by the original recipient. The recipient may not distribute the Reactome Functional interaction data files to other users without a license from Pathway Solutions, Inc. If KEGG is a critical data resource, NIH would have to negotiate something. That is not a bad thing, perhaps, since it fosters international collaboration and buy-in. Just don't know how far NIH will go on this project to support that spirit... how much engagement with the Japanese. |
Has biothings explorer ingested enough of KEGG? If not, then should we create a KEGG beacon?
The text was updated successfully, but these errors were encountered: