OBOFoundry.github.io
OBOFoundry.github.io copied to clipboard
Request for review of the Environment Ontology (ENVO)
Hi all,
I've filled out the review form associated with this issue template to get the ball rolling.
I noticed in the process that our release-bound URIs seem to be out of action since we updated the release process. I've put in a URL to the GitHub release/tag in the meantime, but we'll fix that soon. If you'd like to postpone the review until that's done and we have a new release out, let me know.
Looking forward to the feedback during this process.
Thank you for your submission. The OBO Foundry Editorial Working Group, tasked with overseeing the peer review process, will begin the review at its next meeting. We hope to provide you with feedback in 4-6 weeks.
Many thanks @nataled
In the meantime, our version IRIs are functional (they apparently never went down, but I was using a malformed IRI).
The review version is here: http://purl.obolibrary.org/obo/envo/releases/2019-03-14/envo.owl
@pbuttigieg is chairing the OBO Operations Committee meeting tomorrow (2020-Feb-25). Maybe this issue can be briefly discussed.
(It wasn't.) @nataled are you awaiting more information from @pbuttigieg?
@nlharris Yes, in a sense. The review was completed and the ontology found to contain some deficiencies with respect to some principles (I don't recall the details). We then asked for those to be addressed, followed by an alert to re-review when ready. We are awaiting that alert.
Update: Awaiting feedback from @pbuttigieg. Pier reported that they are actively updating ENVO, and will get back when this round is finished.
Greetings all - many of the issues should be fixed in the next release (several were misconfigurations or syntactic issues, while some have been addressed with support from our community and co-editors).
@nataled as discussed in today's operations call (raised by @cmungall), I'm happy to have the review process made public. Despite the long latency on our side, it may be instructive to the community.
I'm going to leave the "submitter action needed" tag on until the problems have been confirmed to be fixed. "Should be fixed in the next release" is good news, but we all know how sometimes those best intentions can take a while to actually come to fruition.
@pbuttigieg what should the action item be on this now?
Can this be closed?
Hi @pbuttigieg, Since there has been no activity on this issue for quite a long time, we assume that it is no longer relevant and choose to close it to facilitate issues handling on this repository. Please let me know if there are any questions about this process and feel free to reopen it if you think it is still of interest.