Skip to content

Commit bcf162f

Browse files
erik-whitingmatentznnataled
authored
Add CONTRIBUTING.MD sentence (OBOFoundry#2341)
* Add CONTRIBUTING.MD sentence * Update fp-010-collaboration.md * Update fp-010-collaboration.md * Update fp-010-collaboration.md * Update principles/fp-010-collaboration.md * Update principles/fp-010-collaboration.md --------- Co-authored-by: Nico Matentzoglu <nicolas.matentzoglu@gmail.com> Co-authored-by: Darren A. Natale <nataled@users.noreply.github.com>
1 parent 2ca2acc commit bcf162f

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

principles/fp-010-collaboration.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,14 +26,15 @@ It is expected that Foundry ontologies will collaborate with other Foundry ontol
2626
- _Contribution to external ontology_: Plant Ontology (PO) curators contribute definitions to Gene Ontology (GO) for biological processes and cell components in plants. PO then uses the GO terms in their definition of corresponding structures and stages.
2727
- _Documentation of collaboration_: Cell Line Ontology (CLO), Cell Ontology (CL), and Ontology of Biomedical Investigations (OBI) published a paper sorting out their overlap and documented working together. Sarntivjiai et al., "CLO: The cell line ontology", J. Biomed. Sem., 2014, 5, 37. http://www.ncbi.nlm.nih.gov/pubmed/25852852
2828
- _Providing terms upon request_: The Disease Ontology (DO) responded to a request from the PRotein Ontology for curation of certain disease terms.
29+
- _Providing guidance on how to contribute_: The Relations Ontology (RO) GitHub includes a [CONTRIBUTING.md](https://github.com/oborel/obo-relations/blob/master/CONTRIBUTING.md) file.
2930

3031
### Counter-examples:
3132

3233
Interactions between ontologies developed by the same entity (person, consortium) are not evidence of collaboration.
3334

3435
## Criteria for Review
3536

36-
Ontology developers must document their attempts at an open dialog with OBO Foundry members, for example by attempting to ascertain if there are other possible ontologies in (or overlapping) the domain of interest. Such documentation can be a simple pointer to an e-mail thread on the OBO discuss list. If there are other ontologies that might need to be aligned or have boundaries determined, evidence of coordination or cooperation should be provided. Further evidence of collaboration may include examples of terms that have been provided to other ontologies in the OBO Foundry community. Finally, hosting or participating in collaborative workshops or meetings attended by OBO Foundry community members is considered evidence of collaboration.
37+
Ontology developers must document their attempts at an open dialog with OBO Foundry members, for example by attempting to ascertain if there are other possible ontologies in (or overlapping) the domain of interest. Such documentation can be a simple pointer to an e-mail thread on the OBO discuss list. If there are other ontologies that might need to be aligned or have boundaries determined, evidence of coordination or cooperation should be provided. Further evidence of collaboration may include examples of terms that have been provided to other ontologies in the OBO Foundry community, while evidence for a willingness to collaborate includes the creation of a CONTRIBUTING.md file to provide guidance for contributions ([learn more](http://mozillascience.github.io/working-open-workshop/contributing/)). Finally, hosting or participating in collaborative workshops or meetings attended by OBO Foundry community members is considered evidence of collaboration.
3738

3839
## Feedback and Discussion
3940

0 commit comments

Comments
 (0)