-
Notifications
You must be signed in to change notification settings - Fork 3
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
suggestions for editors guide #23
Comments
Nice!
…On Wed, 25 Jul 2018, 18:27 Hervé Ménager, ***@***.***> wrote:
Here are a few suggestions for modifications in the editors guide
@joncison <https://github.com/joncison> @veitveit
<https://github.com/veitveit>. Would you agree with these?
- "If you are editing the EDAM.owl file directly" -> "If you are
editing the EDAM OWL file directly"
- "EDAM must always evolve, which means additions, edits, and
occasionally deprecations: marking-up concepts as not recommended for use:
the EDAM developers follow special deprecation guidelines for this." ->
"EDAM must always evolve, which means additions, edits, and occasionally
deprecations: the EDAM developers follow special deprecation guidelines for
this."
- [Data] "MUST have *at least one* corresponding concept in the Format
subontology"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/APEZhWVJRE3qWYWgcIftQclKuKaToIoTks5uKJx3gaJpZM4VgZsa>
.
|
cool ... @hmenager nice if you can clone the repo. and commit the changes |
Hi people. This is obviously an old issue, but I've cloned the repo and made the suggested changes. In case you're interested, I could make a pull request to hopefully have the file updated. |
Thank you so much @melibleq for picking this up!🙏🏽 Please go ahead with your PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here are a few suggestions for modifications in the editors guide @joncison @veitveit. Would you agree with these?
The text was updated successfully, but these errors were encountered: