Principle #13 "Notification" : specify types of changes requiring notifications about obofoundry.github.io

[nlharris]

See also: Principle #13 "Notification" - NEW PROPOSED PRINCIPLE #1715

[nataled]

My recollection of discussion of this principle is that it IS very subjective, and the guidelines were kept a bit vague to err on the side of flexibility (hence the clause "...and any other[types of change]s that are determined with stakeholder benefit in mind"). The major concern cited was that this can end up being a very heavy-weight principle for smaller ontologies. That being said, it is likely that we could come up with a minimum set of 'important' notifications.

[balhoff]

Discussed in OFOC call 2023-07-11: agreement that it would be useful to add examples to the principle page for the kinds of changes that it's useful to notify users about. Please add suggestions to this issue.

[matentzn]

The most important one is: planned obsoletions. This can help users to intervene if necessary. I would start with that and then add others if needed.

[matentzn]

Removed the OFOC call label as no clear action items for the Ops call. At the last meeting, 13 people did not have any further opinion about this.