2010 GO camp Meeting Logistics

From GO Wiki
Revision as of 11:28, 22 February 2010 by Slaulederkind (talk | contribs) (5. process beginning/end (maybe in the context of the new signaling terms))

Jump to: navigation, search


The 3rd GO annotation camp (3 days) will be held from June 16-18, 2010 (Wednesday-Friday).


This annotation camp will be focused on updating and refining skills of existing GO biocurators including new GO biocurators in existing annotation groups and including the Swiss-Prot curation team. We hope members of each MOD will be represented.

  • Deliverables: (1) final annotation documentation for each of the three annotation topics.
    • There will be a special emphasis on the reference genome project. Deliverable: (2) annotation propagation rules for the reference genome project.


Swiss Institute for Bioinformatics (SIB), Geneva, Switzerland.


Not yet open.

Lodging Information

To be announced.


To be announced.


Structure: There will be three (3) ‘focused annotation sessions’ where specific annotation issues will be discussed. Suggestion for discussion topics should be added to the GO camp agenda: 2010_GO_camp_Meeting_Logistics#Suggestions_for_annotation_issues_to_be_discussed

The agenda is not yet finalized.

Suggestions for annotation issues to be discussed

  • Please add any concerns you have regarding specific GO annotation issues here, or add your comments to an existing annotation issue.
  • As three topics will be selected for further discussion for the GO camp, please indicate which 3 issues are of most interest to you.

1. Binding (binding working group would like to finalize the annotation documentation)

Notes: The binding group presented annotation policy suggestions at the last GO Consortium meeting [1] These annotation guidelines should be finalized, and a full set of annotation guidelines on how annotation data is curated and presented in GAF files should be fully documented. For instance determine:

  • that binding annotations, especially those where the GO term does not specify a particular binding partner, should where possible, indicate the interacting partner in the 'with' column
  • fully describe the usage of pipes etc in the 'with' column.
  • ask that protein binding annotations should be reciprocal - that if protein A is annotated as binding protein B, the reverse annotation should be provided

The use of column 16 to identify protein/gene targets of an molecular function GO annotation, could benefit this binding discussion.

Curators interested in discussing this topic at the GO Camp:


2.annotation of complexes

  1. Can IPI be used to annotate molecular function? For example ribosomal subunits are annotated to 'structural constituent of ribosome' (a function)
  2. 'Structural components activity' function terms: some ribosome proteins are annotated to 'structural constituent of ribosome' by IDA (for example SGD:S000005760); but the paper (PMID: 18782943) only shows purification of the complex.
  3. Chromatin? See NIPBL discussion from Feb 22 jamboree. The general question is when is a protein part of a complex or organelle or when it binds to it?

Curators interested in discussing this topic at the GO Camp: Pascale, Stan

3. use of regulation

Notes: How do groups decide on when to annotate to 'regulates process x' or 'process x'? For instance does SLIT regulate axon guidance or involved in the process of axon guidance? Val - this depends on the defined start/end of a process and somethings can be annotated to BOTH the regulates term and also directly to the process term. Some groups decide that if removing the activity of a gene product produces an all/nothing event - then they define it as being part of the process. When should annotations be inherited up the regulates relationship?

Curators interested in discussing this topic at the GO Camp


4. use of column 16

Notes: The suggested use of Cell Type in column 16 seems to be progressing [2], and a date for GAF2.0 has been agreed for the 1st June. However this discussion needs to progress to decide how targets of a molecular function/biological process should be best captured in this field, as well as the linking of terms between different annotation lines.

Curators interested in discussing this topic at the GO Camp: Stan

5. process beginning/end (maybe in the context of the new signaling terms)

Notes:Annotations could be checked more efficiently if GO term definitions could include the beginning and end of a process.

Curators interested in discussing this topic at the GO Camp: Stan

6. response to terms, how will these relate to signaling terms and to final cellular effect

Curators interested in discussing this topic at the GO Camp

7. How is a downstream effect defined (i.e when not to capture phenotypes )

Curators interested in discussing this topic at the GO Camp

Other suggestions for agenda items

  1. What is the bottle neck for manual annotations (with experimental evidence)? How can we step up manual curation? (Rama)
  2. How are the various annotating groups keeping with all the ontology development/changes (new relationships specifically)? (Rama)


Name Organization Arrival Date/Time to Airport Departure Date/Time from Airport

Remote Attendees

We will try to provide Webex and Telephone Conferencing.

Name Organization email (needed to set up your remote access)

Return to Consortium_Meetings page