Applying WIPO Standard ST.26 to modified, structured and multi-component RNA inventions

1. Introduction

The success of mRNA vaccines and the growth of RNA therapeutics (protein-replacement mRNA, self-amplifying RNA, circular RNA, mRNA-encoded antibodies, in vivo gene editing payloads and cancer neoantigen vaccines) have made RNA sequences central to patent filings. In these filings, the sequence listing is not an administrative afterthought. It is the formal, machine-readable part of the disclosure that defines each sequence you rely on in the specification and claims. Errors in it can trigger notices to comply, indefiniteness rejections, loss of searchability and, in the worst cases, argument over what was actually disclosed.

This article explains how the current sequence-listing standard applies to mRNA inventions, focusing on the issues that are particular to RNA: how to represent uracil, modified nucleotides, caps, poly(A) tails and untranslated regions, how to treat encoded proteins and codon-optimized variants and how to align the listing with the specification and the claims.

2. The Legal and Technical Framework

2.1 WIPO Standard ST.26

Since 1 July 2022, patent offices that follow WIPO standards, including the USPTO, EPO and the PCT receiving offices, require nucleotide and amino acid sequence listings to be filed in WIPO Standard ST.26, an XML-based format. It replaced the older text-based ST.25 for applications filed on or after that date. A listing in the old ST.25 format is not acceptable for new applications filed after the switch, even if a priority application used it, so converting priority-document listings is a real task for family members filed after July 2022.

2.2 U.S. rules

In the United States, the sequence-listing provisions are found in 37 C.F.R. ยงยง 1.831 through 1.835. In summary:

If the listing is missing or non-compliant, the Office issues a notice requiring compliance with a time limit and fees for extension of time may apply. These notices delay examination and for an application with time-critical claims, such as a vaccine candidate in an active outbreak or a Track One filing, delay has strategic cost.

2.3 Which sequences must be listed

The rule applies to sequences that are specifically defined at each position. A sequence of ten or more nucleotides that contains only “n” positions for modified bases is treated differently from one composed of defined residues. As a practical matter, you should list:

Sequences that are shorter than the thresholds are not required to appear in the listing and may appear in the text, but be consistent. Many practitioners list borderline sequences anyway so that claims can refer to them by SEQ ID NO.

3. Representing RNA in ST.26

3.1 The molecule type and the uracil convention

This is the point where mRNA filers most often make mistakes. Under ST.26, nucleotide sequences are represented using the lowercase letters a, c, g and t, even for RNA. Uracil is represented as “t” and the molecule type is identified in the feature table by setting the /mol_type qualifier of the source feature to “mRNA,” “other RNA” or another appropriate value, as the standard allows. Do not enter “u” in the sequence. Do not enter uppercase letters. If you paste a sequence from a laboratory tool that outputs “AUGC,” it must be converted to lowercase and U must be changed to t.

The specification, on the other hand, can describe RNA in conventional terms (using U), but the specification should state that, in the sequence listing, uracil is represented as thymine, so as to make consistent the relationship between text and listing. A helpful sentence is: “In the sequence listing, RNA sequences are presented as DNA symbols with T representing U.” This avoids arguments that the listing sequence is DNA rather than RNA.

3.2 Why this matters for claims

A claim that recites “an mRNA comprising the sequence of SEQ ID NO: 1” is being read against a listing in which the sequence is expressed with t. In litigation or prosecution, any difference between the text and the listing can be exploited. Define the convention early and keep the claims neutral. Claims referencing “wherein the uracil of SEQ ID NO: 1 is N1-methylpseudouridine” are better than claims that try to embed the substitution in the sequence string.

3.3 Mandatory elements of the XML file

ElementWhat to supply
Document type and DTD versionThe root element ST26SequenceListing with the current DTD version.
Header informationSoftware name and version, production date, applicant file reference, application identification if known, earliest priority information, applicant name(s), invention title (one per language) and the total quantity of sequences.
SequenceData blocksOne block per sequence, with a unique sequenceIDNumber, an INSDSeq element including the length, molecule type (DNA, RNA or AA), division code, feature table and sequence residues.
Feature tableAt least a source feature with an /organism qualifier and an appropriate /mol_type qualifier. Add features for UTRs, coding regions and modified bases, as described below.
Language-dependent free textFree-text qualifiers (notes) must be in English and for languages in the application, an additional language version is also provided where required.

Do not write XML by hand. Use WIPO Sequence, the official authoring and validation tool, or another compliant tool and always run the validator before filing. Validation will catch many structural and syntactic errors, but it cannot tell whether your biology is right.

4. Modified Nucleotides, Caps and Tails

Therapeutic mRNA rarely consists only of natural A, C, G and U. A typical construct has N1-methylpseudouridine or pseudouridine in place of uridine, a 5′ cap, optimized UTRs, a coding region and a poly(A) tail and sometimes additional modifications such as 5-methylcytidine or specialized cap analogs. ST.26 offers specific mechanisms for these.

4.1 Modified bases

The decision about how to represent a modification can have claim-scope consequences. If the listing represents N1-methylpseudouridine positions as plain “t,” a claim to “SEQ ID NO: 1” may be read to cover unmodified RNA. If the listing marks modifications, the claim may be read as narrower. Draft specification text that expressly explains the intended meaning and consider dependent claims that recite the modification separately.

4.2 Cap structures

The 5′ cap (for example Cap 0, Cap 1 or a co-transcriptional trinucleotide cap analog such as CleanCap-type structures) is a chemical structure that cannot be fully described in a sequence string. The sequence listing should represent the nucleotide sequence of the transcript. The cap itself should be described in the specification and, if it is claimed, in the claims, with chemical structure drawings or clear names. Where the standard permits, you may annotate the 5′ end with a feature such as a modified_base or misc_feature with an explanatory note, but do not assume the listing alone captures the cap. If the cap analog contributes nucleotides that count in the sequence, describe how they are numbered, to avoid positional confusion.

4.3 Poly(A) tails

A poly(A) tail is usually shown as a string of a’s. If the tail has ten or more specifically defined adenosines, it is a nucleotide sequence within the rule. Two practical issues arise:

4.4 UTRs and coding regions

Annotate regulatory and coding regions in the feature table using standard keys such as 5’UTR, 3’UTR and CDS, with accurate location ranges. For a CDS feature, include the /translation qualifier where the standard requires it, so that the encoded protein is represented. Proteins encoded by the mRNA should be listed as separate amino acid sequences with their own SEQ ID NOs, if they have four or more specifically defined amino acids and the CDS feature should be consistent with them. Incorrect location numbers are an easy and common error, especially when an upstream sequence is lengthened or shortened late in drafting.

4.5 Other RNA formats

5. Encoded Proteins, Codon Optimization and Variants

Vaccine claims often cover an antigen, a nucleic acid encoding it and compositions comprising that nucleic acid. The sequence listing should reflect each of those layers.

Remember the relationship between claims and disclosure. After the U.S. Supreme Court’s 2023 decision in Amgen Inc. v. Sanofi, broad functional genus claims face substantial enablement scrutiny. In mRNA filings this means that listing and disclosing a wide range of working variants, not just a single lead sequence, can matter for supporting claims to sequence families defined by percent identity or function. The sequence listing should include the species you actually have and have tested, so the claims can be tied to concrete SEQ ID NOs.

6. Aligning the Listing With the Specification and Claims

6.1 Referring to sequences in the text

6.2 Incorporation by reference

Include a short, accurate paragraph in the specification, such as: “The instant application contains a Sequence Listing which has been submitted in XML format and is hereby incorporated by reference in its entirety. Said XML file, created on [date], is named [filename] and is [size] bytes in size.” Update the file name, date and size every time you regenerate the XML, since the figures change with each edit.

6.3 Priority documents and later filings

7. Common Errors in mRNA Listings

ErrorConsequenceHow to avoid it
Using “u” or uppercase letters in the sequenceValidation failure or an incorrect, DNA-style representation.Convert to lowercase and replace U with t before import. Use the WIPO tool for validation.
Mislabeling mol_type (DNA instead of RNA, or the reverse)Ambiguity over whether the claimed molecule is DNA or RNA.Set the molecule type deliberately for each entry; plasmids are DNA, transcripts are RNA.
Failing to list encoded proteinsClaims to the protein have no listing support; missing SEQ ID NOs in claims.List each protein of four or more residues and link it to the CDS.
Wrong feature locations after sequence editsAnnotations point to wrong region; examiner questions disclosure.Re-verify the feature table after any change and compare to a map of the construct.
Misrepresenting modified basesClaim scope unclear or listing rejected.Use modified_base features and /mod_base or /note. Explain conventions in the specification.
Inconsistent sequence between text, claims and listingRejections for indefiniteness or lack of written description.Treat the listing as the single source of truth and generate text excerpts from it, not the reverse.
Sequence number gaps, duplicate SEQ ID NOs or incorrect total quantityValidation errors.Regenerate numbering after deletions; confirm sequenceTotalQuantity.
Incorrect incorporation-by-reference dataNotice to comply.Update file name, date and size after each export.
Listing unspecified sequences with long “n” runsSequence is not a “specifically defined” sequence; the listing may be unnecessary or misleading.Decide whether to omit or describe the sequence in words.
Leaving out variants disclosed in tables or figuresNotice to comply or lost basis for claims.Search the specification for every sequence of the threshold length.

8. A Practical Workflow

  1. Collect the sequences. Get the electronic source files from the lab, not retyped copies. Confirm which sequences are RNA, DNA and protein.
  2. Define conventions. Decide how to represent modifications, caps and tails. Draft the description paragraph that explains these conventions.
  3. Build the listing. Use WIPO Sequence. Enter the sequence, set the molecule type, add features (source, 5’UTR, CDS, 3’UTR, modified_base, misc_feature) and add the encoded proteins as separate entries.
  4. Validate. Run the validator, resolve all errors and read every warning. Treat warnings as a to-do list.
  5. Cross-check biology. Have a scientist verify that the translation of each CDS matches the listed protein, that mutations are at the stated positions and that UTR and CDS boundaries match the plasmid map.
  6. Cross-check the text. Search the specification and claims for every SEQ ID NO and verify the description. Confirm all sequences of required length are in the listing.
  7. Update the incorporation-by-reference paragraph with the final file details.
  8. File and preserve. Upload the XML file as the sequence listing document type in Patent Center. Keep a copy of the final XML and validation report for your records.
  9. Re-run the process for every amendment that changes any sequence or the order of SEQ ID NOs.

9. Strategic Considerations for Vaccine and Therapeutic Applicants

10. Conclusion

For mRNA vaccines and therapeutics, the sequence listing is a legal document that carries real weight. Under ST.26, RNA is entered with lowercase DNA symbols, uracil as t and the molecule type specified separately; modifications, caps and tails require careful annotation and explanatory text; and every encoded protein and every variant you intend to claim must appear with an identifier. Build the listing with the official tool, validate it, verify the biology independently, align the text and claims to it and keep the incorporation-by-reference details current. A disciplined approach protects your priority date, avoids avoidable office actions and supports the claim scope that your science deserves.

Leave a Reply

Your email address will not be published. Required fields are marked *