Darren A. Natale

Looks like all aspects of this have either been taken care of, or have a ticket to do so.

The only concern I have is with the 'strength' of this requirement, and its scope. Strength referring to dashboard report error, warn, or info. I'm certain that a clash with...

It's basically written that way now, at least by interpretation. I'm not objecting or wavering, really, but I don't recall any discussion of nuances like those I mentioned. Perhaps an...

@matentzn as the pull request focuses on wording, I'm going to put your comment on the general ticket for this, and respond there.

1) Chris M. is correct that the PRO idspace used to be 'PRO' but changed to 'PR' to avoid clashing with UniProt's 'PRO_' (at the time PRO began, these identifiers...

With the exception of GOCHE, they are there because PRO references them (see my reply above). Only recently did I realize that OORT (which we've used to convert OBO to...

I'm unfamiliar with that service. What does it do? As far the unregistered prefixes used by PRO, these will no longer default to an obolibrary PURL. That was fixed as...

In terms of branding, bear in mind that we (and others) often refer to the principles as 'best practices', so keep that in mind when deciding what to call these....

Notes from Ops meeting 2022-09-06: Nomi suggests that minutes could be published on github, affording the opportunity to redact. Pier suggests we can use obo-discuss as the gatekeeper. James affirms...

Points from EWG discussion: 1) The first proposed solution falls outside the purview of this principle. However, the second solution can be addressed. P16 "maintenance" is not at all appropriate...