Merge branch 'master' into nataled-patch-7

Author: nataled

principles/fp-000-summary.md

@@ -24,9 +24,9 @@ P5) <b>Scope</b> - The scope of an ontology is the extent of the domain or subje
 
 P6) <b>Textual Definitions</b> - The ontology MUST have textual definitions for the majority of its classes and for top level terms in particular.
 
-P7) <b>Relations</b> - Relations SHOULD be reused from the Relations Ontology (RO).
+P7) <b>Relations</b> - Existing relations MUST be reused. New relations SHOULD be submitted to the Relations Ontology (RO).
 
-P8) <b>Documentation</b> - The owners of the ontology SHOULD strive to provide as much documentation as possible.
+P8) <b>Documentation</b> - The owners of the ontology SHOULD strive to provide as much documentation as possible. The documentation SHOULD detail the different processes specific to an ontology life cycle and target various audiences (users or developers).
 
 P9) <b>Documented Plurality of Users</b> - The ontology developers SHOULD document that the ontology is used by multiple independent people or organizations.
 

principles/fp-006-textual-definitions.md

@@ -7,7 +7,7 @@ GO TO: [Recommendations/Requirements](#recommendations-and-requirements) |
 
 ## Summary
 
-The ontology has textual definitions for the majority of its classes and for top level terms in particular.
+The ontology MUST have textual definitions for the majority of its classes and for top level terms in particular.
 
 ## Purpose
 

principles/fp-008-documented.md

@@ -10,7 +10,7 @@ The wording of this principle is still in progress, with some issues still to be
 
 ## Summary
 
-The owners of the ontology should strive to provide as much documentation as possible. The documentation should detail the different processes specific to an ontology life cycle and target various audiences (users or developers).
+The owners of the ontology SHOULD strive to provide as much documentation as possible. The documentation SHOULD detail the different processes specific to an ontology life cycle and target various audiences (users or developers).
 
 [This check is automatically validated.](checks/fp_008)
 

principles/fp-009-users.md

@@ -7,8 +7,7 @@ GO TO: [Recommendations/Requirements](#recommendations-and-requirements) |
 
 ## Summary
 
-The ontology developers should document that the ontology is used by
-multiple independent people or organizations.
+The ontology developers SHOULD document that the ontology is used by multiple independent people or organizations.
 
 ## Purpose
 

principles/fp-011-locus-of-authority.md

@@ -7,10 +7,7 @@ GO TO: [Recommendations/Requirements](#recommendations-and-requirements) |
 
 ## Summary
 
-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.
+There MUST 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.
 
 ## Purpose
 

principles/fp-012-naming-conventions.md

@@ -12,7 +12,7 @@ GO TO: [Recommendations/Requirements](#recommendations-and-requirements) |
 
 ## Summary
 
-The names (primary labels) for elements (classes, properties, etc.) in an ontology must be intelligible to scientists and amenable to natural language processing. Each primary label SHOULD be unique among OBO Foundry ontologies, and MUST be unique within its own ontology.
+The names (primary labels) for elements (classes, properties, etc.) in an ontology SHOULD be unique among OBO Foundry ontologies, and MUST be unique within its own ontology.
 
 ## Purpose
 

principles/fp-016-maintenance.md

@@ -8,22 +8,25 @@ title: Maintenance (principle 16)
 
 The wording of this principle is still in progress.
 
-## Summary and Purpose
+## Summary
 
-The ontology needs to reflect changes in scientific consensus to remain accurate over time.
+The ontology SHOULD reflect changes in scientific consensus to remain accurate over time, and MUST be responsive to community requests.
 
-[This check is automatically validated.](checks/fp_016)
+## Purpose
 
-## Implementation
+## Recommendations and Requirements
 
 Ideally, the maintainer of an ontology SHOULD actively monitor for any changes in scientific consensus, but--at a minimum--the maintainer MUST respond to requests from the community pointing out such changes in accordance with the [Responsiveness principle](http://obofoundry.org/principles/fp-020-responsiveness.html). Tentatively, we consider scientific consensus to be reached if multiple publications by independent labs over a year come to the same conclusion, and there is no or limited (<10%) dissenting opinions published in the same time frame. In cases when an area remains controversial, and no consensus is reached, then it is up to the ontology maintainer to either leave out the controversial term, or pick a viewpoint for practical considerations, and note the presence of controversy in an editor note.
 
+## Implementation
+
 ## Examples
 
 ## Counter-Examples
 
 ## Criteria for Review
 
 The developers of the ontology need to include a statement specifying how they are planning to maintain the ontology. We expect that an ontology will be maintained for at least 3 years from the time of acceptance.
+[This check is automatically validated.](checks/fp_016)
 
 <Category:Principles> <Category:Accepted>