HL7 Terminology (THO)
6.0.0 - Publication
This page is part of the HL7 Terminology (v6.0.0: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Active as of 2023-12-11 |
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="SO"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem SO</b></p><a name="SO"> </a><a name="hcSO"> </a><a name="SO-en-US"> </a><p>This case-sensitive code system <code>http://www.sequenceontology.org</code> defines codes, but no codes are represented here</p></div>
</text>
<url value="http://www.sequenceontology.org"/>
<version value="1.0.0"/>
<name value="SO"/>
<title value="Sequence Ontology"/>
<status value="active"/>
<experimental value="false"/>
<date value="2023-12-11T00:00:00-00:00"/>
<publisher value="Sequence Ontology"/>
<contact>
<name
value="Sequence Ontology; Karen Eilbeck (PI), Barry Moore (Software Developer), Shawn Rynearson (Software Developer)"/>
<telecom>
<system value="url"/>
<value value="http://www.sequenceontology.org"/>
</telecom>
<telecom>
<system value="email"/>
<value value="keilbeck@genetics.utah.edu"/>
</telecom>
<telecom>
<system value="email"/>
<value value="barry.moore@genetics.utah.edu"/>
</telecom>
<telecom>
<system value="email"/>
<value value="shawn.rynearson@gmail.com"/>
</telecom>
</contact>
<description
value=""The Sequence Ontology is a set of terms and relationships used to describe the features and attributes of biological sequence. SO includes different kinds of features which can be located on the sequence. Biological features are those which are defined by their disposition to be involved in a biological process."
"The Sequence Ontologies are provided as a resource to the biological community. They have the following obvious uses:
* To provide for a structured controlled vocabulary for the description of primary annotations of nucleic acid sequence, e.g. the annotations shared by a DAS server ([BioDAS](http://www.biodas.org/documents/das2/das2_protocol.html), [Biosapiens DAS](http://www.biosapiens.info/page.php?page=das_portal)), or annotations encoded by [GFF3](http://www.sequenceontology.org/gff3.shtml)."
* To provide for a structured representation of these annotations within databases. Were genes within model organism databases to be annotated with these terms then it would be possible to query all these databases for, for example, all genes whose transcripts are edited, or trans-spliced, or are bound by a particular protein. One such genomic database is [Chado](http://www.gmod.org/wiki/Chado).
* To provide a structured controlled vocabulary for the description of mutations at both the sequence and more gross level in the context of genomic databases."
"The Sequence Ontology is part of [OBO](http://www.obofoundry.org/). It has close links to other ontology projects such as the [RNAO consortium](http://roc.bgsu.edu/), and the [Biosapiens polypeptide features](http://www.ebi.ac.uk/ontology-lookup/browse.do?ontName=BS)."
The content can be browsed [here](http://www.sequenceontology.org/browser/obob.cgi)
The content can be downloaded [here](https://github.com/The-Sequence-Ontology/SO-Ontologies)
For information on contributing, please see [here](https://github.com/The-Sequence-Ontology/SO-Ontologies#contributing)
To request a term or register feedback, see [here](https://github.com/The-Sequence-Ontology/SO-Ontologies/issues)"/>
<copyright
value="The Sequence Ontology: A tool for the unification of genome annotations. Eilbeck K., Lewis S.E., Mungall C.J., Yandell M., Stein L., Durbin R., Ashburner M. [Genome Biology (2005) 6:R44](http://genomebiology.com/2005/6/5/R44)
Please also include the version of SO used.
Sequence Ontology data and data products are licensed under the [Creative Commons Attribution 4.0 Unported License](https://creativecommons.org/licenses/by/4.0/legalcode)."/>
<caseSensitive value="true"/>
<content value="not-present"/>
</CodeSystem>