-
Notifications
You must be signed in to change notification settings - Fork 204
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 foodon.md #2609
Update foodon.md #2609
Conversation
Updating usages
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @ddooley for updating the impressive usages for FOODON!
Unfortunately, so we dont open the floodgates to the wild west, we require verifiable usages. For example:
OBOFoundry.github.io/ontology/mondo.md
Line 67 in 0881025
examples: |
A link to a FOODON term on a site is a good proof.
We have had huge debates whether scientific papers count as proof and I forgot were we stand on this, but I guess we said ok.
I was trying to fulfill usages references for FoodOn, but I can't really see what's wrong in yaml file from error report of first step. Also I don't know how to edit what I submitted there from the OBO Foundry "Edit" yaml option which leads to: https://github.com/OBOFoundry/OBOFoundry.github.io/edit/master/ontology/foodon.md |
You can
To edit the yaml file in this PR. Dont worry about QC, for now, I can help you fix it. You have to run "tox -e lint" on the command line, but @jsstevenson will write an action at some point to do this automatically. In the meantime, I can do it for you. |
Ok thanks for your help. I've updated the pull request to include links to specific entries showing FoodOn IDs. |
@ddooley Please see and address the above comments. I updated the usage examples to better fit the formatting described in https://obofoundry.org/principles/fp-009-users.html (See the 'Implementation' and/or 'Examples' section). I also fixed the linting issue you were seeing earlier. |
@deepakunni3 I think everything is resolved now! Thanks for checking it out in detail. |
@ddooley Thank you! Looks good to me :) |
Updating usages