# namespace SMRUCC.genomics.Annotation.Assembly.NCBI.GenBank.TabularFormat.GFF
export class GFFTable {
# date (##date )
#
# The date the file was made, Or perhaps that the prediction programs were run. We suggest to use
# astronomical format 1997-11-08 for 8th November 1997, first because these sort properly, And
# second to avoid any US/European bias.
date: string;
# DNA
#
# (##DNA
# ##acggctcggattggcgctggatgatagatcagacgac
# ##...
# ##End-DNA)
#
# To give a DNA sequence. Several people have pointed out that it may be convenient to include the sequence in the file.
# It should Not become mandatory to do so, And in our experience this has been very little used. Often the seqname will
# be a well-known identifier, And the sequence can easily be retrieved from a database, Or an accompanying file.
DNA: string;
# 基因组上面的特性位点
features: Feature[];
# gff-version (##gff-version 2)
#
# GFF version - In Case it Is a real success And we want To change it. The current Default version Is 2,
# so If this line Is Not present version 2 Is assumed.
GffVersion: integer;
# 生成这个文件的应用程序
processor: string;
# Protein
#
# (##Protein
#
# ##MVLSPADKTNVKAAWGKVGAHAGEYGAEALERMFLSF
# ##...
# ##End-Protein)
#
# Similar to DNA. Creates an implicit ##Type Protein directive.
Protein: string;
# RNA
#
# (##RNA
# ##acggcucggauuggcgcuggaugauagaucagacgac
# ##...
# ##End-RNA)
#
# Similar to DNA. Creates an implicit ##Type RNA directive.
RNA: string;
# sequence-region (##sequence-region )
#
# To indicate that this file only contains entries for the specified subregion of a sequence.
SeqRegion: SeqRegion;
# Genome size
Size: integer;
species: string;
# source-version (##source-version )
#
# So that people can record what version Of a program Or package was used To make the data In this file.
# I suggest the version Is text without whitespace. That allows things Like 1.3, 4a etc. There should be
# at most one source-version line per source.
SrcVersion: string;
# type (##Type [])
#
# The type Of host sequence described by the features. Standard types are 'DNA', 'Protein' and 'RNA'.
# The optional allows multiple ##Type definitions describing multiple GFF sets in one file,
# each of which have a distinct type. If the name is not provided, then all the features in the file
# are of the given type. Thus, with this meta-comment, a single file could contain DNA, RNA and
# Protein features, for example, representing a single genomic locus or 'gene', alongside type-specific
# features of its transcribed mRNA and translated protein sequences. If no ##Type meta-comment is
# provided for a given GFF file, then the type is assumed to be DNA.
type: string;
}