Merge branch 'master' into souzadevinicius/issue2567

OBOFoundry · Apr 17, 2024 · a651754 · a651754
2 parents abd1243 + bfda41c
commit a651754
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 2 deletions.
diff --git a/_data/operations.yml b/_data/operations.yml
@@ -250,7 +250,7 @@ members:
   orcid: 0000-0002-7356-1779
   wikidata: Q60972192
 - affiliation:
-    name: Unversity of Colorado Anschutz Medical Campus, Auroa, CO
+    name: Critical Path Institute, Tucson, AZ
     ror: 03wmf1y16
   country: USA
   github: nicolevasilevsky

diff --git a/ontology/clo.md b/ontology/clo.md
@@ -14,7 +14,7 @@ dependencies:
 - id: uberon
 description: An ontology to standardize and integrate cell line information and to support computer-assisted reasoning.
 domain: anatomy and development
-homepage: http://www.clo-ontology.org
+homepage: https://github.com/CLO-Ontology/CLO
 license:
   label: CC BY 3.0
   url: http://creativecommons.org/licenses/by/3.0/

diff --git a/principles/fp-000-summary.md b/principles/fp-000-summary.md
@@ -36,6 +36,8 @@ P11) <b>Locus of Authority</b> - There should be a person who is responsible for
 
 P12) <b>Naming Conventions</b> - The names (primary labels) for elements (classes, properties, etc.) in an ontology must be intelligible to scientists and amenable to natural language processing. Primary labels should be unique among OBO Library ontologies.
 
+P13) <b>Notification of Changes</b> - Ontologies SHOULD announce major changes to relevant stakeholders and collaborators ahead of release.
+
 P16) <b>Maintenance</b> - The ontology needs to reflect changes in scientific consensus to remain accurate over time.
 
 P20) <b>Responsiveness</b> - Ontology developers MUST offer channels for community participation and SHOULD be responsive to requests.