Core review criteria

For each term considered in the Core review, please check each of the following:


 * 1) Labels: check that all the term's labels are clear and accurate
 * 2) rdfs:label: required
 * 3) editor preferred term: required, should match the rdfs:label (check will be done during release process too)
 * 4) alternative terms: recommended
 * 5) Textual Definition: check that the textual definition is clear and accurate
 * 6) should follow Aristotelean pattern, giving the parent term and the differentia: e.g. the definition of "documenting" is "a planned process in which input information is used to create or add to a document"
 * 7) must include a definition source
 * 8) Comment: It would be desirable to always have the same structure of the textual definition i.e. when C-Thing SubClassOf P-Thing then either "A C-Thing is a P-Thing that..." or "A P-thing that..."
 * 9) Logical Definition: there must be a logical definition (?)
 * 10) Example of Use: there should be at least one example of use
 * 11) Other Annotations: make sure that other annotations are accurate and up-to-data
 * 12) must have term editor
 * 13) has curation status will be updated to 'ready for release' when review is done
 * 14) editor note: optional
 * 15) imported from: only for terms imported from another ontology
 * 16) Uses in the Core (optional): review the uses of this term in other OBI Core classes
 * 17) Uses in OBI (optional): review the uses of this term in other OBI classes

For details of metadata requirement, please see: http://obi-ontology.org/page/OBI_Minimal_metadata