{"id":21,"date":"2022-06-20T11:33:55","date_gmt":"2022-06-20T10:33:55","guid":{"rendered":"https:\/\/insdc.org\/?page_id=21"},"modified":"2024-05-10T17:03:52","modified_gmt":"2024-05-10T16:03:52","slug":"feature-table","status":"publish","type":"page","link":"https:\/\/www.insdc.org\/submitting-standards\/feature-table\/","title":{"rendered":"The DDBJ\/ENA\/GenBank Feature Table Definition"},"content":{"rendered":"\n<pre class=\"wp-block-preformatted\">The DDBJ\/ENA\/GenBank \nFeature Table\nDefinition\nVersion 11.2 February 2024\n\n\nDNA Data Bank of Japan, Mishima, Japan.\nEMBL-EBI, European Nucleotide Archive, Cambridge, UK.\nGenBank, NCBI, Bethesda, MD, USA.\n\n\n<a href=\"#1\">1 Introduction<\/a>\n<a href=\"#2\">2 Overview of the Feature Table format<\/a>\n<a href=\"#2.1\">2.1 Format Design<\/a>\n<a href=\"#2.2\">2.2 Key aspects of this feature table design<\/a>\n<a href=\"#2.3\">2.3 Feature Table Terminology<\/a>\n<a href=\"#3\">3 Feature table components and format<\/a>\n<a href=\"#3.1\">3.1 Naming conventions<\/a>\n<a href=\"#3.2\">3.2 Feature keys<\/a>\n<a href=\"#3.2.1\">3.2.1 Purpose<\/a>\n<a href=\"#3.2.2\">3.2.2 Format and conventions<\/a>\n<a href=\"#3.2.3\">3.2.3 Key groups and hierarchy<\/a>\n<a href=\"#3.2.4\">3.2.4 Feature key examples<\/a>\n<a href=\"#3.3\">3.3 Qualifiers<\/a>\n<a href=\"#3.3.1\">3.3.1 Purpose<\/a>\n<a href=\"#3.3.2\">3.3.2 Format and conventions<\/a>\n<a href=\"#3.3.3\">3.3.3 Qualifier values<\/a>\n<a href=\"#3.3.4\">3.3.4 Qualifier examples<\/a>\n<a href=\"#3.4\">3.4 Location<\/a>\n<a href=\"#3.4.1\">3.4.1 Purpose<\/a>\n<a href=\"#3.4.2\">3.4.2 Format and conventions<\/a>\n<a href=\"#3.4.3\">3.4.3 Location examples<\/a>\n<a href=\"#4\">4 Feature table Format<\/a>\n<a href=\"#4.1\">4.1 Format examples<\/a>\n<a href=\"#4.2\">4.2 Definition of line types<\/a>\n<a href=\"#4.3\">4.3 Data item positions<\/a>\n<a href=\"#4.4\">4.4 Use of blanks<\/a>\n<a href=\"#5\">5 Examples of sequence annotation<\/a>\n<a href=\"#5.1\">5.1 Eukaryotic gene<\/a>\n<a href=\"#5.2\">5.2 Bacterial operon<\/a>\n<a href=\"#5.3\">5.3 Artificial cloning vector (circular)<\/a>\n<a href=\"#5.4\">5.4 Plasmid<\/a>\n<a href=\"#5.5\">5.5 Repeat element<\/a>\n<a href=\"#5.6\">5.6 Immunoglobulin heavy chain<\/a>\n<a href=\"#5.7\">5.7 T-cell receptor<\/a>\n<a href=\"#5.8\">5.8 Transfer RNA<\/a>\n<a href=\"#6\">6 Limitations of this feature table design<\/a>\n<a href=\"#7\">7 Appendices<\/a>\n<a href=\"#7.1\">7.1 Appendix I EMBL, GenBank and DDBJ entries<\/a>\n<a href=\"#7.1.1\">7.1.1 EMBL Format<\/a>\n<a href=\"#7.1.2\">7.1.2 GenBank Format<\/a>\n<a href=\"#7.1.3\">7.1.3 DDBJ Format<\/a>\n<a href=\"#7.2\">7.2 Appendix II: Feature keys reference<\/a>\n<a href=\"#7.3\">7.3 Appendix III: Summary of qualifiers for feature keys<\/a>\n<a href=\"#7.3.1\">7.3.1 Qualifier List<\/a>\n<a href=\"#7.4\">7.4 Appendix IV: Controlled vocabularies<\/a>\n<a href=\"#7.4.1\">7.4.1 Nucleotide base codes (IUPAC)<\/a>\n<a href=\"#7.4.2\">7.4.2 Modified base abbreviations<\/a>\n<a href=\"#7.4.3\">7.4.3 Amino acid abbreviations<\/a>\n<a href=\"#7.4.4\">7.4.4 Modified and unusual Amino Acids<\/a>\n<a href=\"#7.4.5\">7.4.5 Genetic Code Tables<\/a>\n<a href=\"#7.4.6\">7.4.6 Country Names<\/a>\n<a href=\"#7.4.7\">7.4.7 Announces<\/a>\n\n\n\n<a name=\"1\"><\/a><\/pre>\n\n\n\n<h1 class=\"wp-block-heading\">1 Introduction<\/h1>\n\n\n\n<pre class=\"wp-block-preformatted\">Nucleic acid sequences provide the fundamental starting point for describing \nand understanding the structure, function, and development of genetically \ndiverse organisms. The GenBank, EMBL, and DDBJ nucleic acid sequence data \nbanks have from their inception used tables of sites and features to describe \nthe roles and locations of higher order sequence domains and elements within \nthe genome of an organism. \nIn February, 1986, GenBank and EMBL began a collaborative effort (joined by \nDDBJ in 1987) to devise a common feature table format and common standards for \nannotation practice. \n\n<a name=\"2\"><\/a><\/pre>\n\n\n\n<h1 class=\"wp-block-heading\">2 Overview of the Feature Table format<\/h1>\n\n\n\n<pre class=\"wp-block-preformatted\">The overall goal of the feature table design is to provide an extensive \nvocabulary for describing features in a flexible framework for manipulating \nthem. The Feature Table documentation represents the shared rules that allow \nthe three databases to exchange data on a daily basis. \nThe range of features to be represented is diverse, including regions which: \n* perform a biological function, \n* affect or are the result of the expression of a biological function, \n* interact with other molecules, \n* affect replication of a sequence, \n* affect or are the result of recombination of different sequences, \n* are a recognizable repeated unit, \n* have secondary or tertiary structure,\n* exhibit variation, or have been revised or corrected.\n\n\n<a name=\"2.1\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">2.1 Format Design<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\"> \nThe format design is based on a tabular approach and consists of the following \nitems: \n\nFeature key - a single word or abbreviation indicating functional group \nLocation - instructions for finding the feature \nQualifiers - auxiliary information about a feature \n \n\n<a name=\"2.2\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">2.2 Key aspects of this feature table design<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">* Feature keys allow specific annotation of important sequence features.\n\n* Related features can be easily specified and retrieved.\nFeature keys are arranged hierarchically, allowing complex and compound \nfeatures to be expressed. Both location operators and the feature keys show \nfeature relationships even when the features are not contiguous. The hierarchy \nof feature keys allows broad categories of biological functionality, such as \nrRNAs, to be easily retrieved.\n\n* Generic feature keys provide a means for entering new or undefined features.\nA number of \"generic\" or miscellaneous feature keys have been added to permit \nannotation of features that cannot be adequately described by existing feature \nkeys. These generic feature keys will serve as an intermediate step in the \nidentification and addition of new feature keys. The syntax has been designed \nto allow the addition of new feature keys as they are required. \n\n* More complex locations (fuzzy and alternate ends, for example) can be specified.\nEach end point of a feature may be specified as a single point, an alternate \nset of possible end points, a base number beyond which the end point lies, or \na region which contains the end point. \n\n* Features can be combined and manipulated in many different ways.\nThe location field can contain operators or functional descriptors specifying \nwhat must be done to the sequence to reproduce the feature. For example, a \nseries of exons may be \"join\"ed into a full coding sequence. \n\n* Standardized qualifiers provide precision and parsibility of descriptive details \nA combination of standardized qualifiers and their controlled-vocabulary \nvalues enable free-text descriptions to be avoided.\n \n* The nature of supporting evidence for a feature can be explicitly indicated.\nFeatures, such as open reading frames or sequences showing sequence similarity \nto consensus sequences, for which there is no direct experimental evidence can \nbe annotated. Therefore, the feature table can incorporate contributions from \nresearchers doing computational analysis of the sequence databases. However, \nall features that are supported by experimental data will be clearly marked as \nsuch. \n\n* The table syntax has been designed to be machine parsible.\nA consistent syntax allows machine extraction and manipulation of sequences \ncoding for all features in the table.\n \n<a name=\"2.3\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">2.3 Feature Table Terminology<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">The format and wording in the feature table use common biological research \nterminology whenever possible. For example, an item in the feature table such as: \n\nKey Location\/Qualifiers\nCDS 23..400\n \/product=\"alcohol dehydrogenase\" \n \/gene=\"adhI\"\n \nmight be read as: \nThe feature CDS is a coding sequence beginning at base 23 and ending at base \n400, has a product called 'alcohol dehydrogenase' and is coded for by a gene \ncalled \"adhI\".\n\nA more complex description:\nKey Location\/Qualifiers\nCDS join(544..589,688..>1032)\n \/product=\"T-cell receptor beta-chain\"\n\nwhich might be read as: \nThis feature, which is a partial coding sequence, is formed by joining \nelements indicated to form one contiguous sequence encoding a product called T-\ncell receptor beta-chain. \n\nThe following sections contain detailed explanations of the feature table \ndesign showing conventions for each component of the feature table, examples \nof how the format might be implemented, a description of the exact column \nplacement of all the data items and examples of complete sequence entries that \nhave been annotated using the new format. The last section of this document \ndescribes known limitations of the current feature table design. \n\nAppendix I gives an example database entry for the DDBJ, GenBank and EMBL \nformats. \n\nAppendices II and III provide reference manuals for the feature table keys and \nqualifiers, respectively. \n\nAppendix IV includes controlled vocabularies such as nucleotide base codes, \nmodified base abbreviations, genetic code tables etc.\n\nThis document defines the syntax and vocabulary of the feature table. The \nsyntax is sufficiently flexible to allow expression of a single biological \nentity in numerous ways. In such cases, the annotation staffs at the databases \nwill propose conventions for standard means of denoting the entities. \nThis feature table format is shared by GenBank, EMBL and DDBJ. Comments, \ncorrections, and suggestions may be submitted to any of the database staffs. \nNew format specifications will be added as needed. \n \n<a name=\"3\"><\/a><\/pre>\n\n\n\n<h1 class=\"wp-block-heading\">3 Feature table components and format<\/h1>\n\n\n\n<pre class=\"wp-block-preformatted\"><a name=\"3.1\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3.1 Naming conventions<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Feature table components, including feature keys, qualifiers, accession \nnumbers, database name abbreviations, and location operators, are all named \nfollowing the same conventions. Component names may be no more than 20 \ncharacters long (Feature keys 15, Feature qualifiers 20) and must \ncontain at least one letter. The following characters are permitted to \noccur in feature table component names: \n\n* Uppercase letters (A-Z) \n* Lowercase letters (a-z) Numbers (0-9) \n* Underscore (_) \n* Hyphen (-) \n* Single quotation mark or apostrophe (') \n* Asterisk (*) \n\n\n<a name=\"3.2\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3.2 Feature keys<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\"><a name=\"3.2.1\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3.2.1 Purpose<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Feature keys indicate \n(1) the biological nature of the annotated feature or \n(2) information about changes to or other versions of the sequence. \nThe feature key permits a user to quickly find or retrieve similar features or \nfeatures with related functions. \n\n<a name=\"3.2.2\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3.2.2 Format and conventions<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">There is a defined list of allowable feature keys, which is shown in Appendix \nII. Each feature must contain a feature key. \n \n<a name=\"3.2.3\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3.2.3 Key groups and hierarchy<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">The feature keys fall into families which are in some sense similar in \nfunction and which are annotated in a similar manner. A functional family may \nhave a \"generic\" or miscellaneous key, which can be recognized by the 'misc.' \nprefix, that can used for instances not covered by the other defined keys of \nthat group. \n\nThe feature key groups are listed below with a short definition and an \nannotation example: \n\n1. Difference and change features\n\nIndicate ways in which a sequence should be changed to produce a different \n\"version\": \nmisc_difference location\n \/replace=\"change_location\"\n\n2. Transcript features\n\nIndicate products made by a region: \nmisc_RNA location\n\n\n3. Binding features\n\nIndicate that a sequence or nucleotide is covalently, non-covalently, or \notherwise bound to something else: \nmisc_binding location\n \/bound_moiety=\"bound molecule\" \n\n4. Repeat features\n\nIndicate repetitive sequence elements: \nrepeat_region location\n\n\n5. Recombination features\n\nIndicate regions that have been either inserted or deleted by recombination: \nmisc_recomb location\n\n\n6. Structure features\n\nIndicate sequence for which there is secondary or tertiary structural \ninformation: \nmisc_structure location\n\n<a name=\"3.2.4\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3.2.4 Feature key examples<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Key Description \n\nCDS Protein-coding sequence \nrep_origin Origin of replication\nprotein_bind Protein binding site on DNA\ntRNA mature transfer RNA\n\nSee Appendix II for descriptions of all feature keys. \n\n<a name=\"3.3\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3.3 Qualifiers<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\"><a name=\"3.3.1\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3.3.1 Purpose<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Qualifiers provide a general mechanism for supplying information about \nfeatures in addition to that conveyed by the key and location. \n\n<a name=\"3.3.2\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3.3.2 Format and conventions<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Qualifiers take the form of a slash (\/) followed by the qualifier name and, if \napplicable, an equal sign (=) and a value. Each qualifier should have a single \nvalue; if multiple values are necessary, these should be represented by \niterating the same qualifier, eg: \nKey Location\/Qualifiers\n\nsource 1..1000\n \/culture_collection=\"ATCC:11775\"\n \/culture_collection=\"CECT:515\"\n\nIf the location descriptor does not need a continuation line, the first \nqualifier begins a new line in the feature location column. If the location \ndescriptor requires a continuation line, the first qualifier may follow \nimmediately after the location. Any necessary continuation lines begin in the \nsame column. See Section 4 for a complete description of data item positions. \n \n\n<a name=\"3.3.3\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3.3.3 Qualifier values<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Since qualifiers convey many different types of information, there are several value formats: \n1. Free text \n2. Controlled vocabulary or enumerated values \n3. Citation or reference numbers \n4. Sequences<\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">3.3.3.1 Free text<\/h4>\n\n\n\n<pre class=\"wp-block-preformatted\">Most qualifier values will be a descriptive text phrase which must be enclosed \nin double quotation marks. When the text occupies more than one line, a single \nset of quotation marks is required at the beginning and at the end of the \ntext. The text itself may be composed of any printable characters (ASCII \nvalues 32-126 decimal). If double quotation marks are used within a free text \nstring, each set (\") must be 'escaped' by placing a second double quotation \nmark immediately before it (\"\"). For example: \n \/note=\"This is an example of \"\"escaped\"\" quotation marks\"<\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">3.3.3.2 Controlled vocabulary or enumerated values<\/h4>\n\n\n\n<pre class=\"wp-block-preformatted\">Some qualifiers require values from a controlled vocabulary and are entered \nwithout quotation marks. For example, the '\/direction' qualifier has only \nthree values: 'left', 'right' or 'both'. Qualifier value controlled \nvocabularies, like feature table component names, must be treated as \ncompletely case insensitive: they may be entered and displayed in any \ncombination of upper and lower case ('\/direction=Left' '\/direction=left' and '\/\ndirection=LEFT' are all legal and all convey the same meaning). The database \nstaffs reserve the right to regularize the case of qualifier values. Qualifier \nvalue controlled vocabularies will be maintained by the cooperating database \nstaffs. Examples of controlled vocabularies can be found in Appendices IV and \nV. The database staff should be contacted for the current lists.<\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">3.3.3.3 Citation or reference numbers<\/h4>\n\n\n\n<pre class=\"wp-block-preformatted\">The citation or published reference number (as enumerated in the entry \n'REFERENCE' or 'RN' data item) should be enclosed in square brackets \n(e.g., [3]) to distinguish it from other numbers.<\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">3.3.3.4 Sequences<\/h4>\n\n\n\n<pre class=\"wp-block-preformatted\">Literal sequence of nucleotide bases e.g., join(12..45,\"atgcatt\",988..1050) in \nlocation descriptors has become illegal starting from implementation of \nversion 2.1 of the Feature Table Definition Document (December 15, 1998) \n\n<a name=\"3.3.4\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3.3.4 Qualifier examples<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Key Location\/Qualifiers\n\nsource 1..1509\n \/organism=\"Mus musculus\"\n \/strain=\"CD1\"\n \/mol_type=\"genomic DNA\"\nregulatory <1..9\n \/gene=\"ubc42\"\n \/regulatory_class=\"promoter\"\nmRNA join(10..567,789..1320)\n \/gene=\"ubc42\"\nCDS join(54..567,789..1254)\n \/gene=\"ubc42\"\n \/product=\"ubiquitin conjugating enzyme\"\n \/function=\"cell division control\"\n\n\n<a name=\"3.4\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3.4 Location<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\"><a name=\"3.4.1\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3.4.1 Purpose<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">The location indicates the region of the presented sequence which corresponds \nto a feature. \n\n<a name=\"3.4.2\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3.4.2 Format and conventions<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">The location contains at least one sequence location descriptor and may \ncontain one or more operators with one or more sequence location descriptors. \nBase numbers refer to the numbering in the entry. This numbering designates \nthe first base (5' end) of the presented sequence as base 1. \nBase locations beyond the range of the presented sequence may not be used in \nlocation descriptors, the only exception being location in a remote entry (see \n3.4.2.1, e). \n\nLocation operators and descriptors are discussed in more detail below.<\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">3.4.2.1 Location descriptors<\/h4>\n\n\n\n<pre class=\"wp-block-preformatted\">The location descriptor can be one of the following: \n(a) a single base number\n(b) a site between two indicated adjoining bases\n(c) a single base chosen from within a specified range of bases (not allowed for new\n entries)\n(d) the base numbers delimiting a sequence span\n(e) a remote entry identifier followed by a local location descriptor\n (i.e., a-d)\n\nA site between two adjoining nucleotides, such as endonucleolytic cleavage \nsite, is indicated by listing the two points separated by a carat (^). The \npermitted formats for this descriptor are n^n+1 (for example 55^56), or, for \ncircular molecules, n^1, where \"n\" is the full length of the molecule, ie \n1000^1 for circular molecule with length 1000.\n\nA single base chosen from a range of bases is indicated by the first base \nnumber and the last base number of the range separated by a single period \n(e.g., '12.21' indicates a single base taken from between the indicated \npoints). From October 2006 the usage of this descriptor is restricted : \nit is illegal to use \"a single base from a range\" (c) either on its own or \nin combination with the \"sequence span\" (d) descriptor for newly created entries. \nThe existing entries where such descriptors exist are going to be retrofitted. \n\nSequence spans are indicated by the starting base number and the ending base \nnumber separated by two periods (e.g., '34..456'). The '<' and '>' symbols may \nbe used with the starting and ending base numbers to indicate that an end \npoint is beyond the specified base number. The starting and ending base \npositions can be represented as distinct base numbers ('34..456') or a site \nbetween two indicated adjoining bases. \n\nA location in a remote entry (not the entry to which the feature table \nbelongs) can be specified by giving the accession-number and sequence version \nof the remote entry, followed by a colon \":\", followed by a location \ndescriptor which applies to that entry's sequence (i.e. J12345.1:1..15, see \nalso examples below)<\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">3.4.2.2 Operators<\/h4>\n\n\n\n<pre class=\"wp-block-preformatted\">The location operator is a prefix that specifies what must be done to the \nindicated sequence to find or construct the location corresponding to the \nfeature. A list of operators is given below with their definitions and most \ncommon format. \n\ncomplement(location) \nFind the complement of the presented sequence in the span specified by \"\nlocation\" (i.e., read the complement of the presented strand in its 5'-to-3' \ndirection) \n\njoin(location,location, ... location) \nThe indicated elements should be joined (placed end-to-end) to form one \ncontiguous sequence \n\norder(location,location, ... location) \nThe elements can be found in the \nspecified order (5' to 3' direction), but nothing is implied about the \nreasonableness about joining them \n\nNote : location operator \"complement\" can be used in combination with either \"\njoin\" or \"order\" within the same location; combinations of \"join\" and \"order\" \nwithin the same location (nested operators) are illegal.\n\n\n\n<a name=\"3.4.3\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3.4.3 Location examples<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">The following is a list of common location descriptors with their meanings: \n\nLocation Description \n\n467 Points to a single base in the presented sequence \n\n340..565 Points to a continuous range of bases bounded by and\n including the starting and ending bases\n\n<345..500 Indicates that the exact lower boundary point of a feature\n is unknown. The location begins at some base previous to\n the first base specified (which need not be contained in \n the presented sequence) and continues to and includes the \n ending base \n\n<1..888 The feature starts before the first sequenced base and \n continues to and includes base 888\n\n1..>888 The feature starts at the first sequenced base and \n continues beyond base 888\n\n102.110 Indicates that the exact location is unknown but that it is \n one of the bases between bases 102 and 110, inclusive\n\n123^124 Points to a site between bases 123 and 124\n\njoin(12..78,134..202) Regions 12 to 78 and 134 to 202 should be joined to form \n one contiguous sequence\n\n\ncomplement(34..126) Start at the base complementary to 126 and finish at the \n base complementary to base 34 (the feature is on the strand \n complementary to the presented strand)\n\n\ncomplement(join(2691..4571,4918..5163))\n Joins regions 2691 to 4571 and 4918 to 5163, then \n complements the joined segments (the feature is on the \n strand complementary to the presented strand) \n\njoin(complement(4918..5163),complement(2691..4571))\n Complements regions 4918 to 5163 and 2691 to 4571, then \n joins the complemented segments (the feature is on the \n strand complementary to the presented strand)\n \nJ00194.1:100..202 Points to bases 100 to 202, inclusive, in the entry (in \n this database) with primary accession number 'J00194'\n \njoin(1..100,J00194.1:100..202)\n Joins region 1..100 of the existing entry with the region\n 100..202 of remote entry J00194\n\n\n<a name=\"4\"><\/a><\/pre>\n\n\n\n<h1 class=\"wp-block-heading\">4 Feature table Format<\/h1>\n\n\n\n<pre class=\"wp-block-preformatted\">The examples below show the preferred sequence annotations for a number of \ncommonly occurring sequence types. These examples may not be appropriate in \nall cases but should be used as a guide whenever possible. This section \ndescribes the columnar format used to write this feature table in \"flat-file\" \nform for distributions of the database. \n\n<a name=\"4.1\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">4.1 Format examples<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Feature table format example (EMBL): \nFT source 1..1859\nFT \/db_xref=\"taxon:3899\"\nFT \/organism=\"Trifolium repens\"\nFT \/tissue_type=\"leaves\"\nFT \/clone_lib=\"lambda gt10\"\nFT \/clone=\"TRE361\"\nFT \/mol_type=\"genomic DNA\"\nFT CDS 14..1495\nFT \/db_xref=\"MENDEL:11000\"\nFT \/db_xref=\"UniProtKB\/Swiss-Prot:P26204\"\nFT \/note=\"non-cyanogenic\"\nFT \/EC_number=\"3.2.1.21\"\nFT \/product=\"beta-glucosidase\"\nFT \/protein_id=\"CAA40058.1\"\nFT \/translation=\"MDFIVAIFALFVISSFTITSTNAVEASTLLDIGNLSR.......\n---------+---------+---------+---------+---------+---------+---------+---------\n1 10 20 30 40 50 60 70 79\n\nFeature table format example (GenBank):\n\n source 1..8959\n \/organism=\"Homo sapiens\"\n \/db_xref=\"taxon:9606\"\n \/mol_type=\"genomic DNA\"\n gene 212..8668\n \/gene=\"NF1\"\n CDS 212..8668\n \/gene=\"NF1\"\n \/note=\"putative\"\n \/codon_start=1\n \/product=\"GAP-related protein\"\n \/protein_id=\"AAA59924.1\"\n \/translation=\"MAAHRPVEWVQAVVSRFDEQLPIKTGQQNTHTKVSTE.......\n---------+---------+---------+---------+---------+---------+---------+---------\n1 10 20 30 40 50 60 70 79\n\nFeature table format example (DDBJ):\n\n \n source 1..2136\n \/clone=\"pK28\"\n \/organism=\"Rattus norvegicus\"\n \/strain=\"Sprague-Dawley\"\n \/tissue_type=\"kidney\"\n \/mol_type=\"genomic DNA\" \n mRNA 19..2128\n CDS 31..1212\n \/codon_start=1\n \/function=\"Dual specificity protein tyrosine\/threonine\n kinase\"\n \/product=\"MAP kinase kinase\"\n \/protein_id=\"BAA02603.1\"\n \/translation=\"MPKKKPTPIQLNPAPDGSAVNGTSSAETNLEALQKKL.......\n---------+---------+---------+---------+---------+---------+---------+---------\n1 10 20 30 40 50 60 70 79\n\n\n<a name=\"4.2\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">4.2 Definition of line types<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">The feature table consists of a header line, which contains the column titles \nfor the table, and the individual feature entries. Each feature entry is \ncomposed of a feature descriptor line and qualifier and continuation lines, \nif needed. The feature descriptor line contains the feature's name, key, and \nlocation. If the location cannot be contained on the first line of the feature \ndescriptor, it is continued on a continuation line immediately following the \ndescriptor line. If the feature requires further attributes, feature qualifier \nlines immediately follow the corresponding feature descriptor line (or its \ncontinuation). Qualifier information that cannot be contained on one line \ncontinues on the following continuation lines as necessary.\n \nThus, there are 4 types of feature table lines: \n Line type Content #\/entry #\/feature\n --------- ------- ------- ---------\n\n Header Column titles 1* N\/A\n Feature descriptor Key and location 1 to many* 1\n Feature qualifiers Qualifiers and values N\/A 0 to many\n Continuation lines Feature descriptor or 0 to many 0 to many\n qualifier continuation\n\n\n<a name=\"4.3\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">4.3 Data item positions<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">The position of the data items within the feature descriptor line is as follows: \n column position data item\n --------------- ---------\n\n 1-5 blank \n 6-20 feature key\n 21 blank\n 22-80 location\n\nData on the qualifier and continuation lines begins in column position 22 (the \nfirst 21 columns contain blanks). The EMBL format for all lines differs from \nthe GenBank \/ DDBJ formats that it includes a line type abbreviation in \ncolumns 1 and 2. \n\n<a name=\"4.4\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">4.4 Use of blanks<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Blanks (spaces) may, in general, be used within the feature location and \nqualifier values to make the construction more readable. The following rules \nshould be observed: \n* Names of feature table components may not contain blanks (see Section 3.1) \n* Operator names may not be separated from the following open parenthesis (the \n beginning of the operand list) by blanks. \n* Qualifiers may not be separated from the preceding slash or the following \n equals sign (if one) by blanks \n\n\n<a name=\"5\"><\/a><\/pre>\n\n\n\n<h1 class=\"wp-block-heading\">5 Examples of sequence annotation<\/h1>\n\n\n\n<pre class=\"wp-block-preformatted\">The examples below show the preferred sequence annotations for a number of \ncommonly occurring sequence types. These examples may not be appropriate in \nall cases but should be used as a guide whenever possible.\n\n<a name=\"5.1\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">5.1 Eukaryotic gene<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">source 1..1509\n \/organism=\"Mus musculus\"\n \/strain=\"CD1\"\n \/mol_type=\"genomic DNA\"\nregulatory <1..9\n \/gene=\"ubc42\"\n \/regulatory_class=\"promoter\"\nmRNA join(10..567,789..1320)\n \/gene=\"ubc42\"\nCDS join(54..567,789..1254)\n \/gene=\"ubc42\"\n \/product=\"ubiquitin conjugating enzyme\"\n \/function=\"cell division control\"\n \/translation=\"MVSSFLLAEYKNLIVNPSEHFKISVNEDNLTEGPPDTLY\n QKIDTVLLSVISLLNEPNPDSPANVDAAKSYRKYLYKEDLESYPMEKSLDECS\n AEDIEYFKNVPVNVLPVPSDDYEDEEMEDGTYILTYDDEDEEEDEEMDDE\"\nexon 10..567\n \/gene=\"ubc42\"\n \/number=1\nintron 568..788\n \/gene=\"ubc42\"\n \/number=1\nexon 789..1320\n \/gene=\"ubc42\"\n \/number=2\nregulatory 1310..1317\n \/regulatory_class=\"polyA_signal_sequence\"\n \/gene=\"ubc42\"\n\n\n\n \n<a name=\"5.2\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">5.2 Bacterial operon<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">source 1..9430\n \/organism=\"Lactococcus sp.\"\n \/strain=\"MG1234\"\n \/mol_type=\"genomic DNA\"\noperon 160..6865\n \/operon=\"gal\"\nregulatory 160..165\n \/operon=\"gal\"\n\t \/regulatory_class=\"minus_35_signal\"\nregulatory 179..184\n \/operon=\"gal\" \n \t\/regulatory_class=\"minus_10_signal\"\nCDS 405..1934\n \/operon=\"gal\"\n \/gene=\"galA\"\n \/product=\"galactose permease\"\n \/function=\"galactose transporter\"\nCDS 2003..3001\n \/operon=\"gal\"\n \/gene=\"galM\"\n \/product=\"aldose 1-epimerase\"\n \/EC_number=\"5.1.3.3\"\n \/function=\"mutarotase\"\nCDS 3235..4537\n \/operon=\"gal\"\n \/gene=\"galK\"\n \/product=\"galactokinase\"\n \/EC_number=\"2.7.1.6\"\nmRNA 189..6865\n \/operon=\"gal\"\n\n\n<a name=\"5.3\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">5.3 Artificial cloning vector (circular)<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">source 1..5300\n \/organism=\"Cloning vector pABC\"\n \/lab_host=\"Escherichia coli\"\n \/mol_type=\"other DNA\"\n \/focus\nsource 1..5138\n \/organism=\"Escherichia coli\"\n \/mol_type=\"other DNA\"\n \/strain=\"K12\"\nsource 5139..5247\n \/organism=\"Aequorea victoria\"\n \/mol_type=\"other DNA\"\n \/dev_stage=\"adult\"\nsource 5248..5300\n \/organism=\"Escherichia coli\"\n \/mol_type=\"other DNA\"\n \/strain=\"K12\"\nCDS join(complement(1..799),complement(5080..5120))\n \/gene=\"mob1\"\n \/product=\"mobilization protein 1\"\nCDS complement(1697..2512)\n \/gene=\"Km\"\n \/product=\"kanamycin resistance protein\"\nCDS 3037..3711\n \/gene=\"rep1\"\n \/product=\"replication protein 1\"\nCDS complement(4170..4829)\n \/gene=\"Cm\"\n \/product=\"chloramphenicol resistance protein\"\nCDS 5139..5247\n \/gene=\"GFP\"\n \/product=\"green fluorescent protein\" \n\n\n\n<a name=\"5.4 Plasmid\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">5.4 Plasmid<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">source 1..2245\n \/organism=\"Escherichia coli\"\n \/plasmid=\"Plasmid XYZ\"\n \/strain=\"K12\"\n \/mol_type=\"genomic DNA\"\nrep_origin 6\n \/direction=LEFT\n \/note=\"ori\"\nCDS complement(join(21..349,567..795))\n \/gene=\"trbC\"\n \/product=\"transfer protein C\"\nCDS 803..1344\n \/gene=\"traN\"\n \/product=\"transfer protein N\"\nCDS 1559..1985\n \/gene=\"incA\"\n \/product=\"incompatability protein A\"\nCDS join(2004..2195,3..20)\n \/gene=\"finP\"\n \/product=\"fertility inhibition protein P\"\n<a name=\"5.5\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">5.5 Repeat element<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">source 1..1011\n \/organism=\"Homo sapiens\"\n \/clone=\"pha281u\/1DO\"\n \/mol_type=\"genomic DNA\"\nrepeat_region 80..401\n \/rpt_type=DISPERSED\n \/rpt_family=\"Alu-J\"\n\n\n<a name=\"5.6\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">5.6 Immunoglobulin heavy chain<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">source 1..321\n \/organism=\"Mus musculus \"\n \/strain=\"BALB\/c2\n \/cell_line=\"hybridoma 1A4\"\n \/rearranged\n \/mol_type=\"mRNA\"\nCDS <1..>321\n \/codon_start=1\n \/gene=\"VFM1-DFL16.1-JH4\"\n \/product=\"immunoglobulin heavy chain\"\nV_region 1..277\n \/gene=\"VFM1\"\n \/product=\"immunoglobulin heavy chain variable region\" \n\n\n<a name=\"5.7\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">5.7 T-cell receptor<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">source 1..402\n \/organism=\"Homo sapiens\"\n \/sex=\"male\"\n \/cell_type=\"CD4+ T-lymphocyte\"\n \/rearranged\n \/clone=\"TCR1A.12\"\n \/mol_type=\"mRNA\"\nsig_peptide 1..54\n \/gene=\"TCR1A\"\nCDS 1..402\n \/gene=\"TCR1A\"\n \/product=\"T-cell receptor alpha chain\"\nmat_peptide 55..399\n \/gene=\"TCR1A\"\n \/product=\"T-cell receptor alpha chain\"\nV_region 55..327\n \/gene=\"TCR1A\"\nJ_segment 328..393\n \/gene=\"TCR1A\"\nC_region 394..399\n \/gene=\"TCR1A\" \n\n\n\n\n<a name=\"5.8\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">5.8 Transfer RNA<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">source 1..2345\n \/organism=\"Yersinia sp.\"\n \/strain=\"IP134\"\n \/mol_type=\"genomic DNA\"\nregulatory 644..650\n \/gene=\"tRNA-Leu(UUR)\"\n\t \/regulatory_class=\"minus_35_signal\"\ntRNA 655..730\n \/gene=\"tRNA-Leu(UUR)\"\n \/anticodon=(pos:678..680,aa:Leu,seq:taa)\n \/product=\"transfer RNA-Leu(UUR)\"\n \n<a name=\"6\"><\/a><\/pre>\n\n\n\n<h1 class=\"wp-block-heading\">6 Limitations of this feature table design<\/h1>\n\n\n\n<pre class=\"wp-block-preformatted\">During the development of the feature table design numerous choices between \nsimplicity and representational power had to be made. In order to create a \ndesign which was capable of representing the most common features of \nbiological significance, a certain degree of complexity in the syntax was \nguaranteed. However, to limit that level of complexity, certain limitations of \nthe design syntax have been accepted. \n \n<a name=\"7\"><\/a><\/pre>\n\n\n\n<h1 class=\"wp-block-heading\">7 Appendices<\/h1>\n\n\n\n<pre class=\"wp-block-preformatted\"><a name=\"7.1\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7.1 Appendix I EMBL, GenBank and DDBJ entries<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\"><a name=\"7.1.1\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7.1.1 EMBL Format<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">ID X64011; SV 1; linear; genomic DNA; STD; PRO; 756 BP.\nXX \nAC X64011; S78972;\nXX\nSV X64011.1\nXX\nDT 28-APR-1992 (Rel. 31, Created)\nDT 30-JUN-1993 (Rel. 36, Last updated, Version 6)\nXX\nDE Listeria ivanovii sod gene for superoxide dismutase\nXX\nKW sod gene; superoxide dismutase.\nXX\nOS Listeria ivanovii\nOC Bacteria; Firmicutes; Bacillus\/Clostridium group;\nOC Bacillus\/Staphylococcus group; Listeria.\nXX\nRN [1]\nRX MEDLINE; 92140371.\nRA Haas A., Goebel W.;\nRT \"Cloning of a superoxide dismutase gene from Listeria ivanovii by\nRT functional complementation in Escherichia coli and characterization of the\nRT gene product.\";\nRL Mol. Gen. Genet. 231:313-322(1992).\nXX\nRN [2]\nRP 1-756\nRA Kreft J.;\nRT ;\nRL Submitted (21-APR-1992) to the EMBL\/GenBank\/DDBJ databases.\nRL J. Kreft, Institut f. Mikrobiologie, Universitaet Wuerzburg, Biozentrum Am\nRL Hubland, 8700 Wuerzburg, FRG\nXX\nFH Key Location\/Qualifiers\nFH\nFT source 1..756\nFT \/db_xref=\"taxon:1638\"\nFT \/organism=\"Listeria ivanovii\"\nFT \/strain=\"ATCC 19119\"\nFT \/mol_type=\"genomic DNA\"\nFT regulatory 95..100\nFT \/gene=\"sod\"\nFT \/regulatory_class=\"ribosome_binding_site\"\nFT regulatory 723..746\nFT \/gene=\"sod\"\nFT \/regulatory_class=\"terminator\"\nFT CDS 109..717\nFT \/transl_table=11\nFT \/gene=\"sod\"\nFT \/EC_number=\"1.15.1.1\"\nFT \/db_xref=\"GOA:P28763\"\nFT \/db_xref=\"HSSP:P00448\"\nFT \/db_xref=\"InterPro:IPR001189\"\nFT \/db_xref=\"UniProtKB\/Swiss-Prot:P28763\"\nFT \/product=\"superoxide dismutase\"\nFT \/protein_id=\"CAA45406.1\"\nFT \/translation=\"MTYELPKLPYTYDALEPNFDKETMEIHYTKHHNIYVTKLNEAVSG\nFT HAELASKPGEELVANLDSVPEEIRGAVRNHGGGHANHTLFWSSLSPNGGGAPTGNLKAA\nFT IESEFGTFDEFKEKFNAAAAARFGSGWAWLVVNNGKLEIVSTANQDSPLSEGKTPVLGL\nFT DVWEHAYYLKFQNRRPEYIDTFWNVINWDERNKRFDAAK\"\nXX\nSQ Sequence 756 BP; 247 A; 136 C; 151 G; 222 T; 0 other;\n cgttatttaa ggtgttacat agttctatgg aaatagggtc tatacctttc gccttacaat 60\n gtaatttctt .......... 120\n\/\/ \n \n<a name=\"7.1.2\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7.1.2 GenBank Format<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">LOCUS LISOD 756 bp DNA linear BCT 30-JUN-1993\nDEFINITION Listeria ivanovii sod gene for superoxide dismutase.\nACCESSION X64011 S78972\nVERSION X64011.1 GI:44010\nKEYWORDS sod gene; superoxide dismutase.\nSOURCE Listeria ivanovii\n ORGANISM Listeria ivanovii\n Bacteria; Firmicutes; Bacillales; Listeriaceae; Listeria. \nREFERENCE 1 (bases 1 to 756)\n AUTHORS Haas,A. and Goebel,W.\n TITLE Cloning of a superoxide dismutase gene from Listeria ivanovii by\n functional complementation in Escherichia coli and characterization\n of the gene product\n JOURNAL Mol. Gen. Genet. 231 (2), 313-322 (1992)\n MEDLINE 92140371\nREFERENCE 2 (bases 1 to 756)\n AUTHORS Kreft,J.\n TITLE Direct Submission\n JOURNAL Submitted (21-APR-1992) J. Kreft, Institut f. Mikrobiologie,\n Universitaet Wuerzburg, Biozentrum Am Hubland, 8700 Wuerzburg, FRG\nFEATURES Location\/Qualifiers\n source 1..756\n \/organism=\"Listeria ivanovii\"\n \/strain=\"ATCC 19119\"\n \/db_xref=\"taxon:1638\"\n \/mol_type=\"genomic DNA\"\n regulatory 95..100\n \/gene=\"sod\"\n \/regulatory_class=\"ribosome_binding_site\"\n gene 95..746\n \/gene=\"sod\"\n CDS 109..717\n \/gene=\"sod\"\n \/EC_number=\"1.15.1.1\"\n \/codon_start=1\n \/transl_table=11\n \/product=\"superoxide dismutase\" \n \/db_xref=\"GI:44011\"\n \/db_xref=\"GOA:P28763\"\n \/db_xref=\"InterPro:IPR001189\"\n \/db_xref=\"UniProtKB\/Swiss-Prot:P28763\"\n \/protein_id=\"CAA45406.1\"\n \/translation=\"MTYELPKLPYTYDALEPNFDKETMEIHYTKHHNIYVTKLNEAVS\n GHAELASKPGEELVANLDSVPEEIRGAVRNHGGGHANHTLFWSSLSPNGGGAPTGNLK\n AAIESEFGTFDEFKEKFNAAAAARFGSGWAWLVVNNGKLEIVSTANQDSPLSEGKTPV\n LGLDVWEHAYYLKFQNRRPEYIDTFWNVINWDERNKRFDAAK\"\n regulatory 723..746\n \/gene=\"sod\"\n \/regulatory_class=\"terminator\"\nORIGIN \n 1 cgttatttaa ggtgttacat agttctatgg aaatagggtc tatacctttc gccttacaat\n 61 gtaatttctt ..........\n\/\/ \n\n\n<a name=\"7.1.3\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7.1.3 DDBJ Format<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">LOCUS LISOD 756 bp DNA linear BCT 30-JUN-1993\nDEFINITION Listeria ivanovii sod gene for superoxide dismutase.\nACCESSION X64011 S78972\nVERSION X64011.1 GI:44010\nKEYWORDS sod gene; superoxide dismutase.\nSOURCE Listeria ivanovii\n ORGANISM Listeria ivanovii\n Bacteria; Firmicutes; Bacillales; Listeriaceae; Listeria. \nREFERENCE 1 (bases 1 to 756)\n AUTHORS Haas,A. and Goebel,W.\n TITLE Cloning of a superoxide dismutase gene from Listeria ivanovii by\n functional complementation in Escherichia coli and characterization\n of the gene product\n JOURNAL Mol. Gen. Genet. 231 (2), 313-322 (1992)\n MEDLINE 92140371\nREFERENCE 2 (bases 1 to 756)\n AUTHORS Kreft,J.\n TITLE Direct Submission\n JOURNAL Submitted (21-APR-1992) J. Kreft, Institut f. Mikrobiologie,\n Universitaet Wuerzburg, Biozentrum Am Hubland, 8700 Wuerzburg, FRG\nFEATURES Location\/Qualifiers\n source 1..756\n \/organism=\"Listeria ivanovii\"\n \/strain=\"ATCC 19119\"\n \/db_xref=\"taxon:1638\"\n \/mol_type=\"genomic DNA\"\n regulatory 95..100\n \/gene=\"sod\"\n \/regulatory_class=\"ribosome_binding_site\"\n gene 95..746\n \/gene=\"sod\"\n CDS 109..717\n \/gene=\"sod\"\n \/EC_number=\"1.15.1.1\"\n \/codon_start=1\n \/transl_table=11\n \/product=\"superoxide dismutase\" \n \/db_xref=\"GOA:P28763\"\n \/db_xref=\"HSSP:P00448\"\n \/db_xref=\"InterPro:IPR001189\"\n \/db_xref=\"UniProtKB\/Swiss-Prot:P28763\"\n \/protein_id=\"CAA45406.1\"\n \/translation=\"MTYELPKLPYTYDALEPNFDKETMEIHYTKHHNIYVTKLNEAVS\n GHAELASKPGEELVANLDSVPEEIRGAVRNHGGGHANHTLFWSSLSPNGGGAPTGNLK\n AAIESEFGTFDEFKEKFNAAAAARFGSGWAWLVVNNGKLEIVSTANQDSPLSEGKTPV\n LGLDVWEHAYYLKFQNRRPEYIDTFWNVINWDERNKRFDAAK\"\n regulatory 723..746\n \/gene=\"sod\"\n \/regulatory_class=\"terminator\"\nBASE COUNT 247 a 136 c 151 g 222 t\nORIGIN \n 1 cgttatttaa ggtgttacat agttctatgg aaatagggtc tatacctttc gccttacaat\n 61 gtaatttctt ..........\n\/\/ \n\n\n\n\n<a name=\"7.2\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7.2 Appendix II: Feature keys reference<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">The following has been organized according to the following format: \nFeature Key the feature key name\nDefinition the definition of the key\nMandatory qualifiers qualifiers required with the key; if there are no\n mandatory qualifiers, this field is omitted.\nOptional qualifiers optional qualifiers associated with the key\nOrganism scope valid organisms for the key; if the scope is any\n organism, this field is omitted.\nMolecule scope valid molecule types; if the scope is any molecule\n type, this field is omitted.\nReferences citations of published reports, usually supporting the\n feature consensus sequence\nComment comments and clarifications\nAbbreviations: \naccnum an entry primary accession number\n<amino_acid> abbreviation for amino acid\n<base_range> location descriptor for a simple range of bases\n<bool> Boolean truth value. Valid values are yes and no\n<integer> unsigned integer value\n<location> general feature location descriptor\n<modified_base> abbreviation for modified nucleotide base\n[number] integer representing number of citation in entry's\n reference list\n<repeat_type> value indicating the organization of a repeated\n sequence. \n\"text\" any text or character string. Since the string is\n delimited by double quotes, double quotes may only\n appear as part of the string if they appear in pairs.\n For example, the sentence:\n\n The \"label\" qualifier is no longer legal.\n\n would be formatted thus:\n\n \"The \"\"label\"\" qualifier is no longer legal.\"\n \n\nFeature Key assembly_gap\n\n\nDefinition gap between two components of a genome or transcriptome assembly;\n\nMandatory qualifiers \/estimated_length=unknown or <integer>\n\t\t \/gap_type=\"TYPE\"\n \/linkage_evidence=\"TYPE\" (Note: Mandatory only if the \n \/gap_type is \"within scaffold\", \"repeat within scaffold\" or \"contamination\".\n If there are multiple types of linkage_evidence\n they will appear as multiple \/linkage_evidence=\"TYPE\"\n qualifiers. For all other types of assembly_gap\n features, use of the \/linkage_evidence qualifier is \n invalid.)\n Mandatory qualifiers under assembly_gap feature for transcriptome\n shotgun assemblies (TSA):\n \/estimated_length=<integer>\n \/gap_type=\"within scaffold\" and \/linkage_evidence=\"TYPE\" where TYPE\n can not be \"unspecified\"; \n\nComment the location span of the assembly_gap feature for an unknown gap has \n to be specified by the submitter; the specified gap length has to be \n reasonable (less or = 1000) and will be indicated as \"n\"'s in sequence.\n However, the value for the estimated_length of assembly_gap features \n within a single (non-CON) transcriptome record must be an integer \n and can not be \"unknown\";\n\n\n\nFeature Key C_region\n\n\nDefinition constant region of immunoglobulin light and heavy \n chains, and T-cell receptor alpha, beta, and gamma \n chains; includes one or more exons depending on the \n particular chain\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n\nOrganism scope eukaryotes\n\n\nFeature Key CDS\n\nDefinition coding sequence; sequence of nucleotides that\n corresponds with the sequence of amino acids in a\n protein (location includes stop codon); \n feature includes amino acid conceptual translation.\n\nOptional qualifiers \/allele=\"text\"\n \/artificial_location=\"[artificial_location_value]\"\n \/circular_RNA\n \/codon_start=<1 or 2 or 3>\n \/db_xref=\"<database>:<identifier>\"\n \/EC_number=\"text\"\n \/exception=\"[exception_value]\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/number=unquoted text (single token)\n \/old_locus_tag=\"text\" (single token)\n \/operon=\"text\"\n \/product=\"text\"\n \/protein_id=\"<identifier>\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/ribosomal_slippage\n \/standard_name=\"text\"\n \/translation=\"text\"\n \/transl_except=(pos:<location>,aa:<amino_acid>)\n \/transl_table =<integer>\n \/trans_splicing\n\nComment \/codon_start has valid value of 1 or 2 or 3, indicating\n the offset at which the first complete codon of a coding\n feature can be found, relative to the first base of\n that feature;\n \/transl_table defines the genetic code table used if\n other than the universal genetic code table;\n genetic code exceptions outside the range of the specified\n tables is reported in \/transl_except qualifier;\n \/protein_id consists of a stable ID portion (from the end of 2018\n new accessions may be extended to a 3+7 accession format with \n 3 position letters and 7 numbers; existing data before the end of \n 2018 uses a 3+5 format) plus a version number after the decimal point;\n when the protein sequence encoded by the CDS changes, only the version \n number of the \/protein_id value is incremented; the\n stable part of the \/protein_id remains unchanged and as \n a result will permanently be associated with a given protein; \n\n\nFeature Key centromere\n\n\nDefinition region of biological interest identified as a centromere and\n which has been experimentally characterized;\n\nOptional qualifiers \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \t\t \/inference=\"[CATEGORY:]TYPE[(same species)][:EVIDENCE_BASIS]\" \n \/note=\"text\"\n \/standard_name=\"text\"\n\nComment the centromere feature describes the interval of DNA \n that corresponds to a region where chromatids are held \n and a kinetochore is formed\n\n\n\nFeature Key D-loop\n\n\nDefinition displacement loop; a region within mitochondrial DNA in\n which a short stretch of RNA is paired with one strand\n of DNA, displacing the original partner DNA strand in\n this region; also used to describe the displacement of a\n region of one strand of duplex DNA by a single stranded\n invader in the reaction catalyzed by RecA protein\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n\nMolecule scope DNA\n\n\nFeature Key D_segment\n\n\nDefinition Diversity segment of immunoglobulin heavy chain, and \n T-cell receptor beta chain; \n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n\nOrganism scope eukaryotes\n\n\nFeature Key exon\n\n\nDefinition region of genome that codes for portion of spliced mRNA, \n rRNA and tRNA; may contain 5'UTR, all CDSs and 3' UTR; \n\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/EC_number=\"text\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/number=unquoted text (single token)\n \/old_locus_tag=\"text\" (single token)\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n \/trans_splicing\n\n\n\nFeature Key gap\n\nDefinition gap in the sequence\n\nMandatory qualifiers \/estimated_length=unknown or <integer>\n\nOptional qualifiers \/experiment=\"[CATEGORY:]text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/map=\"text\"\n \/note=\"text\"\n\nComment the location span of the gap feature for an unknown \n gap is 100 bp, with the 100 bp indicated as 100 \"n\"'s in \n the sequence. Where estimated length is indicated by \n an integer, this is indicated by the same number of \n \"n\"'s in the sequence. \n No upper or lower limit is set on the size of the gap.\n\n\n\nFeature Key gene\n\n\nDefinition region of biological interest identified as a gene \n and for which a name has been assigned;\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/operon=\"text\"\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/phenotype=\"text\"\n \/standard_name=\"text\"\n \/trans_splicing\n\n \nComment the gene feature describes the interval of DNA that \n corresponds to a genetic trait or phenotype; the feature is,\n by definition, not strictly bound to it's positions at the \n ends; it is meant to represent a region where the gene is \n located.\n \n\n\n\n\nFeature Key iDNA\n\n\nDefinition intervening DNA; DNA which is eliminated through any of\n several kinds of recombination;\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/number=unquoted text (single token)\n \/old_locus_tag=\"text\" (single token)\n \/standard_name=\"text\"\n\nMolecule scope DNA\n\nComment e.g., in the somatic processing of immunoglobulin genes.\n\n\n\n\nFeature Key intron\n\n\nDefinition a segment of DNA that is transcribed, but removed from\n within the transcript by splicing together the sequences\n (exons) on either side of it;\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/number=unquoted text (single token)\n \/old_locus_tag=\"text\" (single token)\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n \/trans_splicing\n\n\nFeature Key J_segment\n \n\nDefinition joining segment of immunoglobulin light and heavy \n chains, and T-cell receptor alpha, beta, and gamma \n chains; \n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n\nOrganism scope eukaryotes\n\n\nFeature Key mat_peptide\n\n\nDefinition mature peptide or protein coding sequence; coding\n sequence for the mature or final peptide or protein\n product following post-translational modification; the\n location does not include the stop codon (unlike the\n corresponding CDS);\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/EC_number=\"text\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n\n\n\n\n\nFeature Key misc_binding\n\n\nDefinition site in nucleic acid which covalently or non-covalently\n binds another moiety that cannot be described by any\n other binding key (primer_bind or protein_bind);\n\nMandatory qualifiers \/bound_moiety=\"text\"\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n\nComment note that feature key regulatory with \/regulatory_class=\"ribosome_binding_site\"\n should be used for ribosome binding sites.\n\n\n\nFeature Key misc_difference\n\n\nDefinition feature sequence is different from that presented \n in the entry and cannot be described by any other \n difference key (old_sequence, variation, or modified_base);\n\nOptional qualifiers \/allele=\"text\"\n \/clone=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\" \n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/phenotype=\"text\"\n \/replace=\"text\" \n \/standard_name=\"text\"\n\nComment the misc_difference feature key should be used to \n describe variability that arises as a result of \n genetic manipulation (e.g. site directed mutagenesis);\n use \/replace=\"\" to annotate deletion, e.g. \n misc_difference 412..433\n \/replace=\"\" \n\n\n\n\nFeature Key misc_feature\n\n\nDefinition region of biological interest which cannot be described\n by any other feature key; a new or rare feature;\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/number=unquoted text (single token)\n \/old_locus_tag=\"text\" (single token)\n \/phenotype=\"text\"\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n\nComment this key should not be used when the need is merely to \n mark a region in order to comment on it or to use it in \n another feature's location\n\n\nFeature Key misc_recomb\n\nDefinition site of any generalized, site-specific or replicative\n recombination event where there is a breakage and\n reunion of duplex DNA that cannot be described by other\n recombination keys or qualifiers of source key \n (\/proviral);\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/recombination_class=\"TYPE\"\n \/standard_name=\"text\"\n\nMolecule scope DNA\n \n\n\n\nFeature Key misc_RNA\n\n\nDefinition any transcript or RNA product that cannot be defined by\n other RNA keys (prim_transcript, precursor_RNA, mRNA,\n 5'UTR, 3'UTR, exon, CDS, sig_peptide, transit_peptide,\n mat_peptide, intron, polyA_site, ncRNA, rRNA and tRNA);\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/operon=\"text\"\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n \/trans_splicing\n\n\n\nFeature Key misc_structure\n\n\nDefinition any secondary or tertiary nucleotide structure or \n conformation that cannot be described by other Structure\n keys (stem_loop and D-loop);\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/standard_name=\"text\"\n\n\nFeature Key mobile_element\n\n\nDefinition region of genome containing mobile elements;\n\nMandatory qualifiers \/mobile_element_type=\"<mobile_element_type>\n [:<mobile_element_name>]\"\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\" \n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/rpt_family=\"text\"\n \/rpt_type=<repeat_type>\n \/standard_name=\"text\"\n\n\nFeature Key modified_base\n\n\nDefinition the indicated nucleotide is a modified nucleotide and\n should be substituted for by the indicated molecule\n (given in the mod_base qualifier value)\n \nMandatory qualifiers \/mod_base=<modified_base>\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/frequency=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n\nComment value is limited to the restricted vocabulary for \n modified base abbreviations;\n\n\nFeature Key mRNA\n\n\nDefinition messenger RNA; includes 5'untranslated region (5'UTR),\n coding sequences (CDS, exon) and 3'untranslated region\n (3'UTR);\n\nOptional qualifiers \/allele=\"text\"\n \/artificial_location=\"[artificial_location_value]\"\n \/circular_RNA\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/operon=\"text\"\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n \/trans_splicing\n\n\nFeature Key ncRNA\n\nDefinition a non-protein-coding gene, other than ribosomal RNA and\n transfer RNA, the functional molecule of which is the RNA\n transcript;\n\nMandatory qualifiers \/ncRNA_class=\"TYPE\"\n \nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/operon=\"text\"\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n \/trans_splicing\n\nExample \/ncRNA_class=\"miRNA\"\n \/ncRNA_class=\"siRNA\"\n \/ncRNA_class=\"scRNA\" \n\nComment the ncRNA feature is not used for ribosomal and transfer\n RNA annotation, for which the rRNA and tRNA feature keys\n should be used, respectively;\n\n\nFeature Key N_region\n\n\nDefinition extra nucleotides inserted between rearranged \n immunoglobulin segments.\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n\nOrganism scope eukaryotes\n\n\nFeature Key old_sequence\n\n\nDefinition the presented sequence revises a previous version of the\n sequence at this location;\n\nMandatory qualifiers \/citation=[number]\n Or\n \/compare=[accession-number.sequence-version]\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/replace=\"text\"\n\nComment \/replace=\"\" is used to annotate deletion, e.g. \n old_sequence 12..15\n \/replace=\"\" \n NOTE: This feature key is not valid in entries\/records\n created from 15-Oct-2007.\n\n\nFeature Key operon\n\nDefinition region containing polycistronic transcript including a cluster of\n genes that are under the control of the same regulatory sequences\/promoter\n and in the same biological pathway\n\nMandatory qualifiers \/operon=\"text\"\n \nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/map=\"text\"\n \/note=\"text\"\n \/phenotype=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n \n\n\n\nFeature Key oriT\nDefinition origin of transfer; region of a DNA molecule where transfer is\n initiated during the process of conjugation or mobilization\n\nOptional qualifiers \/allele=\"text\"\n \/bound_moiety=\"text\"\n \/db_xref=\"<database>:<identifier>\" \n \/direction=value\n \/experiment=\"[CATEGORY:]text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/rpt_family=\"text\"\n \/rpt_type=<repeat_type>\n \/rpt_unit_range=<base_range>\n \/rpt_unit_seq=\"text\"\n \/standard_name=\"text\"\n\n\nMolecule Scope DNA\n\nComment rep_origin should be used for origins of replication; \n \/direction has legal values RIGHT, LEFT and BOTH, however only \n RIGHT and LEFT are valid when used in conjunction with the oriT \n feature;\n origins of transfer can be present in the chromosome; \n plasmids can contain multiple origins of transfer\n\n\n\nFeature Key polyA_site\n\n\nDefinition site on an RNA transcript to which will be added adenine\n residues by post-transcriptional polyadenylation;\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\" \n \/experiment=\"[CATEGORY:]text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n\nOrganism scope eukaryotes and eukaryotic viruses\n\n\nFeature Key precursor_RNA\n\n\nDefinition any RNA species that is not yet the mature RNA product;\n may include ncRNA, rRNA, tRNA, 5' untranslated region\n (5'UTR), coding sequences (CDS, exon), intervening\n sequences (intron) and 3' untranslated region (3'UTR);\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\" \n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/operon=\"text\"\n \/product=\"text\"\n \/standard_name=\"text\"\n \/trans_splicing\n\nComment used for RNA which may be the result of \n post-transcriptional processing; if the RNA in question \n is known not to have been processed, use the \n prim_transcript key.\n\n\nFeature Key prim_transcript\n\n\nDefinition primary (initial, unprocessed) transcript; \n may include ncRNA, rRNA, tRNA, 5' untranslated region\n (5'UTR), coding sequences (CDS, exon), intervening\n sequences (intron) and 3' untranslated region (3'UTR);\n\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/operon=\"text\"\n \/standard_name=\"text\"\n\n\nFeature Key primer_bind\n\n\nDefinition non-covalent primer binding site for initiation of\n replication, transcription, or reverse transcription;\n includes site(s) for synthetic e.g., PCR primer elements;\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/standard_name=\"text\"\n \/PCR_conditions=\"text\"\n\nComment used to annotate the site on a given sequence to which a primer \n molecule binds - not intended to represent the sequence of the\n primer molecule itself; PCR components and reaction times may \n be stored under the \"\/PCR_conditions\" qualifier; \n since PCR reactions most often involve pairs of primers,\n a single primer_bind key may use the order() operator\n with two locations, or a pair of primer_bind keys may be\n used.\n\n\nFeature Key propeptide\n\n\nDefinition propeptide coding sequence; coding sequence for the domain of a \n proprotein that is cleaved to form the mature protein product.\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n\n\nFeature Key protein_bind\n\n\nDefinition non-covalent protein binding site on nucleic acid;\n\nMandatory qualifiers \/bound_moiety=\"text\"\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/operon=\"text\"\n \/standard_name=\"text\"\n\nComment note that feature key regulatory with \/regulatory_class=\"ribosome_binding_site\"\n should be used for ribosome binding sites.\n\n\n\nFeature Key regulatory\n\n\nDefinition any region of sequence that functions in the regulation of\n transcription, translation, replication, recombination, or chromatin structure;\n\nMandatory qualifiers \/regulatory_class=\"TYPE\"\n\nOptional qualifiers \/allele=\"text\"\n \/bound_moiety=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/operon=\"text\"\n \/phenotype=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n\nComment\t This feature has replaced the following Feature Keys on 15-DEC-2014:\n enhancer, promoter, CAAT_signal, TATA_signal, -35_signal, -10_signal,\n RBS, GC_signal, polyA_signal, attenuator, terminator, misc_signal.\n\n \nFeature Key repeat_region\n\n\nDefinition region of genome containing repeating units;\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\" \n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/rpt_family=\"text\"\n \/rpt_type=<repeat_type>\n \/rpt_unit_range=<base_range>\n \/rpt_unit_seq=\"text\"\n \/satellite=\"<satellite_type>[:<class>][ <identifier>]\"\n \/standard_name=\"text\"\n\n\nFeature Key rep_origin\n\n\nDefinition origin of replication; starting site for duplication of\n nucleic acid to give two identical copies; \n\nOptional Qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/direction=value\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/standard_name=\"text\"\n\nComment \/direction has valid values: RIGHT, LEFT, or BOTH.\n\n\nFeature Key rRNA\n\n\nDefinition mature ribosomal RNA; RNA component of the\n ribonucleoprotein particle (ribosome) which assembles\n amino acids into proteins.\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/operon=\"text\"\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n\nComment rRNA sizes should be annotated with the \/product\n qualifier. \n\n\nFeature Key S_region\n\n\nDefinition switch region of immunoglobulin heavy chains; \n involved in the rearrangement of heavy chain DNA leading \n to the expression of a different immunoglobulin class \n from the same B-cell;\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n\nOrganism scope eukaryotes\n\n\nFeature Key sig_peptide\n\n\nDefinition signal peptide coding sequence; coding sequence for an\n N-terminal domain of a secreted protein; this domain is\n involved in attaching nascent polypeptide to the\n membrane leader sequence;\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n\n\nFeature Key source\n\n\nDefinition identifies the biological source of the specified span of\n the sequence; this key is mandatory; more than one source\n key per sequence is allowed; every entry\/record will have, as a\n minimum, either a single source key spanning the entire\n sequence or multiple source keys, which together, span the\n entire sequence.\n\nMandatory qualifiers \/organism=\"text\"\n \/mol_type=\"genomic DNA\", \"genomic RNA\", \"mRNA\", \"tRNA\",\n \"rRNA\", \"other RNA\", \"other DNA\", \"transcribed\n RNA\", \"viral cRNA\", \"unassigned DNA\",\n \"unassigned RNA\"\n\n\nOptional qualifiers \/altitude=\"text\"\n \/bio_material=\"[<institution-code>:[<collection-code>:]]<material_id>\"\n \/cell_line=\"text\"\n \/cell_type=\"text\"\n \/chromosome=\"text\"\n \/clone=\"text\"\n \/clone_lib=\"text\"\n \/collected_by=\"text\" \n \/collection_date=\"text\"\n \/country=\"<country_value>[:<region>][, <locality>]\"\n \/cultivar=\"text\"\n \/culture_collection=\"<institution-code>:[<collection-code>:]<culture_id>\"\n \/db_xref=\"<database>:<identifier>\"\n \/dev_stage=\"text\"\n \/ecotype=\"text\"\n \/environmental_sample\n \/focus\n \/geo_loc_name=\"<country_value>[:<region>][, <locality>]\"\n \/germline\n \/haplogroup=\"text\"\n \/haplotype=\"text\"\n \/host=\"text\"\n \/identified_by=\"text\"\n \/isolate=\"text\"\n \/isolation_source=\"text\"\n \/lab_host=\"text\"\n \/lat_lon=\"text\"\n \/macronuclear\n \/map=\"text\"\n \/mating_type=\"text\"\n \/metagenome_source=\"text\"\n \/note=\"text\"\n \/organelle=<organelle_value>\n \/PCR_primers=\"[fwd_name: XXX, ]fwd_seq: xxxxx, \n [rev_name: YYY, ]rev_seq: yyyyy\"\n \/plasmid=\"text\"\n \/pop_variant=\"text\"\n \/proviral\n \/rearranged\n \/segment=\"text\"\n \/serotype=\"text\"\n \/serovar=\"text\"\n \/sex=\"text\"\n \/specimen_voucher=\"[<institution-code>:[<collection-code>:]]<specimen_id>\"\n \/strain=\"text\"\n \/sub_clone=\"text\"\n \/submitter_seqid=\"text\"\n \/sub_species=\"text\"\n \/sub_strain=\"text\"\n \/tissue_lib=\"text\"\n \/tissue_type=\"text\"\n \/transgenic\n \/type_material=\"<type-of-type> of <organism name>\"\n \/variety=\"text\"\n\nMolecule scope any\n\nComment transgenic sequences must have at least two source feature\n keys; in a transgenic sequence the source feature key\n describing the organism that is the recipient of the DNA\n must span the entire sequence;\n see Appendix III \/organelle for a list of <organelle_value>\n From June 2024, the \/country qualifier will be \n transitioned to \/geo_loc_name. \/country may still be \n encountered on records prior to this date. \n\n\nFeature Key stem_loop\n\n\nDefinition hairpin; a double-helical region formed by base-pairing\n between adjacent (inverted) complementary sequences in a\n single strand of RNA or DNA. \n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/operon=\"text\"\n \/standard_name=\"text\"\n\n\nFeature Key STS\n\nDefinition sequence tagged site; short, single-copy DNA sequence\n that characterizes a mapping landmark on the genome and\n can be detected by PCR; a region of the genome can be\n mapped by determining the order of a series of STSs;\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/standard_name=\"text\"\n\nMolecule scope DNA\n\nComment STS location to include primer(s) in primer_bind key or\n primers.\n\n\nFeature Key telomere\n\nDefinition region of biological interest identified as a telomere \n and which has been experimentally characterized;\n\nOptional qualifiers \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\/note=\"text\"\n \/inference=\"[CATEGORY:]TYPE[(same species)][:EVIDENCE_BASIS]\"\n \/note=\"text\" \n \/rpt_type=<repeat_type>\n \/rpt_unit_range=<base_range>\n \/rpt_unit_seq=\"text\"\n \/standard_name=\"text\"\n\nComment the telomere feature describes the interval of DNA \n that corresponds to a specific structure at the end of \n the linear eukaryotic chromosome which is required for \n\t\t the integrity and maintenance of the end; this region\n is unique compared to the rest of the chromosome and \n represent the physical end of the chromosome;\n\n\n\nFeature Key tmRNA\n\nDefinition transfer messenger RNA; tmRNA acts as a tRNA first,\n and then as an mRNA that encodes a peptide tag; the\n ribosome translates this mRNA region of tmRNA and attaches\n the encoded peptide tag to the C-terminus of the\n unfinished protein; this attached tag targets the protein for\n destruction or proteolysis;\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n \/tag_peptide=<base_range>\n\n\n\nFeature Key transit_peptide\n\n\nDefinition transit peptide coding sequence; coding sequence for an\n N-terminal domain of a nuclear-encoded organellar\n protein; this domain is involved in post-translational\n import of the protein into the organelle;\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n\n\n\nFeature Key tRNA\n\n\nDefinition mature transfer RNA, a small RNA molecule (75-85 bases\n long) that mediates the translation of a nucleic acid\n sequence into an amino acid sequence;\n\nOptional qualifiers \/allele=\"text\"\n \/anticodon=(pos:<location>,aa:<amino_acid>,seq:<text>)\n \/circular_RNA\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/operon=\"text\"\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n \/trans_splicing\n\n\n\nFeature Key unsure\n\n\nDefinition a small region of sequenced bases, generally 10 or fewer in its length, which \n could not be confidently identified. Such a region might contain called bases \n (A, T, G, or C), or a mixture of called-bases and uncalled-bases ('N').\n The unsure feature should not be used when annotating gaps in genome assemblies.\n Please refer to assembly_gap feature for gaps within the sequence of an assembled\n genome. For annotation of gaps in other sequences than assembled genomes use the \n gap feature.\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/replace=\"text\"\n\nComment use \/replace=\"\" to annotate deletion, e.g. \n unsure 11..15\n \/replace=\"\" \n\n\n\n\nFeature Key V_region\n \n\nDefinition variable region of immunoglobulin light and heavy\n chains, and T-cell receptor alpha, beta, and gamma\n chains; codes for the variable amino terminal portion;\n can be composed of V_segments, D_segments, N_regions,\n and J_segments;\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n\nOrganism scope eukaryotes\n\n\n\nFeature Key V_segment\n\n\nDefinition variable segment of immunoglobulin light and heavy\n chains, and T-cell receptor alpha, beta, and gamma\n chains; codes for most of the variable region (V_region)\n and the last few amino acids of the leader peptide;\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/product=\"text\"\n \/pseudo\n \/pseudogene=\"TYPE\"\n \/standard_name=\"text\"\n\nOrganism scope eukaryotes\n\n\nFeature Key variation\n\nDefinition a related strain contains stable mutations from the same\n gene (e.g., RFLPs, polymorphisms, etc.) which differ\n from the presented sequence at this location (and\n possibly others);\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/frequency=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/phenotype=\"text\"\n \/product=\"text\"\n \/replace=\"text\"\n \/standard_name=\"text\"\n\nComment used to describe alleles, RFLP's,and other naturally occurring \n mutations and polymorphisms; variability arising as a result \n of genetic manipulation (e.g. site directed mutagenesis) should \n be described with the misc_difference feature;\n use \/replace=\"\" to annotate deletion, e.g. \n variation 4..5\n \/replace=\"\" \n\n\n\n\nFeature Key 3'UTR\n\n\nDefinition 1) region at the 3' end of a mature transcript (following \n the stop codon) that is not translated into a protein;\n 2) region at the 3' end of an RNA virus (following the last stop\n codon) that is not translated into a protein;\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/standard_name=\"text\"\n \/trans_splicing\n\n\n\nFeature Key 5'UTR\n\n\nDefinition 1) region at the 5' end of a mature transcript (preceding \n the initiation codon) that is not translated into a protein;\n 2) region at the 5' end of an RNA virus genome (preceding the first \n initiation codon) that is not translated into a protein;\n\nOptional qualifiers \/allele=\"text\"\n \/db_xref=\"<database>:<identifier>\"\n \/experiment=\"[CATEGORY:]text\"\n \/function=\"text\"\n \/gene=\"text\"\n \/gene_synonym=\"text\"\n \/inference=\"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \/locus_tag=\"text\" (single token)\n \/map=\"text\"\n \/note=\"text\"\n \/old_locus_tag=\"text\" (single token)\n \/standard_name=\"text\"\n \/trans_splicing\n\n\n \n<a name=\"7.3\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7.3 Appendix III: Summary of qualifiers for feature keys<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\"><a name=\"7.3.1\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7.3.1 Qualifier List<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">The following is a list of available qualifiers for feature keys and their usage. \nThe information is arranged as follows:\n\n\nQualifier name of qualifier; qualifier requires a value if followed by an equal \n sign\nDefinition definition of the qualifier\nValue format format of value, if required\nExample example of qualifier with value\nComment comments, questions and clarifications\n\n\nQualifier \/allele=\nDefinition name of the allele for the given gene \nValue format \"text\"\nExample \/allele=\"adh1-1\"\nComment all gene-related features (exon, CDS etc) for a given \n gene should share the same \/allele qualifier value; \n the \/allele qualifier value must, by definition, be \n different from the \/gene qualifier value; when used with \n the variation feature key, the allele qualifier value \n should be that of the variant.\n\n\nQualifier \/altitude=\nDefinition geographical altitude of the location from which the sample\n was collected\nValue format \"text\"\nExample \/altitude=\"-256 m\"\n \/altitude=\"330.12 m\"\nComment Values indicate altitudes above or below nominal sea level \n provided in metres\n\n\n\nQualifier \/anticodon=\nDefinition location of the anticodon of tRNA and the amino acid for which\n it codes\nValue format (pos:<location>,aa:<amino_acid>,seq:<text>) where location\n is the position of the anticodon and amino_acid is the abbreviation for the\n amino acid encoded and seq is the sequence of the anticodon\nExample \/anticodon=(pos:34..36,aa:Phe,seq:aaa)\n \/anticodon=(pos:join(5,495..496),aa:Leu,seq:taa)\n \/anticodon=(pos:complement(4156..4158),aa:Gln,seq:ttg)\n\n\nQualifier \/artificial_location\nDefinition indicates that location of the CDS or mRNA is modified to adjust\n for the presence of a frameshift or internal stop codon and not\n because of biological processing between the regions.\nValue format \"heterogeneous population sequenced\", \"low-quality sequence region\"\nExample \/artificial_location=\"heterogeneous population sequenced\"\n \/artificial_location=\"low-quality sequence region\"\nComment expected to be used only for genome-scale annotation.\n\n\nQualifier \/bio_material=\nDefinition identifier for the biological material from which the nucleic\n acid sequenced was obtained, with optional institution code and\n collection code for the place where it is currently stored.\nValue format \"[<institution-code>:[<collection-code>:]]<material_id>\"\nExample \/bio_material=\"CGC:CB3912\" <- Caenorhabditis stock centre\nComment the bio_material qualifier should be used to annotate the\n identifiers of material in biological collections that are not\n appropriate to annotate as either \/specimen_voucher or\n \/culture_collection; these include zoos and aquaria, stock\n centres, seed banks, germplasm repositories and DNA banks;\n material_id is mandatory, institution_code and collection_code\n are optional; institution code is mandatory where collection\n code is present; institution code and collection code are taken\n from a controlled vocabulary maintained by the INSDC. \n\n\nQualifier \/bound_moiety=\nDefinition name of the molecule\/complex that may bind to the \n given feature \nValue format \"text\"\nExample \/bound_moiety=\"GAL4\" \nComment A single \/bound_moiety qualifier is legal on the \"misc_binding\", \n \"oriT\" and \"protein_bind\" features.\n\n\nQualifier \/cell_line=\nDefinition cell line from which the sequence was obtained\nValue format \"text\"\nExample \/cell_line=\"MCF7\"\n\n\nQualifier \/cell_type=\nDefinition cell type from which the sequence was obtained\nValue format \"text\"\nExample \/cell_type=\"leukocyte\"\n\n\nQualifier \/chromosome=\nDefinition chromosome (e.g. Chromosome number) from which\n the sequence was obtained\nValue format \"text\"\nExample \/chromosome=\"1\"\n\n\nQualifier \/circular_RNA\nDefinition indicates that exons are out-of-order or overlapping \n because this spliced RNA product is a circular RNA \n (circRNA) created by backsplicing, for example when \n a downstream exon in the gene is located 5\u2019 of an \n upstream exon in the RNA product\nValue format none\nExample \/circular_RNA\nComment should be used on features such as CDS, mRNA, tRNA and other \n features that are produced as a result of a backsplicing event. \n This qualifier should be used only when the splice event is \n indicated in the \"join\" operator, \n eg join(101627..101652,102190..102421,73380..73493)\n\n\nQualifier \/citation=\nDefinition reference to a citation listed in the entry reference field\nValue format [integer-number] where integer-number is the number of the\n reference as enumerated in the reference field\nExample \/citation=[3]\nComment not to be used for new entries from 14-MAY-2021;used to indicate \n the citation providing the claim of and\/or evidence for a feature; brackets\n are used for conformity.\n\n\nQualifier \/clone=\nDefinition clone from which the sequence was obtained\nValue format \"text\"\nExample \/clone=\"lambda-hIL7.3\"\nComment not more than one clone should be specified for a given source \n feature; to indicate that the sequence was obtained from\n multiple clones, multiple source features should be given.\n\n\nQualifier \/clone_lib=\nDefinition clone library from which the sequence was obtained\nValue format \"text\"\nExample \/clone_lib=\"lambda-hIL7\"\n\n\nQualifier \/codon_start=\nDefinition indicates the offset at which the first complete codon of a\n coding feature can be found, relative to the first base of that\n feature.\nValue format 1 or 2 or 3\nExample \/codon_start=2\n\n\nQualifier \/collected_by= \nDefinition name of persons or institute who collected the specimen \nValue format \"text\" \nExample \/collected_by=\"Dan Janzen\" \n\n\nQualifier \/collection_date= \n\nDefinition The date on which the specimen was collected. \n Date\/time ranges are supported by providing two collection \n dates from among the supported value formats, delimited by \n a forward-slash character. \n Collection times are supported by adding \"T\", then the hour \n and minute and seconds, after the date. \n Collection times must be in Coordinated Universal Time (UTC), \n otherwise known as \"Zulu Time\" (Z) or be a specified exemption\n from the missing values controlled vocabulary at\n https:\/\/www.insdc.org\/submitting-standards\/missing-value-reporting\/.\n\nValue format \"DD-Mmm-YYYY\", \"Mmm-YYYY\", \"YYYY\"\n \"YYYY-MM-DDThh:mmZ\", \"YYYY-MM-DDThh:mm:ssZ\", \"YYYY-MM-DDThhZ\", \n \"YYYY-MM-DD\", or \"YYYY-MM\"\n Or either of the missing values controlled vocabulary at \n https:\/\/www.insdc.org\/submitting-standards\/missing-value-reporting\/.\n\nExample \/collection_date=\"21-Oct-1952\" \n \/collection_date=\"Oct-1952\" \n \/collection_date=\"1952\" \n \/collection_date=\"1952-10-21T11:43Z\"\n \/collection_date=\"1952-10-21T11Z\"\n \/collection_date=\"1952-10-21\"\n \/collection_date=\"1952-10\"\n \/collection_date=\"21-Oct-1952\/15-Feb-1953\"\n \/collection_date=\"Oct-1952\/Feb-1953\"\n \/collection_date=\"1952\/1953\"\n \/collection_date=\"1952-10-21\/1953-02-15\"\n \/collection_date=\"1952-10\/1953-02\"\n \/collection_date=\"1952-10-21T11:43Z\/1952-10-21T17:43Z\"\n \/collection_date=\"2015-10-11T17:53:03Z\"\n \/collection_date=\"missing: control sample\"\nComment 'Mmm' represents a three-letter month abbreviation, and can be one of the following:\n Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec\n\n 'YYYY' is a four-digit value representing the year. 'MM' is a two-digit value representing\n the month. 'DD' is a two-digit value representing the day of the month.\n\n 'hh' is a two-digit value representing the hour of the day (00 to 23)\n 'mm' is a two-digit value representing the minute of the hour (00 to 59)\n 'ss' is a two-digit value representing the second of the hour (00 to 59)\n\n Within a date range, value formats that make use of 'Mmm' (month abbreviations) cannot be\n combined with value formats that make use of 'MM' (two-digit month number)\n\n Collection dates that are specified to at least the month, day, and year (DD-Mmm-YYYY or YYYY-MM-DD)\n are strongly encouraged. If the day and\/or month of the collection date are not known, \n Mmm-YYYY or YYYY-MM or YYYY may be used.\n\n Within a collection date range, the first date (possibly including time) must be\n prior to the second date (possibly including time).\n\n Within a collection date range for which the day, month, and year are identical, the first time value\n must be prior to the second time value.\n\n\nQualifier \/compare=\nDefinition Reference details of an existing public INSD entry \n to which a comparison is made\nValue format [accession-number.sequence-version]\nExample \/compare=AJ634337.1\nComment not to be used for new entries from 14-MAY-2021; This qualifier may \n be used on the following features: misc_difference, unsure, old_sequence \n\t\t\t\tand variation.\n The feature \"old_sequence\" must have either a\n \/citation or a \/compare qualifier. Multiple \/compare\n qualifiers with different contents are allowed within a \n single feature. \n This qualifier is not intended for large-scale annotation \n of variations, such as SNPs.\n\n\nQualifier \/country=\nDefinition locality of isolation of the sequenced sample indicated in\n terms of political names for nations, oceans or seas, followed\n by regions and localities\nValue format \"<country_value>[:<region>][, <locality>]\" where \n country_value is any value from the controlled vocabulary at \n https:\/\/www.insdc.org\/submitting-standards\/country-qualifier-vocabulary\/ or \n a specified exemption from the missing values controlled vocabulary at \n the https:\/\/www.insdc.org\/submitting-standards\/missing-value-reporting\/.\nExample \/country=\"Canada:Vancouver\"\n \/country=\"France:Cote d'Azur, Antibes\"\n \/country=\"Atlantic Ocean:Charlie Gibbs Fracture Zone\"\n \/country=\"missing: lab stock\"\nComment Intended to provide a reference to the site where the source\n organism was isolated or sampled. Regions and localities should\n be indicated where possible. Note that the physical geography of\n the isolation or sampling site should be represented in\n \/isolation_source. From June 2024, the \/country\n qualifier will be transitioned to \/geo_loc_name. \/country may\n still be encountered on records prior to this date. \n\n\nQualifier \/cultivar=\nDefinition cultivar (cultivated variety) of plant from which sequence was \n obtained. \nValue format \"text\"\nExample \/cultivar=\"Nipponbare\"\n \/cultivar=\"Tenuifolius\"\n \/cultivar=\"Candy Cane\"\n \/cultivar=\"IR36\"\nComment 'cultivar' is applied solely to products of artificial \n selection; use the variety qualifier for natural, named \n plant and fungal varieties; \n\n\nQualifier \/culture_collection=\nDefinition institution code and identifier for the culture from which the\n nucleic acid sequenced was obtained, with optional collection\n code.\nValue format \"<institution-code>:[<collection-code>:]<culture_id>\"\nExample \/culture_collection=\"ATCC:26370\"\nComment the \/culture_collection qualifier should be used to annotate\n live microbial and viral cultures, and cell lines that have been\n deposited in curated culture collections; microbial cultures in\n personal or laboratory collections should be annotated in strain\n qualifiers;\n annotation with a culture_collection qualifier implies that the\n sequence was obtained from a sample retrieved (by the submitter\n or a collaborator) from the indicated culture collection, or\n that the sequence was obtained from a sample that was deposited\n (by the submitter or a collaborator) in the indicated culture\n collection; annotation with more than one culture_collection\n qualifier indicates that the sequence was obtained from a sample\n that was deposited (by the submitter or a collaborator) in more\n than one culture collection.\n culture_id and institution_code are mandatory, collection_code\n is optional; institution code and collection code are taken\n from a controlled vocabulary maintained by the INSDC.\n https:\/\/www.insdc.org\/submitting-standards\/controlled-vocabulary-culturecollection-qualifier\/.\n\n\nQualifier \/db_xref=\nDefinition database cross-reference: pointer to related information in \n another database.\nValue format \"<database:identifier>\" where database is\n the name of the database containing related information, and \n identifier is the internal identifier of the related information\n according to the naming conventions of the cross-referenced \n database.\nExample \/db_xref=\"UniProtKB\/Swiss-Prot:P28763\"\nComment the complete list of allowed database types is kept at \n https:\/\/www.insdc.org\/submitting-standards\/dbxref-qualifier-vocabulary\/.\n\n\nQualifier \/dev_stage=\nDefinition if the sequence was obtained from an organism in a specific \n developmental stage, it is specified with this qualifier\nValue format \"text\"\nExample \/dev_stage=\"fourth instar larva\"\n\n\nQualifier \/direction=\nDefinition direction of DNA replication\nValue format left, right, or both where left indicates toward the 5' end of\n the entry sequence (as presented) and right indicates toward\n the 3' end\nExample \/direction=LEFT\n\n\nQualifier \/EC_number=\nDefinition Enzyme Commission number for enzyme product of sequence\nValue format \"text\"\nExample \/EC_number=\"1.1.2.4\"\n \/EC_number=\"1.1.2.-\"\n \/EC_number=\"1.1.2.n\"\n \/EC_number=\"1.1.2.n1\" \nComment valid values for EC numbers are defined in the list prepared by the \n Nomenclature Committee of the International Union of Biochemistry and\n Molecular Biology (NC-IUBMB) (published in Enzyme Nomenclature 1992,\n Academic Press, San Diego, or a more recent revision thereof). \n The format represents a string of four numbers separated by full\n stops; up to three numbers starting from the end of the string can \n be replaced by dash \".\" to indicate uncertain assignment. \n Symbols including an \"n\", e.g. \"n\", \"n1\" and so on, can be \n used in the last position instead of a number where the EC number is\n awaiting assignment. Please note that such incomplete EC numbers \n are not approved by NC-IUBMB.\n\n\nQualifier \/ecotype=\nDefinition a population within a given species displaying genetically \n based, phenotypic traits that reflect adaptation to a local habitat.\nValue Format \"text\"\nExample \/ecotype=\"Columbia\"\nComment an example of such a population is one that has adapted hairier\n than normal leaves as a response to an especially sunny habitat.\n 'Ecotype' is often applied to standard genetic stocks of\n Arabidopsis thaliana, but it can be applied to any sessile \n organism.\n\n\nQualifier \/environmental_sample\nDefinition identifies sequences derived by direct molecular\n isolation from a bulk environmental DNA sample\n (by PCR with or without subsequent cloning of the\n product, DGGE, or other anonymous methods) with no\n reliable identification of the source organism.\n Environmental samples include clinical samples,\n gut contents, and other sequences from anonymous\n organisms that may be associated with a particular\n host. They do not include endosymbionts that can be\n reliably recovered from a particular host, organisms\n from a readily identifiable but uncultured field sample\n (e.g., many cyanobacteria), or phytoplasmas that can be \n reliably recovered from diseased plants (even though \n these cannot be grown in axenic culture).\nValue format none\nExample \/environmental_sample\nComment used only with the source feature key; source feature \n keys containing the \/environmental_sample qualifier \n should also contain the \/isolation_source qualifier.\n entries including \/environmental_sample must not include \n the \/strain qualifier\n\n\nQualifier \/estimated_length=\nDefinition estimated length of the gap in the sequence\nValue format unknown or <integer>\nExample \/estimated_length=unknown\n \/estimated_length=342\n\n\nQualifier \/exception=\nDefinition indicates that the coding region cannot be translated using\n standard biological rules\nValue format \"RNA editing\", \"reasons given in citation\",\n \"rearrangement required for product\", \"annotated by transcript\n or proteomic data\"\nExample \/exception=\"RNA editing\"\n \/exception=\"reasons given in citation\"\n \/exception=\"rearrangement required for product\"\n \/exception=\"annotated by transcript or proteomic data\"\nComment only to be used to describe biological mechanisms such \n as RNA editing; where the exception cannot easily be described \n a published citation must be referred to; protein translation of\n \/exception CDS will be different from the according conceptual \n translation; \n - An \/inference qualifier should accompany any use of\n \/exception=\"annotated by transcript or proteomic data\", to\n provide support for the existence of the transcript\/protein.\n - must not be used where transl_except would be adequate,\n e.g. in case of stop codon completion use:\n \/transl_except=(pos:6883,aa:TERM)\n \/note=\"TAA stop codon is completed by addition of 3' A residues to \n mRNA\".\n - must not be used for ribosomal slippage, instead use join operator, \n e.g.: CDS join(486..1784,1787..4810)\n \/note=\"ribosomal slip on tttt sequence at 1784..1787\"\n\n\nQualifier \/experiment=\nDefinition a brief description of the nature of the experimental \n evidence that supports the feature identification or assignment.\nValue format \"[CATEGORY:]text\"\n where CATEGORY is one of the following:\n \"COORDINATES\" support for the annotated coordinates\n \"DESCRIPTION\" support for a broad concept of function such as that\n based on phenotype, genetic approach, biochemical function, pathway\n information, etc.\n \"EXISTENCE\" support for the known or inferred existence of the product\n where text is free text (see examples)\nExample \/experiment=\"5' RACE\"\n \/experiment=\"Northern blot [DOI: 12.3456\/FT.789.1.234-567.2010]\"\n \/experiment=\"heterologous expression system of Xenopus laevis\n oocytes [PMID: 12345678, 10101010, 987654]\"\n \/experiment=\"COORDINATES: 5' and 3' RACE\"\nComment detailed experimental details should not be included, and would\n normally be found in the cited publications; PMID, DOI and any \n experimental database ID is allowed to be used in \/experiment\n qualifier; Please also visit: https:\/\/www.insdc.org\/submitting-standards\/recommendations-vocabulary-insdc-experiment-qualifiers\/; \n value \"experimental evidence, no additional details recorded\"\n was used to replace instances of \/evidence=EXPERIMENTAL in\n December 2005\n\n\nQualifier \/focus\nDefinition identifies the source feature of primary biological\n interest for records that have multiple source features\n originating from different organisms and that are not\n transgenic.\nValue format none\nExample \/focus\nComment the source feature carrying the \/focus qualifier\n identifies the main organism of the entry, this\n determines: a) the name displayed in the organism\n lines, b) if no translation table is specified, the\n translation table, c) the DDBJ\/EMBL\/GenBank taxonomic\n division in which the entry will appear; only one\n source feature with \/focus is allowed in an entry; the\n \/focus and \/transgenic qualifiers are mutually exclusive\n in an entry.\n\n\nQualifier \/frequency=\nDefinition frequency of the occurrence of a feature\nValue format text representing the proportion of a population carrying the\n feature expressed as a fraction\nExample \/frequency=\"23\/108\"\n \/frequency=\"1 in 12\"\n \/frequency=\".85\"\n\n\nQualifier \/function=\nDefinition function attributed to a sequence\nValue format \"text\"\nExample function=\"essential for recognition of cofactor\"\nComment \/function is used when the gene name and\/or product name do not \n convey the function attributable to a sequence.\n\n\nQualifier \/gap_type=\nDefinition type of gap connecting components in records of a genome assembly, \n or the type of biological gap in a record that is part of a genome \n assembly;\nValue format \"between scaffolds\", \"within scaffold\", \"telomere\", \"centromere\",\n \"short arm\", \"heterochromatin\", \"repeat within scaffold\", \n \"repeat between scaffolds\", \"contamination\", \"unknown\"\nExample \/gap_type=\"between scaffolds\" \n \/gap_type=\"within scaffold\"\nComment This qualifier is used only for assembly_gap features and its values\n are controlled by the AGP Specification version 2.1:\n https:\/\/www.ncbi.nlm.nih.gov\/assembly\/agp\/AGP_Specification\/\n Please also visit: https:\/\/www.insdc.org\/submitting-standards\/controlled-vocabulary-gaptype-qualifier\/\n\n\nQualifier \/gene=\nDefinition symbol of the gene corresponding to a sequence region\nValue format \"text\"\nExample \/gene=\"ilvE\" \n\n\nQualifier \/gene_synonym=\nDefinition synonymous, replaced, obsolete or former gene symbol\nValue format \"text\"\nExample \/gene_synonym=\"Hox-3.3\"\n in a feature where \/gene=\"Hoxc6\"\nComment used where it is helpful to indicate a gene symbol\n synonym; when used, a primary gene symbol must always be\n indicated in \/gene or a \/locus_tag must be used.\n\n\nQualifier \/geo_loc_name=\nDefinition locality of isolation of the sequenced sample indicated in\n terms of political names for nations, oceans or seas, followed\n by regions and localities\nValue format \"<country_value>[:<region>][, <locality>]\" where \n country_value is any value from the controlled vocabulary at \n https:\/\/www.insdc.org\/submitting-standards\/country-qualifier-vocabulary\/ or \n a specified exemption from the missing values controlled vocabulary at \n the https:\/\/www.insdc.org\/submitting-standards\/missing-value-reporting\/.\nExample \/geo_loc_name=\"Canada:Vancouver\"\n \/geo_loc_name=\"France:Cote d'Azur, Antibes\"\n \/geo_loc_name=\"Atlantic Ocean:Charlie Gibbs Fracture Zone\"\n \/geo_loc_name=\"missing: lab stock\"\nComment Intended to provide a reference to the site where the source\n organism was isolated or sampled. Regions and localities should\n be indicated where possible. Note that the physical geography \n of the isolation or sampling site should be represented in\n \/isolation_source. From June 2024, the \/country\n qualifier will be transitioned to \/geo_loc_name. \/country may\n still be encountered on records prior to this date. \n\n\nQualifier \/germline\nDefinition the sequence presented in the entry has not undergone somatic\n rearrangement as part of an adaptive immune response; it is the\n unrearranged sequence that was inherited from the parental\n germline\nValue format none\nExample \/germline\nComment \/germline should not be used to indicate that the source of\n the sequence is a gamete or germ cell;\n \/germline and \/rearranged cannot be used in the same source\n feature;\n \/germline and \/rearranged should only be used for molecules that\n can undergo somatic rearrangements as part of an adaptive immune \n response; these are the T-cell receptor (TCR) and immunoglobulin\n loci in the jawed vertebrates, and the unrelated variable \n lymphocyte receptor (VLR) locus in the jawless fish (lampreys\n and hagfish);\n \/germline and \/rearranged should not be used outside of the\n Craniata (taxid=89593)\n\n\nQualifier \/haplogroup=\nDefinition name for a group of similar haplotypes that share some\n sequence variation. Haplogroups are often used to track\n\t\tmigration of population groups\nValue format \"text\"\nExample \/haplogroup=\"H*\"\n\n\nQualifier \/haplotype=\nDefinition name for a combination of alleles that are linked together\n on the same physical chromosome. In the absence of\n recombination, each haplotype is inherited as a unit, and may\n be used to track gene flow in populations.\nValue format \"text\"\nExample \/haplotype=\"Dw3 B5 Cw1 A1\"\n \/haplotype=\"M3 [.42]\"\n\n\nQualifier \/host=\nDefinition natural (as opposed to laboratory) host to the organism from\n which sequenced molecule was obtained\nValue format \"text\"\nExample \/host=\"Homo sapiens\"\n \/host=\"Homo sapiens 12 year old girl\"\n \/host=\"Rhizobium NGR234\"\n\n\nQualifier \/identified_by= \nDefinition name of the expert who identified the specimen taxonomically\nValue format \"text\" \nExample \/identified_by=\"John Burns\" \n\n\nQualifier \/inference=\nDefinition a structured description of non-experimental evidence that supports\n the feature identification or assignment.\n\nValue format \"[CATEGORY:]TYPE[ (same species)][:EVIDENCE_BASIS]\"\n \n where CATEGORY is one of the following:\n \"COORDINATES\" support for the annotated coordinates\n \"DESCRIPTION\" support for a broad concept of function such as that\n based on phenotype, genetic approach, biochemical function, pathway\n information, etc.\n \"EXISTENCE\" support for the known or inferred existence of the product\n \n where TYPE is one of the following:\n \"non-experimental evidence, no additional details recorded\"\n \"similar to sequence\"\n \"similar to AA sequence\"\n \"similar to DNA sequence\"\n \"similar to RNA sequence\"\n \"similar to RNA sequence, mRNA\"\n \"similar to RNA sequence, EST\"\n \"similar to RNA sequence, other RNA\"\n \"profile\"\n \"nucleotide motif\"\n \"protein motif\"\n \"ab initio prediction\"\n \"alignment\"\n \n where the optional text \"(same species)\" is included when the\n inference comes from the same species as the entry.\n \n where the optional \"EVIDENCE_BASIS\" is either a reference to a\n database entry (including accession and version) or an algorithm\n (including version) , eg 'INSD:AACN010222672.1', 'InterPro:IPR001900',\n 'ProDom:PD000600', 'Genscan:2.0', etc. and is structured \n \"[ALGORITHM][:EVIDENCE_DBREF[,EVIDENCE_DBREF]*[,...]]\"\n\nExample \/inference=\"COORDINATES:profile:tRNAscan:2.1\"\n \/inference=\"similar to DNA sequence:INSD:AY411252.1\"\n \/inference=\"similar to RNA sequence, mRNA:RefSeq:NM_000041.2\"\n \/inference=\"similar to DNA sequence (same\n species):INSD:AACN010222672.1\"\n \/inference=\"protein motif:InterPro:IPR001900\"\n \/inference=\"ab initio prediction:Genscan:2.0\"\n \/inference=\"alignment:Splign:1.0\"\n \/inference=\"alignment:Splign:1.26p:RefSeq:NM_000041.2,INSD:BC003557.1\"\n\nComment \/inference=\"non-experimental evidence, no additional details \n recorded\" was used to replace instances of \n \/evidence=NOT_EXPERIMENTAL in December 2005; any database ID can be\n used in \/inference= qualifier; recommentations for choice of resource \n acronym for[EVIDENCE_BASIS] are provided in the \/inference qualifier\n vocabulary recommendation document (https:\/\/www.insdc.org\/submitting-standards\/inference-qualifiers\/); \n\n\nQualifier \/isolate=\nDefinition individual isolate from which the sequence was obtained\nValue format \"text\"\nExample \/isolate=\"Patient #152\"\n \/isolate=\"DGGE band PSBAC-13\"\n\n\nQualifier \/isolation_source=\nDefinition describes the physical, environmental and\/or local\n geographical source of the biological sample from which\n the sequence was derived\nValue format \"text\"\nExamples \/isolation_source=\"rumen isolates from standard \n Pelleted ration-fed steer #67\"\n \/isolation_source=\"permanent Antarctic sea ice\"\n \/isolation_source=\"denitrifying activated sludge from\n carbon_limited continuous reactor\" \nComment used only with the source feature key;\n source feature keys containing an \/environmental_sample\n qualifier should also contain an \/isolation_source\n qualifier; the \/country qualifier should be used to \n describe the country and major geographical sub-region.\n\n\nQualifier \/lab_host=\nDefinition scientific name of the laboratory host used to propagate the\n source organism from which the sequenced molecule was obtained\nValue format \"text\"\nExample \/lab_host=\"Gallus gallus\"\n \/lab_host=\"Gallus gallus embryo\"\n \/lab_host=\"Escherichia coli strain DH5 alpha\"\n \/lab_host=\"Homo sapiens HeLa cells\"\nComment the full binomial scientific name of the host organism should\n be used when known; extra conditional information relating to\n the host may also be included\n\n\nQualifier \/lat_lon= \nDefinition geographical coordinates of the location where the specimen was\n collected \nValue format \"text\" \nExample \/lat_lon=\"47.94 N 28.12 W\" \n \/lat_lon=\"45.0123 S 4.1234 E\"\n\t\t\t\t\/lat_lon=\"6.385667 N 162.334778 W\"\n\t\t\t\t\/lat_lon=\"5.38566752 N 150.33477811 W\"\nComment degrees latitude and longitude in format \"d[d.dddddddd] N|S d[dd.dddddddd] W|E\"\n (see the examples)\n\n\nQualifier \/linkage_evidence=\nDefinition type of evidence establishing linkage across an \n\t\tassembly_gap. Only allowed to be used with assembly_gap features that \n have a \/gap_type value of \"within scaffold\", \"repeat within scaffold\" or \"contamination\"; \n Please note if \/gap-type=\"contamination\", \/linkage_evidence must be used and the value of\n \/linkage_evidence must be \"unspecified\".\nValue format \"pcr\", \"paired-ends\", \"align genus\", \"align xgenus\", \"align trnscpt\", \"within clone\", \n \"clone contig\", \"map\", \"strobe\", \"proximity ligation\", \"unspecified\"\nExample \/linkage_evidence=\"paired-ends\"\n\t\t\/linkage_evidence=\"within clone\"\nComment This qualifier is used only for assembly_gap features and its values are\n controlled by the AGP Specification version 2.1:\n https:\/\/www.ncbi.nlm.nih.gov\/assembly\/agp\/AGP_Specification\/\n Please also visit: https:\/\/www.insdc.org\/submitting-standards\/controlled-vocabulary-linkageevidence-qualifier\/.\n\n\nQualifier \/locus_tag=\nDefinition a submitter-supplied, systematic, stable identifier for a gene\n and its associated features, used for tracking purposes\nValue Format \"text\"(single token) \n but not \"<1-5 letters><5-9 digit integer>[.<integer>]\"\nExample \/locus_tag=\"ABC_0022\" \n \/locus_tag=\"A1C_00001\"\nComment \/locus_tag can be used with any feature that \/gene can be used with; \n identical \/locus_tag values may be used within an entry\/record, \n but only if the identical \/locus_tag values are associated \n with the same gene; in all other circumstances the \/locus_tag \n value must be unique within that entry\/record. Multiple \/locus_tag \n values are not allowed within one feature for entries created \n after 15-OCT-2004. \n If a \/locus_tag needs to be re-assigned the \/old_locus_tag qualifier \n should be used to store the old value. The \/locus_tag value should\n not be in a format which resembles INSD accession numbers, \n accession.version, or \/protein_id identifiers.\n\n\nQualifier \/macronuclear\nDefinition if the sequence shown is DNA and from an organism which \n undergoes chromosomal differentiation between macronuclear and\n micronuclear stages, this qualifier is used to denote that the \n sequence is from macronuclear DNA. \nValue format none\nExample \/macronuclear\n\n\nQualifier \/map=\nDefinition genomic map position of feature\nValue format \"text\"\nExample \/map=\"8q12-q13\"\n\n\nQualifier \/mating_type=\nDefinition mating type of the organism from which the sequence was\n obtained; mating type is used for prokaryotes, and for\n eukaryotes that undergo meiosis without sexually dimorphic\n gametes\nValue format \"text\"\nExamples \/mating_type=\"MAT-1\"\n \/mating_type=\"plus\"\n \/mating_type=\"-\"\n \/mating_type=\"odd\"\n \/mating_type=\"even\"\nComment \/mating_type=\"male\" and \/mating_type=\"female\" are\n valid in the prokaryotes, but not in the eukaryotes;\n for more information, see the entry for \/sex.\n\n\nQualifier \/metagenome_source\nDefinition sequences from a Metagenome Assembled Genome (MAG), i.e a single-taxon assembly \n drawn from a binned metagenome, are specified with this qualifier to indicate\n that the assembly is derived from a metagenomic source, rather than from an isolated organism.\n Where this qualifier is present it must contain the word \"metagenome\" and must exist in the \n NCBI taxonomy database: https:\/\/www.ncbi.nlm.nih.gov\/Taxonomy\/\nValue format \"text\"\nExamples \/metagenome_source=\"human gut metagenome\"\n \/metagenome_source=\"soil metagenome\"\nComment the qualifier \/metagenome_source is mandatory when a single-taxon sequence is derived from a metagenome;\n sequences with a \/metagenome_source require also an \/environmental_sample qualifier.\n\n\nQualifier \/mobile_element_type=\nDefinition type and name or identifier of the mobile element which is\n described by the parent feature\nValue format \"<mobile_element_type>[:<mobile_element_name>]\" where\n mobile_element_type is one of the following:\n \"transposon\", \"retrotransposon\", \"integron\", \n \"insertion sequence\", \"non-LTR retrotransposon\", \n \"SINE\", \"MITE\", \"LINE\", \"other\".\nExample \/mobile_element_type=\"transposon:Tnp9\"\nComment \/mobile_element_type is legal on mobile_element feature key only. \n Mobile element should be used to represent both elements which \n are currently mobile, and those which were mobile in the past. \n Value \"other\" requires a mobile_element_name. \n\n\nQualifier \/mod_base=\nDefinition abbreviation for a modified nucleotide base\nValue format modified_base\nExample \/mod_base=m5c\nComment modified nucleotides not found in the restricted vocabulary\n list can be annotated by entering '\/mod_base=OTHER' with\n '\/note=\"name of modified base\"'\n\n\nQualifier \/mol_type=\nDefinition in vivo molecule type of sequence \nValue format \"genomic DNA\", \"genomic RNA\", \"mRNA\", \"tRNA\", \"rRNA\", \"other\n RNA\", \"other DNA\", \"transcribed RNA\", \"viral cRNA\", \"unassigned\n DNA\", \"unassigned RNA\"\nExample \/mol_type=\"genomic DNA\"\nComment all values refer to the in vivo or synthetic molecule for\n primary entries and the hypothetical molecule in Third Party\n Annotation entries; the value \"genomic DNA\" does not imply that\n the molecule is nuclear (e.g. organelle and plasmid DNA should\n be described using \"genomic DNA\"); ribosomal RNA genes should be\n described using \"genomic DNA\"; \"rRNA\" should only be used if the\n ribosomal RNA molecule itself has been sequenced; \/mol_type is\n mandatory on every source feature key; all \/mol_type values\n within one entry\/record must be the same; values \"other RNA\" and\n \"other DNA\" should be applied to synthetic molecules, values\n \"unassigned DNA\", \"unassigned RNA\" should be applied where in\n vivo molecule is unknown\n Please also visit:\n https:\/\/www.insdc.org\/submitting-standards\/controlled-vocabulary-moltype-qualifier\/.\n\n\nQualifier \/ncRNA_class=\nDefinition a structured description of the classification of the\n non-coding RNA described by the ncRNA parent key\nValue format \"TYPE\"\nExample \/ncRNA_class=\"miRNA\"\n \/ncRNA_class=\"siRNA\"\n \/ncRNA_class=\"scRNA\" \nComment TYPE is a term taken from the INSDC controlled vocabulary for ncRNA\n classes. For a complete list of supported values, please see:\n https:\/\/www.insdc.org\/submitting-standards\/ncrna-vocabulary\/;\n ncRNA classes not yet in the INSDC \/ncRNA_class controlled\n vocabulary can be annotated by entering\n '\/ncRNA_class=\"other\"' with either '\/product=\"[name of the product]\"' OR\n '\/note=\"[brief explanation of novel ncRNA_class]\"';\n\n\nQualifier \/note=\nDefinition any comment or additional information\nValue format \"text\"\nExample \/note=\"This qualifier is equivalent to a comment.\"\n\n\nQualifier \/number=\nDefinition a number to indicate the order of genetic elements (e.g.,\n exons or introns) in the 5' to 3' direction\nValue format unquoted text (single token) \nExample \/number=4\n \/number=6B\nComment text limited to integers, letters or combination of integers and\/or \n letters represented as an unquoted single token (e.g. 5a, XIIb);\n any additional terms should be included in \/standard_name.\n Example: \/number=2A\n \/standard_name=\"long\"\n\n\nQualifier \/old_locus_tag=\nDefinition feature tag assigned for tracking purposes \nValue Format \"text\" (single token)\nExample \/old_locus_tag=\"RSc0382\"\n \/locus_tag=\"YPO0002\"\nComment \/old_locus_tag can be used with any feature where \/gene is valid and \n where a \/locus_tag qualifier is present. \n Identical \/old_locus_tag values may be used within an entry\/record, \n but only if the identical \/old_locus_tag values are associated \n with the same gene; in all other circumstances the \/old_locus_tag \n value must be unique within that entry\/record. \n Multiple\/old_locus_tag qualifiers with distinct values are \n allowed within a single feature; \/old_locus_tag and \/locus_tag \n values must not be identical within a single feature.\n\n\nQualifier \/operon=\nDefinition name of the group of contiguous genes transcribed into a \n single transcript to which that feature belongs.\nValue format \"text\"\nExample \/operon=\"lac\"\n\n\nQualifier \/organelle= \nDefinition type of membrane-bound intracellular structure from which the \n sequence was obtained\nValue format chromatophore, hydrogenosome, mitochondrion, nucleomorph, plastid,\n mitochondrion:kinetoplast, plastid:chloroplast, plastid:apicoplast,\n plastid:chromoplast, plastid:cyanelle, plastid:leucoplast, plastid:proplastid\nExamples \/organelle=\"chromatophore\"\n \/organelle=\"hydrogenosome\"\n \/organelle=\"mitochondrion\"\n \/organelle=\"nucleomorph\"\n \/organelle=\"plastid\"\n \/organelle=\"mitochondrion:kinetoplast\"\n \/organelle=\"plastid:chloroplast\"\n \/organelle=\"plastid:apicoplast\"\n \/organelle=\"plastid:chromoplast\"\n \/organelle=\"plastid:cyanelle\"\n \/organelle=\"plastid:leucoplast\"\n \/organelle=\"plastid:proplastid\"\nComments modifier text limited to values from controlled list\n Please also visit: http:\/\/www.insdc.org\/controlled-vocabulary-organelle-qualifier\/.\n\n\nQualifier \/organism=\nDefinition scientific name or higher-level classification of the \n organism or agent that provided the sequenced genetic \n material.\nValue format \"text\"\nExamples \/organism=\"Homo sapiens\"\n \/organism=\"Lactobacillaceae bacterium\"\n \/organism=\"West Nile virus\"\n \/organism=\"synthetic construct\"\n \/organism=\"uncultured bacterium\"\nComment includes names for Prokaryotes, Eukaryotes, Viruses, synthetic \n sequences, uncultured samples, and unclassified organisms. \n The organism name which appears on the OS or ORGANISM line \n will match the value of the \/organism qualifier of the \n source key in the simplest case of a one-source sequence. \n\nQualifier \/partial\nDefinition differentiates between complete regions and partial ones\nValue format none\nExample \/partial\nComment not to be used for new entries from 15-DEC-2001;\n use '<' and '>' signs in the location descriptors to\n indicate that the sequence is partial. \n\n\nQualifier \/PCR_conditions=\nDefinition description of reaction conditions and components for PCR \nValue format \"text\" \nExample \/PCR_conditions=\"Initial denaturation:94degC,1.5min\"\nComment used with primer_bind key\n\n\nQualifier \/PCR_primers=\nDefinition PCR primers that were used to amplify the sequence.\n A single \/PCR_primers qualifier should contain all the primers used \n for a single PCR reaction. If multiple forward or reverse primers are \n present in a single PCR reaction, multiple sets of fwd_name\/fwd_seq \n or rev_name\/rev_seq values will be present.\nValue format \/PCR_primers=\"[fwd_name: XXX1, ]fwd_seq: xxxxx1,[fwd_name: XXX2,]\n fwd_seq: xxxxx2, [rev_name: YYY1, ]rev_seq: yyyyy1, \n [rev_name: YYY2, ]rev_seq: yyyyy2\"\n\nExample \/PCR_primers=\"fwd_name: CO1P1, fwd_seq: ttgattttttggtcayccwgaagt,\n rev_name: CO1R4, rev_seq: ccwvytardcctarraartgttg\"\n \/PCR_primers=\" fwd_name: hoge1, fwd_seq: cgkgtgtatcttact, \n rev_name: hoge2, rev_seq: cg<i>gtgtatcttact\" \n \/PCR_primers=\"fwd_name: CO1P1, fwd_seq: ttgattttttggtcayccwgaagt,\n fwd_name: CO1P2, fwd_seq: gatacacaggtcayccwgaagt, rev_name: CO1R4, \n rev_seq: ccwvytardcctarraartgttg\" \n\nComment fwd_seq and rev_seq are both mandatory; fwd_name and rev_name are\n both optional. Both sequences should be presented in 5'>3' order. \n The sequences should be given in the IUPAC degenerate-base alphabet,\n except for the modified bases; those must be enclosed within angle\n brackets <> \n\n\nQualifier \/phenotype=\nDefinition phenotype conferred by the feature, where phenotype is defined as a \n physical, biochemical or behavioural characteristic or set of \n characteristics\nValue format \"text\"\nExample \/phenotype=\"erythromycin resistance\"\n\n\n\nQualifier \/plasmid=\nDefinition name of naturally occurring plasmid from which the sequence was \n obtained, where plasmid is defined as an independently replicating\n genetic unit that cannot be described by \/chromosome or \/segment\nValue format \"text\"\nExample \/plasmid=\"C-589\"\n\n\n\nQualifier \/pop_variant=\nDefinition name of subpopulation or phenotype of the sample from which the sequence\n was derived \nValue format \"text\"\nExample \/pop_variant=\"pop1\" \n \/pop_variant=\"Bear Paw\"\n\n\n\nQualifier \/product=\nDefinition name of the product associated with the feature, e.g. the mRNA of an \n mRNA feature, the polypeptide of a CDS, the mature peptide of a \n mat_peptide, etc.\nValue format \"text\"\nExample \/product=\"trypsinogen\" (when qualifier appears in CDS feature)\n \/product=\"trypsin\" (when qualifier appears in mat_peptide feature)\n \/product=\"XYZ neural-specific transcript\" (when qualifier appears in \n mRNA feature)\n\n\nQualifier \/protein_id=\nDefinition protein identifier, issued by International collaborators.\n this qualifier consists of a stable ID portion (accessioned data\n before the end of 2018 uses a 3+5 format; from the end of 2018 \n new accessions may be extended to a 3+7 accession format with 3 position\n letters and 7 numbers) plus a version number after the decimal point.\nValue format <identifier>\nExample \/protein_id=\"AAA12345.1\"\n \/protein_id=\"AAA1234567.1\"\nComment when the protein sequence encoded by the CDS changes, only \n the version number of the \/protein_id value is incremented; \n the stable part of the \/protein_id remains unchanged and as a\n result will permanently be associated with a given protein;\n this qualifier is valid only on CDS features which translate\n into a valid protein. \n\n\nQualifier \/proviral\nDefinition this qualifier is used to flag sequence obtained from a virus or\n phage that is integrated into the genome of another organism\nValue format none\nExample \/proviral\n\n\n\nQualifier \/pseudo\nDefinition indicates that this feature is a non-functional version of the\n element named by the feature key\nValue format none\nExample \/pseudo\nComment The qualifier \/pseudo should be used to describe non-functional \n genes that are not formally described as pseudogenes, e.g. CDS \n has no translation due to other reasons than pseudogenisation events.\n Other reasons may include sequencing or assembly errors.\n In order to annotate pseudogenes the qualifier \/pseudogene= must be\n used indicating the TYPE which can be taken from the INSDC controlled vocabulary \n for pseudogenes.\n\n\n\nQualifier \/pseudogene=\nDefinition indicates that this feature is a pseudogene of the element named\n by the feature key\nValue format \"TYPE\"\n where TYPE is one of the following:\n processed, unprocessed, unitary, allelic, unknown\n\nExample \/pseudogene=\"processed\"\n \/pseudogene=\"unprocessed\"\n \/pseudogene=\"unitary\"\n \/pseudogene=\"allelic\"\n \/pseudogene=\"unknown\"\n\nComment TYPE is a term taken from the INSDC controlled vocabulary for pseudogenes\n (https:\/\/www.insdc.org\/submitting-standards\/pseudogene-qualifier-vocabulary\/):\n\n processed: the pseudogene has arisen by reverse transcription of a \n mRNA into cDNA, followed by reintegration into the genome. Therefore,\n it has lost any intron\/exon structure, and it might have a pseudo-polyA-tail.\n\n unprocessed: the pseudogene has arisen from a copy of the parent gene by duplication\n followed by accumulation of random mutations. The changes, compared to their\n functional homolog, include insertions, deletions, premature stop codons, frameshifts\n and a higher proportion of non-synonymous versus synonymous substitutions.\n\n unitary: the pseudogene has no parent. It is the original gene, which is\n functional is some species but disrupted in some way (indels, mutation, \n recombination) in another species or strain.\n\n allelic: a (unitary) pseudogene that is stable in the population but\n importantly it has a functional alternative allele also in the population. i.e.,\n one strain may have the gene, another strain may have the pseudogene.\n MHC haplotypes have allelic pseudogenes.\n\n unknown: the submitter does not know the method of pseudogenisation.\n\n\n\nQualifier \/rearranged\nDefinition the sequence presented in the entry has undergone somatic\n rearrangement as part of an adaptive immune response; it is not\n the unrearranged sequence that was inherited from the parental\n germline\nValue format none\nExample \/rearranged\nComment \/rearranged should not be used to annotate chromosome\n rearrangements that are not involved in an adaptive immune\n response;\n \/germline and \/rearranged cannot be used in the same source\n feature;\n \/germline and \/rearranged should only be used for molecules that\n can undergo somatic rearrangements as part of an adaptive immune \n response; these are the T-cell receptor (TCR) and immunoglobulin\n loci in the jawed vertebrates, and the unrelated variable \n lymphocyte receptor (VLR) locus in the jawless fish (lampreys\n and hagfish);\n \/germline and \/rearranged should not be used outside of the\n Craniata (taxid=89593)\n\n\nQualifier\t\/recombination_class\nDefinition a structured description of the classification of recombination \n hotspot region within a sequence\nValue format \"TYPE\"\nExample \/recombination_class=\"meiotic\"\n \/recombination_class=\"chromosome_breakpoint\"\nComment TYPE is a term taken from the INSDC controlled vocabulary for recombination classes\n (https:\/\/www.insdc.org\/submitting-standards\/controlled-vocabulary-recombination-class\/); in DEC 2017,\n the following terms were valid:\n\n \"meiotic\"\n \"mitotic\"\n \"non_allelic_homologous\"\n \"chromosome_breakpoint\"\n \"other\"\n\n recombination classes not yet in the INSDC \/recombination_class controlled vocabulary\n can be annotated by entering \/recombination_class=\"other\" with\n \/note=\"[brief explanation of novel \/recombination_class]\";\t\n\n\nQualifier\t\/regulatory_class\nDefinition a structured description of the classification of transcriptional,\n translational, replicational, recombination and chromatin structure related \n regulatory elements in a sequence \nValue format \"TYPE\"\nExample \/regulatory_class=\"promoter\"\n \/regulatory_class=\"enhancer\"\n \/regulatory_class=\"ribosome_binding_site\"\nComment TYPE is a term taken from the INSDC controlled vocabulary for regulatory classes. For\n a complete list of supported values, please see:\n https:\/\/www.insdc.org\/submitting-standards\/controlled-vocabulary-regulatoryclass\/;\n regulatory classes not yet in the INSDC \/regulatory_class controlled vocabulary\n can be annotated by entering \/regulatory_class=\"other\" with\n \/note=\"[brief explanation of novel regulatory_class]\";\n\n\nQualifier \/replace=\nDefinition indicates that the sequence identified a feature's intervals is \n replaced by the sequence shown in \"text\"; if no sequence is \n contained within the qualifier, this indicates a deletion.\nValue format \"text\"\nExample \/replace=\"a\"\n \/replace=\"\"\n\n\nQualifier \/ribosomal_slippage\nDefinition during protein translation, certain sequences can program\n ribosomes to change to an alternative reading frame by a \n mechanism known as ribosomal slippage \nValue format none \nExample \/ribosomal_slippage \nComment a join operator,e.g.: [join(486..1784,1787..4810)] should be used \n in the CDS spans to indicate the location of ribosomal_slippage \n\n\nQualifier \/rpt_family=\nDefinition type of repeated sequence; \"Alu\" or \"Kpn\", for example\nValue format \"text\"\nExample \/rpt_family=\"Alu\"\n\n\nQualifier \/rpt_type=\nDefinition structure and distribution of repeated sequence\nValue format tandem, direct, inverted, flanking, nested, dispersed, terminal, \n long_terminal_repeat, non_ltr_retrotransposon_polymeric_tract, \n centromeric_repeat, telomeric_repeat, x_element_combinatorial_repeat,\n y_prime_element and other\nExample \/rpt_type=INVERTED\nComment the values are case-insensitive, i.e. both \"INVERTED\" and \"inverted\" \n are valid; For the most current list of allowed values and their definitions please visit:\n https:\/\/www.insdc.org\/submitting-standards\/controlled-vocabulary-rpttype-qualifier\/.\n\n\nQualifier \/rpt_unit_range=\nDefinition identity of a repeat range\nValue format <base_range>\nExample \/rpt_unit_range=202..245\nComment used to indicate the base range of the sequence that constitutes \n a repeated sequence specified by the feature keys oriT and\n repeat_region; qualifiers \/rpt_unit_range and \/rpt_unit_seq\n replaced qualifier \/rpt_unit in December 2005\n\n\nQualifier \/rpt_unit_seq=\nDefinition identity of a repeat sequence\nValue format \"text\"\nExample \/rpt_unit_seq=\"aagggc\"\n \/rpt_unit_seq=\"ag(5)tg(8)\"\n \/rpt_unit_seq=\"(AAAGA)6(AAAA)1(AAAGA)12\"\nComment used to indicate the literal sequence that constitutes a\n repeated sequence specified by the feature keys oriT and\n repeat_region; qualifiers \/rpt_unit_range and \/rpt_unit_seq\n replaced qualifier \/rpt_unit in December 2005\n\n\nQualifier \/satellite=\nDefinition identifier for a satellite DNA marker, compose of many tandem\n repeats (identical or related) of a short basic repeated unit;\nValue format \"<satellite_type>[:<class>][ <identifier>]\"\n where satellite_type is one of the following \n \"satellite\", \"microsatellite\", \"minisatellite\"\nExample \/satellite=\"satellite: S1a\"\n \/satellite=\"satellite: alpha\"\n \/satellite=\"satellite: gamma III\"\n \/satellite=\"microsatellite: DC130\"\nComment many satellites have base composition or other properties\n that differ from those of the rest of the genome that allows\n them to be identified.\n Please also visit: https:\/\/www.insdc.org\/submitting-standards\/controlled-vocabulary-satellite-qualifier\/.\n\n\nQualifier \/segment=\nDefinition name of viral or phage segment sequenced\nValue format \"text\"\nExample \/segment=\"6\"\n\n\nQualifier \/serotype=\nDefinition serological variety of a species characterized by its\n antigenic properties\nValue format \"text\"\nExample \/serotype=\"B1\"\nComment used only with the source feature key;\n the Bacteriological Code recommends the use of the\n term 'serovar' instead of 'serotype' for the \n prokaryotes; see the International Code of Nomenclature\n of Bacteria (1990 Revision) Appendix 10.B \"Infraspecific\n Terms\".\n\n\nQualifier \/serovar=\nDefinition serological variety of a species (usually a prokaryote)\n characterized by its antigenic properties\nValue format \"text\"\nExample \/serovar=\"O157:H7\"\nComment used only with the source feature key;\n the Bacteriological Code recommends the use of the\n term 'serovar' instead of 'serotype' for prokaryotes;\n see the International Code of Nomenclature of Bacteria\n (1990 Revision) Appendix 10.B \"Infraspecific Terms\".\n\n\nQualifier \/sex=\nDefinition sex of the organism from which the sequence was obtained;\n sex is used for eukaryotic organisms that undergo meiosis\n and have sexually dimorphic gametes\nValue format \"text\"\nExamples \/sex=\"female\"\n \/sex=\"male\"\n \/sex=\"hermaphrodite\"\n \/sex=\"unisexual\"\n \/sex=\"bisexual\"\n \/sex=\"asexual\"\n \/sex=\"monoecious\" [or monecious]\n \/sex=\"dioecious\" [or diecious]\nComment \/sex should be used (instead of \/mating_type)\n in the Metazoa, Embryophyta, Rhodophyta & Phaeophyceae;\n \/mating_type should be used (instead of \/sex)\n in the Bacteria, Archaea & Fungi;\n neither \/sex nor \/mating_type should be used\n in the viruses;\n outside of the taxa listed above, \/mating_type\n should be used unless the value of the qualifier\n is taken from the vocabulary given in the examples\n above\n\n\nQualifier \/specimen_voucher=\nDefinition identifier for the specimen from which the nucleic acid\n sequenced was obtained\nValue format \/specimen_voucher=\"[<institution-code>:[<collection-code>:]]<specimen_id>\"\nExample \/specimen_voucher=\"UAM:Mamm:52179\"\n \/specimen_voucher=\"AMCC:101706\"\n \/specimen_voucher=\"USNM:field series 8798\"\n \/specimen_voucher=\"personal:Dan Janzen:99-SRNP-2003\"\n \/specimen_voucher=\"99-SRNP-2003\"\nComment the \/specimen_voucher qualifier is intended to annotate a\n reference to the physical specimen that remains after the\n sequence has been obtained;\n if the specimen was destroyed in the process of sequencing,\n electronic images (e-vouchers) are an adequate substitute for a\n physical voucher specimen; ideally the specimens will be\n deposited in a curated museum, herbarium, or frozen tissue\n collection, but often they will remain in a personal or\n laboratory collection for some time before they are deposited in\n a curated collection;\n there are three forms of specimen_voucher qualifiers; if the\n text of the qualifier includes one or more colons it is a\n 'structured voucher'; structured vouchers include\n institution-codes (and optional collection-codes) taken from a\n controlled vocabulary maintained by the INSDC that denotes the\n museum or herbarium collection where the specimen resides;\n Please also visit: https:\/\/www.insdc.org\/submitting-standards\/controlled-vocabulary-specimenvoucher-qualifier\/.\n\n\nQualifier \/standard_name=\nDefinition accepted standard name for this feature\nValue format \"text\"\nExample \/standard_name=\"dotted\"\nComment use \/standard_name to give full gene name, but use \/gene to\n give gene symbol (in the above example \/gene=\"Dt\").\n\n\nQualifier \/strain=\nDefinition strain from which sequence was obtained\nValue format \"text\"\nExample \/strain=\"BALB\/c\"\nComment entries including \/strain must not include\n the \/environmental_sample qualifier\n\n\nQualifier \/sub_clone=\nDefinition sub-clone from which sequence was obtained\nValue format \"text\"\nExample \/sub_clone=\"lambda-hIL7.20g\"\nComment the comments on \/clone apply to \/sub_clone\n\n\nQualifier \/submitter_seqid=\nDefinition identifier attributed to each sequence within an assembly. This identifier \n is appropriate for WGS, TSA, TLS and CON records. The submitter_seqid should be \n unique within the context of a single set of assembled sequences.\nValue format \"text\"\nExample \/submitter_seqid=\"NODE_1\"\nComment The length of the value should be limited to <51 characters. Spaces, greater than (>),\n left\/right square brackets ([ ]) and vertical bar (|) in addition to\n double quotation marks (\") can not be used for the value of \/submitter_seqid qualifier.\n Please also visit: https:\/\/www.insdc.org\/submitting-standards\/submitterseqid-qualifier-recommendation-document\/.\n\n\nQualifier \/sub_species=\nDefinition name of sub-species of organism from which sequence was\n obtained\nValue format \"text\"\nExample \/sub_species=\"lactis\"\n\n\nQualifier \/sub_strain=\nDefinition name or identifier of a genetically or otherwise modified \n strain from which sequence was obtained, derived from a \n parental strain (which should be annotated in the \/strain \n qualifier).sub_strain from which sequence was obtained\nValue format \"text\"\nExample \/sub_strain=\"abis\"\nComment if the parental strain is not given, this should\n be annotated in the strain qualifier instead of sub_strain.\n Either:\n \/strain=\"K-12\"\n \/sub_strain=\"MG1655\"\n or:\n \/strain=\"MG1655\"\n\n\nQualifier \/tag_peptide=\nDefinition base location encoding the polypeptide for proteolysis tag of \n tmRNA and its termination codon;\nValue format <base_range>\nExample \/tag_peptide=90..122\nComment it is recommended that the amino acid sequence corresponding\n to the \/tag_peptide be annotated by describing a 5' partial \n CDS feature; e.g. CDS <90..122;\n\n\nQualifier \/tissue_lib=\nDefinition tissue library from which sequence was obtained\nValue format \"text\"\nExample \/tissue_lib=\"tissue library 772\"\n\n\nQualifier \/tissue_type=\nDefinition tissue type from which the sequence was obtained\nValue format \"text\"\nExample \/tissue_type=\"liver\"\n\n\nQualifier \/transgenic\nDefinition identifies the source feature of the organism which was \n the recipient of transgenic DNA.\nValue format none\nExample \/transgenic\nComment transgenic sequences must have at least two source feature keys; \n the source feature key having the \/transgenic qualifier must \n span the whole sequence; the source feature carrying the \n \/transgenic qualifier identifies the main organism of the entry, \n this determines: a) the name displayed in the organism lines, \n b) if no translation table is specified, the translation table;\n only one source feature with \/transgenic is allowed in an entry; \n the \/focus and \/transgenic qualifiers are mutually exclusive in \n an entry.\n\n\nQualifier \/translation=\nDefinition automatically generated one-letter abbreviated amino acid\n sequence derived from either the universal genetic code or the\n table as specified in \/transl_table and as determined by an\n exception in the \/transl_except qualifier\nValue format IUPAC one-letter amino acid abbreviation, \"X\" is to be used\n for AA exceptions.\nExample \/translation=\"MASTFPPWYRGCASTPSLKGLIMCTW\"\nComment to be used with CDS feature only; this is a mandatory qualifier \n in the CDS feature key except where \/pseudogene=\"TYPE\" or \/pseudo\n is shown; see \/transl_table for definition and location of genetic\n code tables. \n\n\nQualifier \/transl_except=\nDefinition translational exception: single codon the translation of which\n does not conform to genetic code defined by \/organism or \n \/transl_table.\nValue format (pos:<location>,aa:<amino_acid>) where amino_acid is the\n amino acid coded by the codon at the base_range position\nExample \/transl_except=(pos:213..215,aa:Trp)\n \/transl_except=(pos:1017,aa:TERM)\n \/transl_except=(pos:2000..2001,aa:TERM)\n \/transl_except=(pos:X22222:15..17,aa:Ala)\nComment if the amino acid is not on the restricted vocabulary list use\n e.g., '\/transl_except=(pos:213..215,aa:OTHER)' with\n '\/note=\"name of unusual amino acid\"';\n for modified amino-acid selenocysteine use three letter code\n 'Sec' (one letter code 'U' in amino-acid sequence)\n \/transl_except=(pos:1002..1004,aa:Sec);\n for partial termination codons where TAA stop codon is\n completed by the addition of 3' A residues to the mRNA\n either a single base_position or a base_range is used, e.g.\n if partial stop codon is a single base:\n \/transl_except=(pos:1017,aa:TERM)\n if partial stop codon consists of two bases:\n \/transl_except=(pos:2000..2001,aa:TERM) with\n '\/note='stop codon completed by the addition of 3' A residues \n to the mRNA'.\n\n\nQualifier \/transl_table=\nDefinition definition of genetic code table used if other than universal\n genetic code table. Tables used are described at the specified URLs in appendix IV.\nValue format <integer> 1=universal table 1;2=non-universal table 2;...\nExample \/transl_table=4\nComment genetic code exceptions outside range of specified tables are\n reported in \/transl_except qualifier.\n\n\nQualifier \/trans_splicing \nDefinition indicates that exons from two RNA molecules are ligated in\n intermolecular reaction to form mature RNA \nValue format none \nExample \/trans_splicing \nComment should be used on features such as CDS, mRNA and other features\n that are produced as a result of a trans-splicing event. This\n qualifier should be used only when the splice event is indicated in\n the \"join\" operator, eg join(complement(69611..69724),139856..140087)\n\n\nQualifier \/type_material=\nDefinition indicates that the organism from which this sequence was obtained is\n a nomenclatural type of the species (or subspecies) corresponding with\n the \/organism identified in the sequence entry\nValue format \"<type-of-type> of <organism name>\"\n where type-of-type is one of the following:\n type strain, neotype strain, holotype, paratype, neotype, allotype, hapanotype,\n syntype, lectotype, paralectotype, isotype, epitype, isosyntype, ex-type,\n reference strain, type material;\nExample \/type_material=\"type strain of Escherichia coli\"\n \/type_material=\"holotype of Cercopitheus lomamiensis\"\n \/type_material=\"paratype of Cercopitheus lomamiensis\"\nComment <type-of-type> is taken from the INSDC controlled vocabularly for \/type_material\n at: https:\/\/www.insdc.org\/submitting-standards\/controlled-vocabulary-typematerial-qualifer\/\n <organism name> should be listed as the scientific name \n (or as a synonym) at the species (or subspecies) node in the taxonomy database.\n INSDC will automatically populate this qualifier from the NCBI taxonomy database to\n flag sequences of form type in the INSDC databases (ENA\/GenBank\/DDBJ).\n\n\nQualifier \/variety=\nDefinition variety (= varietas, a formal Linnaean rank) of organism \n from which sequence was derived.\nValue format \"text\"\nExample \/variety=\"insularis\"\nComment use the cultivar qualifier for cultivated plant \n varieties, i.e., products of artificial selection;\n varieties other than plant and fungal variatas should be \n annotated via \/note, e.g. \/note=\"breed:Cukorova\"\n\n\n\n \n<a name=\"7.4\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7.4 Appendix IV: Controlled vocabularies<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">This appendix contains information on the restricted vocabulary fields used in \nthe Feature Table. The information contained in this appendix is subject to \nchange, please contact the database staff for the most recent information \nconcerning controlled vocabularies. This appendix is organized as follows: \n\nAuthority The organization with authority to define the vocabulary\nReference Publications of (or about) the vocabulary\nContact Name of database staff responsible for maintaining \n the database copy of the vocabulary\nScope Feature Table qualifiers which take members of this vocabulary \n as values\nListing A listing of the current vocabulary with definitions or\n explanations\nThis appendix includes reference lists for the following controlled vocabulary \nfields: \n- Nucleotide base codes (IUPAC)\n- Modified base abbreviations \n- Amino acid abbreviations \n- Modified and unusual Amino Acids \n- Genetic Code Tables \n- Country Names\n \n<a name=\"7.4.1\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7.4.1 Nucleotide base codes (IUPAC)<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Authority Nomenclature Committee of the International Union of \n Biochemistry \nReference Cornish-Bowden, A. Nucl Acid Res 13, 3021-3030 (1985)\nContact EMBL-EBI\nScope Location descriptors \n\nListing\n\n Symbol Meaning\n ------ -------\n\n a a; adenine\n c c; cytosine\n g g; guanine\n t t; thymine in DNA; uracil in RNA\n m a or c\n r a or g\n w a or t\n s c or g\n y c or t\n k g or t\n v a or c or g; not t\n h a or c or t; not g\n d a or g or t; not c\n b c or g or t; not a\n n a or c or g or t\n\n\n<a name=\"7.4.2\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7.4.2 Modified base abbreviations<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Authority Sprinzl, M. and Gauss, D.H.\nReference Sprinzl, M. and Gauss, D.H. Nucl Acid Res 10, r1 (1982).\n (note that in Cornish_Bowden, A. Nucl Acid Res 13, 3021-3030\n (1985) the IUPAC-IUB declined to recommend a set of\n abbreviations for modified nucleotides)\nContact NCBI\nScope \/mod_base\n\n Abbreviation Modified base description\n ------------ -------------------------\n ac4c 4-acetylcytidine\n chm5u 5-(carboxyhydroxylmethyl)uridine\n cm 2'-O-methylcytidine\n cmnm5s2u 5-carboxymethylaminomethyl-2-thiouridine\n cmnm5u 5-carboxymethylaminomethyluridine\n dhu dihydrouridine\n fm 2'-O-methylpseudouridine\n gal q beta-D-galactosylqueuosine\n gm 2'-O-methylguanosine\n i inosine\n i6a N6-isopentenyladenosine\n m1a 1-methyladenosine\n m1f 1-methylpseudouridine\n m1g 1-methylguanosine\n m1i 1-methylinosine\n m22g 2,2-dimethylguanosine\n m2a 2-methyladenosine\n m2g 2-methylguanosine\n m3c 3-methylcytidine\n m4c N4-methylcytosine\n m5c 5-methylcytidine\n m6a N6-methyladenosine\n m7g 7-methylguanosine\n mam5u 5-methylaminomethyluridine\n mam5s2u 5-methylaminomethyl-2-thiouridine\n man q beta-D-mannosylqueuosine\n mcm5s2u 5-methoxycarbonylmethyl-2-thiouridine\n mcm5u 5-methoxycarbonylmethyluridine\n mo5u 5-methoxyuridine\n ms2i6a 2-methylthio-N6-isopentenyladenosine\n ms2t6a N-((9-beta-D-ribofurnosyl-2-methylthiopurin-6-yl)carbamoyl)threonine\n mt6a N-((9-beta-D-ribofuranosylpurine-6-yl)N-methyl-carbamoyl)threonine\n mv uridine-5-oxoacetic acid methylester\n o5u uridine-5-oxyacetic acid (v)\n osyw wybutoxosine\n p pseudouridine\n q queuosine\n s2c 2-thiocytidine\n s2t 5-methyl-2-thiouridine\n s2u 2-thiouridine\n s4u 4-thiouridine\n m5u 5-methyluridine\n t6a N-((9-beta-D-ribofuranosylpurine-6-yl)carbamoyl)threonine\n tm 2'-O-methyl-5-methyluridine\n um 2'-O-methyluridine\n yw wybutosine\n x 3-(3-amino-3-carboxypropyl)uridine, (acp3)u\n OTHER (requires \/note= qualifier)\n\n\n<a name=\"7.4.3\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7.4.3 Amino acid abbreviations<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Authority IUPAC-IUB Joint Commission on Biochemical Nomenclature.\nReference IUPAC-IUB Joint Commission on Biochemical Nomenclature.\n Nomenclature and Symbolism for Amino Acids and\n Peptides.\n Eur. J. Biochem. 138:9-37(1984).\n IUPAC-IUBMB JCBN Newsletter, 1999 \n http:\/\/www.chem.qmul.ac.uk\/iubmb\/newsletter\/1999\/item3.html\nScope \/anticodon, \/transl_except\nContact EMBL-EBI\n\nListing (note that the abbreviations are legal values for amino acids, not the full names)\n Abbreviation Amino acid name\n ------------ ---------------\n\n Ala A Alanine\n Arg R Arginine\n Asn N Asparagine\n Asp D Aspartic acid (Aspartate)\n Cys C Cysteine\n Gln Q Glutamine\n Glu E Glutamic acid (Glutamate)\n Gly G Glycine\n His H Histidine\n Ile I Isoleucine\n Leu L Leucine\n Lys K Lysine\n Met M Methionine\n Phe F Phenylalanine\n Pro P Proline\n Pyl O Pyrrolysine\n Ser S Serine\n Sec U Selenocysteine\n Thr T Threonine\n Trp W Tryptophan\n Tyr Y Tyrosine\n Val V Valine\n Asx B Aspartic acid or Asparagine\n Glx Z Glutamine or Glutamic acid.\n Xaa X Any amino acid.\n Xle J Leucine or Isoleucine\n TERM termination codon\n\n\n<a name=\"7.4.4\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7.4.4 Modified and unusual Amino Acids<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\"> Abbreviation Amino acid\n ------------ ---------\n\n Aad 2-Aminoadipic acid\n bAad 3-Aminoadipic acid\n bAla beta-Alanine, beta-Aminoproprionic acid\n Abu 2-Aminobutyric acid\n 4Abu 4-Aminobutyric acid, piperidinic acid\n Acp 6-Aminocaproic acid\n Ahe 2-Aminoheptanoic acid\n Aib 2-Aminoisobutyric acid\n bAib 3-Aminoisobutyric acid\n Apm 2-Aminopimelic acid\n Dbu 2,4-Diaminobutyric acid\n Des Desmosine\n Dpm 2,2'-Diaminopimelic acid\n Dpr 2,3-Diaminoproprionic acid\n EtGly N-Ethylglycine\n EtAsn N-Ethylasparagine\n Hyl Hydroxylysine\n aHyl allo-Hydroxylysine\n 3Hyp 3-Hydroxyproline\n 4Hyp 4-Hydroxyproline\n Ide Isodesmosine\n aIle allo-Isoleucine\n MeGly N-Methylglycine, sarcosine\n MeIle N-Methylisoleucine\n MeLys 6-N-Methyllysine\n MeVal N-Methylvaline\n Nva Norvaline\n Nle Norleucine\n Orn Ornithine\n OTHER (requires \/note=)\n\n\n<a name=\"7.4.5\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7.4.5 Genetic Code Tables<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Authority International Nucleotide Sequence Database Collaboration\nContact NCBI\nScope \/transl_table qualifier\nURL https:\/\/www.ncbi.nlm.nih.gov\/Taxonomy\/Utils\/wprintgc.cgi?mode=c\nURL https:\/\/www.insdc.org\/submitting-standards\/genetic-code-tables\/\n\n\n<a name=\"7.4.6\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7.4.6 Country Names<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Authority International Nucleotide Sequence Database Collaboration\nContact INSDC member databases\nScope \/country qualifier\nURL https:\/\/www.insdc.org\/submitting-standards\/country-qualifier-vocabulary\/\n\n\n<a name=\"7.4.7\"><\/a><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7.4.7 Announces<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Additional controlled vocabulary terms for qualifier values might be added\noutside of the cycle of the Feature Table document release. See also www.insdc.org\nwith controlled vocabularies in the Feature Table document.\nFrom December 2016 a complete list of the genetic codes will also be maintained outside \nof the cycle of the Feature Table document release at:\nhttps:\/\/www.insdc.org\/submitting-standards\/genetic-code-tables\/.\n\n<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>The DDBJ\/ENA\/GenBank Feature Table Definition Version 11.2 February 2024 DNA Data Bank of Japan, Mishima, Japan. EMBL-EBI, European Nucleotide Archive, Cambridge, UK. GenBank, NCBI, Bethesda, MD, USA. 1 Introduction 2 Overview of the Feature Table format 2.1 Format Design 2.2 Key aspects of this…<\/p>\n","protected":false},"author":15,"featured_media":0,"parent":233,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"acf":[],"_links":{"self":[{"href":"https:\/\/www.insdc.org\/wp-json\/wp\/v2\/pages\/21"}],"collection":[{"href":"https:\/\/www.insdc.org\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.insdc.org\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.insdc.org\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/www.insdc.org\/wp-json\/wp\/v2\/comments?post=21"}],"version-history":[{"count":3,"href":"https:\/\/www.insdc.org\/wp-json\/wp\/v2\/pages\/21\/revisions"}],"predecessor-version":[{"id":537,"href":"https:\/\/www.insdc.org\/wp-json\/wp\/v2\/pages\/21\/revisions\/537"}],"up":[{"embeddable":true,"href":"https:\/\/www.insdc.org\/wp-json\/wp\/v2\/pages\/233"}],"wp:attachment":[{"href":"https:\/\/www.insdc.org\/wp-json\/wp\/v2\/media?parent=21"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}