Sequences

Check a sequence listing before you file

A software check can test the file against ST.26. Only you can confirm that it holds every sequence the application discloses.

What a software check can test

  1. The file is one XML file in UTF-8, with the XML declaration on its first line and the DOCTYPE declaration on its second [ST.26, paragraphs 39 and 40].
  2. SEQ ID NOs start at 1 and go up by one. A skipped number is written as a 000 sequence, and SequenceTotalQuantity counts it too [ST.26, paragraphs 10 and 45].
  3. No sequence with fewer than 10 specifically defined nucleotides, or fewer than 4 specifically defined amino acids, has a SEQ ID NO of its own [ST.26, paragraph 8].
  4. Nucleotides are in lower case and amino acids in upper case, written with the symbols of Annex I [ST.26, paragraphs 13 and 26].
  5. Each sequence has one source feature over its whole length, with organism and mol_type [ST.26, paragraphs 63 and 75].
  6. Every feature key comes from Annex I, and no qualifier's free text runs past 1,000 characters [ST.26, paragraphs 62 and 86].

What only you can confirm

  • The listing includes every sequence the application spells out residue by residue, if it has 10 or more specifically defined nucleotides or 4 or more specifically defined amino acids. That includes a sequence identical to part of a longer one [ST.26, paragraphs 7 and 10].
  • A sequence built from segments of other sequences is listed as a sequence of its own [ST.26, paragraph 35].
  • A sequence with a gap of unknown length is split, and each part with enough specifically defined residues has its own SEQ ID NO [ST.26, paragraph 37].
  • Each organism and feature is right for its sequence.

Run a check

The ST.26 check applies 37 rules in your browser, each with the paragraph of ST.26 that sets it. The file stays on your computer.

Sources, checked 16 November 2026