Function

OBI Function Branch Home
This page provides general information on OBI Function branch activities and links to related OBI Function branch pages including term lists, TCon agendas/minutes, and Use Case analysis.

<<Back to Homepage

1. Editors

 * Bill
 * Alan
 * Suzi & GO (advisor)

2. Function Branch TCons:

 * conference call agendas |
 * conference call minutes |

3. Link to OBI Function terms' list |
(Find here a list of excel files, as the works progress)

4. Original list of terms - as provided by each community
(Dear editors, add here the link to the file with your list of terms here)  Tab delimited file with terms from flow cytometry: Upload:Function-FlowCytometry-2007-03-30.txt
 * Flow Cytometry

5. General Guidelines
Communities are compiling lists of their ~Function term requirements (preferably following the naming conventions2|) as a tab-delimited file (term name and definition) - all needed terms if time permits. Examples below provide general guidance on how Function term defintions should be specified. As this branch is built out, a term's parent class should also be specified. Currently only a parent obi:function class, a placeholder for GO:Molecularfunction, and OBI:Instrumentfunction exist. As the examples below make clear, we will also likely have foundational function classes for:
 * Assay_function
 * Assessmentfunction (likely a specialization of Assayfunction)
 * Indicator_function (e.g., fluorophores, radiolabels, optically dense indicators such as HRP & DAB/Ni)
 * Reagent_function
 * Algorithm_function
 * Instrumentpartfunction (not really a type of Instrument_function)
 * Analyticalinstrumentfunction (according to Instrument Branch discussions, devices such as dialysis tubing that do not produce data will be considered a type of Instrument. The collection of Instruments that directly produce the observations collected for analysis colloquially referred to as "data" will be sub-types of Analytical_instrument)

As the BFO:function definition makes clear, functions are end-directed activities manifested by specific continuants. Functions typically provide a description of how a variety of continuants inter-relate in a particular context. With this in mind, it is expected definitions submitted for particular functions will include a reference to the continuant exhibiting it, as well as other continuants and occurents involved in the function. Necessary additional continuants and occurents, if not internal to OBI, should be derived from existing ontologies when possible, preferably one amongst the [OBO Foundry] constellation of ontologies.

The Function branch editors will be responsible for communicating to other branch editors a continuant residing in the branch they curate is linked to a specific function.

Finally, the Functions to be covered by OBI will be those specifically related to investigational details such as executing a protocol, performing an assay, or using an instrument.