Principle: Locus of Authority (principle 11)
- Open (principle 1)
- Common Format (principle 2)
- URI/Identifier Space (principle 3)
- Versioning (principle 4)
- Scope (principle 5)
- Textual Definitions (principle 6)
- Relations (principle 7)
- Documentation (principle 8)
- Documented Plurality of Users (principle 9)
- Commitment To Collaboration (principle 10)
- Locus of Authority (principle 11)
- Naming Conventions (principle 12)
- Maintenance (principle 16)
- Responsiveness (principle 20)
There should be a person who is responsible for communications between the community and the ontology developers, for communicating with the Foundry on all Foundry-related matters, for mediating discussions involving maintenance in the light of scientific advance, and for ensuring that all user feedback is addressed.
It is important that there is a person responsible for communication rather than a group of people or a list. Often in communications to a list, the responsibility for responding can be diffused and it is likely that in some scenarios no response will be given. It may also, from time to time, be necessary to engage in strategic communications (e.g. relating to funding or collaboration possibilities) that are not able to be made public, and these should not be conducted on public mailing lists. The designation of a contact person is not to be interpreted as a designation for credit. Note that alternative contacts can be designated in case the primary contact is unavailable. However, as for the primary contact, each alternative contact must be an individual.
Recommendations and Requirements
The name, email address and github username of this person should be provided when requesting to register with OBO. This person must be subscribed to obo-discuss in order to be kept abreast of community developments of relevance to participating ontology projects. The email address of the person who is the locus of the authority must be kept up-to-date, and before that person ceases to have responsibility for the project, they should identify a replacement and update the metadata accordingly (via the OBO Foundry issue tracker) before they move on. The contact person can, of course, delegate these responsibilities as necessary.
For ChEBI, the primary contact person is Adnan Malik (firstname.lastname@example.org).
Mailing list; for ChEBI, email@example.com