OBOFoundry.github.io
OBOFoundry.github.io copied to clipboard
OBOFoundry
Principle #13 "Notification" - NEW PROPOSED PRINCIPLE
Draft text has been uploaded in a new pull request https://github.com/OBOFoundry/OBOFoundry.github.io/pull/1714
Please comment on the text as a whole and on specific areas for change.
The EWG believes there is the possibility for automating this, though doing so would likely require narrowing the scope of allowable mechanisms for notification. Automation would involve ascertaining the date of announcement as it compares to date of implementation.
From @matentzn:
Wow this is some principle.. :) I love this, but this will put a huge burden on ontology developers.. If they use GitHub, maybe we can promote an ongoing diff report that is published at some predefined purl location like /diff.txt or some such.. It will also be massively complex otherwise to automatically test this. I am not against it, just.. worried its quite a tough one to meet!
This principle was moved forward during the Operations call of 30-Nov-2021, so the principle itself is set. There was, however, general agreement during the call that this could be a burden, which is why we went with "should" instead of "must". I agree with your sentiment regarding automated testing. However, (1) we have so far one other principle with no testing; and (2) most checks done by the dashboard only approximate the principle anyway (though the EWG is working on ways to diminish that).
Awaits refinement of wording by EWG. We typically do so when the person who wrote the original draft is available, but I was recently informed that this person is no longer available for meetings. Will be taken up again when manpower allows.
Who was the person who wrote the original draft? It shows up as being by you.
I'm the one that wrote the ticket on github. The draft was by Krishna Udaiwal.
Writing is done, page is ready, awaiting review by OFOC and linking on main site. To review: https://obofoundry.org/principles/fp-013-notification.html
Action items (from last call)
- [x] Ask for feedback on obo-discuss
- [x] Ask feedback on Slack’s #general channel
- [x] When feedback is in, add back on OFOC agenda.
Barring any feedback that scuttles the whole thing or that requires major revision, this principle will become official as of 2023-03-28.