Difference between revisions of "Ontology Development"

From GO Wiki
Jump to: navigation, search
m (Completed projects)
m (SPARQL checks on the ontology)
Line 181: Line 181:
=Quality Control=
=Quality Control=
==SPARQL checks on the ontology==  
==SPARQL checks on the ontology==  
[[https://github.com/rctauber/robot/tree/reporting/robot-core/src/main/resources/queries |SPARQL checks on the ontology]]
[https://github.com/rctauber/robot/tree/reporting/robot-core/src/main/resources/queries SPARQL checks on the ontology]
==Ontology release pipeline==
==Ontology release pipeline==

Revision as of 05:47, 12 April 2019

Group's focus

This group's purpose is to ensure that the Gene Ontology represents biology in a way that is useful for gene product annotation of reference genomes and other MODs using the GO for annotation. The group serves as the link between biological knowledge that is gained from wet-bench scientists and the representation of that knowledge in the GO. Members of the group are responsible for reporting areas of the GO that need development and for suggesting changes and additions to the GO as needs arise. Members of the group serve as biological experts in domains that are covered by their organism. They are responsible for reviewing changes to be sure that they accurately reflect our current understanding of biology. With the help of the software team the group create rules to ensure the ontology's integrity.

Group Leader

David Hill (MGI); GitHub: @ukemi


Editor's Conference calls


  • Calls are held weekly on Mondays, 12:00PM-1:00PM EST
  • Calls are scheduled on the GO's Google calendar. Please request access to the calendar if you don't have it.
  • Reminder emails are sent out to the go-ontology mailing list (see Internal_email_lists to register).

Agenda and Minutes


Setting up Protege for GO editors

Installing and Using git

Ontology Editors Daily Workflow

Editing the Ontology

General Gene Ontology Principles
New terms
Principles for creating a GO term (being reviewed) Guidelines for creating a GO term
Guidelines for creating relationships between terms (being reviewed)
Guidelines for creating disjoint terms (to be written)
Guidelines for creating a Regulation Term
Guidelines for GO textual definitions (being reviewed)
Guidelines for equivalence axioms (being reviewed) --- Also Logical_Definitions (being reviewed)
Guidelines for new Molecular Functions (new)
Guidelines for new Biological Processes (new)
Guidelines for new Cellular Components (new)
Modifying existing terms
Principles for Modifying an Existing Ontology Term (to be reviewed) Deleting Asserted Subclasses
Adding Term Comments
Adding a Term to a GO Subset (Slim)
Adding Taxon Restrictions
Term obsoletion
Principles for term obsoletion Obsoleting an Existing Ontology Term
Restoring an Obsolete Ontology Term
Term merges
Principles for merging terms (being reviewed) Merging Ontology Terms
Subset documentation (to add) Adding and Removing GO Subsets (Slims)
Import Files
Principles for GO import files Adding Terms and Regenerating the Import Files

Relations General Relations Documentation Draft To be reviewed

Website - to be moved to the wiki?

Identifiers To be reviewed

Guidance for organizing content meetings

(old doc, but basic principles still apply)

Content Development

Ongoing Projects

Low priority

Completed projects

Proposed content work

A list of topics that we propose to address, but for which a timeline has not been set

Quality Control

SPARQL checks on the ontology

SPARQL checks on the ontology

Ontology release pipeline