Source: https://www.bitlaw.com/source/mpep/2429.html
Timestamp: 2018-02-25 04:05:12
Document Index: 440946739

Matched Legal Cases: ['§2428', '§2430', '§ 2422', '§ 2422', '§ 2426', '§ 2422', '§ 2428', '§ 2422', '§ 2424', '§ 2422']

MPEP 2429: Helpful Hints for Compliance, Jan. 2018 (BitLaw)
MPEP 2429
Helpful Hints for Compliance
Previous: §2428 | Next: §2430
2429 Helpful Hints for Compliance [R-07.2015]
The Office has now had a good deal of experience in the implementation of the sequence rules. The following list sets forth helpful hints, for both examiners and applicants, for compliance. For the most part, the list is a compilation of frequently asked questions.
—Compliance is not a filing date issue.
—Compliance is not a 35 U.S.C. 112 issue.
—Compliance is not a 35 U.S.C. 119 /120 issue.
—Compliance is not per se a new matter issue. The standard for resolution of inconsistencies between the official sequence listing (submitted on paper or compact disc pursuant to 37 CFR 1.821(c) ) and the computer readable form thereof and/or errors in the official copy of sequence information is based on the new matter standard. If there are inconsistencies in compact discs submitted in accordance with 37 CFR 1.52(e) between "Copy 1" and "Copy 2", the compact disc labeled "Copy 1" will be used for further processing.
—Compliance can be achieved via amendment.
—If a new application is filed via EFS-Web with an ASCII text file sequence listing that complies with the requirements of 37 CFR 1.824(a)(2) - (6) and 37 CFR 1.824(b), and applicant has not filed a sequence listing in a PDF file, the text file will serve as both the paper copy required by 37 CFR 1.821(c) and the computer readable form (CRF) required by 37 CFR 1.821(e) thus the filer need not submit i) any additional copies of the sequence listing pursuant to 37 CFR 1.821(e) nor ii) the statement described in 37 CFR 1.821(f). Any sequence listing submitted as an ASCII text file via EFS-Web that is otherwise in compliance with 37 CFR 1.52(e) and 37 CFR 1.824(a)(2) - (6) and 37 CFR 1.824(b) will be excluded when determining the application size fee required by 37 CFR 1.16(s) or 37 CFR 1.492(j) as per 37 CFR 1.52(f)(1). See MPEP § 2422.03(a) for additional information.
—Filing a sequence listing via EFS-Web in PDF format is not recommended. A sequence listing in PDF format is treated as the paper copy required by 37 CFR 1.821(c) and would require filing of both a separate CRF and a statement that the written copy and the CRF are identical as required by 37 CFR 1.821(f). In addition, a sequence listing submitted via EFS-Web in PDF format as part of the specification is not excluded when determining the application size fee required by 37 CFR 1.16(s) or 1.492(j) as per 37 CFR 1.52(f)(1).
—For international applications (PCT), the check list of the PCT Request filed with the international application must contain an indication that the sequence listing forms part of the international application. See MPEP § 2422.03(a), subsection IV, for information specific to filing sequence listings in international applications (PCT) via EFS-Web.
—Applicants are reminded that for fee purposes, a table of sequences is not a sequence listing. Such tables are considered text as part of the specification and are included when determining the application size fee required by 37 CFR 1.16(s) or 1.492(j) as per 37 CFR 1.52(f)(1).
—Failure to reply to sequence compliance issues in a timely manner may reduce any patent term adjustment. Patent applications filed under 35 U.S.C. 111(a) on or after December 18, 2013, and international patent applications in which the national stage commenced under 35 U.S.C. 371 on or after December 18, 2013, may be subject to reductions in patent terms adjustment pursuant to 37 CFR 1.704(c)(13) if they are not in condition for examination within eight months from the filing date or date of commencement, respectively. "In condition for examination" includes compliance with 37 CFR 1.821 - 1.825 (see 37 CFR 1.704(f) ).
—The copy of the sequence listing required by 37 CFR 1.821(c) is an integral part of the application. If submitted on paper, the sequence listing must begin on a new page, should appear at the end of the application, and preferably should be numbered independently of the numbering of the remainder of the application. The new page that begins the sequence listing should be entitled "Sequence Listing." If not submitted as such at filing, the Sequence Listing must be inserted into the application via amendment, e.g., by preliminary amendment. If submitted on compact disc, or as an ASCII text file via EFS-Web, the specification must contain an incorporation by reference of the material on the compact disc or submitted via EFS-Web in a separate paragraph identifying each compact disc or ASCII text file.
—Substitute pages, replacement compact discs, or replacement ASCII text files submitted via EFS-Web, as appropriate, must be used for any changes to the sequence listing or CRF thereof. See MPEP § 2426 for additional information regarding amendments to or replacement of a sequence listing or CRF thereof.
—Applicant's reply to a notice of a defective transfer request preferably includes a CRF (an ASCII text file submitted via EFS-Web or on compact disc(s)), however a new transfer request and correction of the noted deficiencies is also permitted. See MPEP § 2422.05.
—Angle brackets and numeric identifiers listed in 37 CFR 1.823 are very important for our database. Extra punctuation should not be used in sequence listings.
—The computer readable form cannot contain page numbers. Page numbers should only be placed on the paper copy of the sequence listing. Page numbers should not be placed on the ASCII text file or compact disc copy of the sequence listing.
—The PatentIn computer program is not the only means by which to comply with the rules. Any word processing program can be used to generate a sequence listing if it has the capability to convert a file into ASCII text. However, use of a word processing program to generate or amend a sequence listing file is discouraged. Word processing programs often introduce unintended changes to the sequence listing that render the listing unacceptable. Use of a plain text editor to generate or edit a sequence listing is recommended.
—If a word processing program is used to generate a sequence listing, hard page break controls should not be used and margins should be adjusted to the smallest setting.
—Word processing files should not be submitted to the Office; the sequence listing generated by a word processing file should be saved as an ASCII text file for submission. Most word processing programs provide this feature.
—Statements in accordance with 37 CFR 1.821(f), (g), and (h) and 37 CFR 1.825 and proper labeling in accordance with 37 CFR 1.824(a)(6) should be noted. Sample statements to support filings and submissions in accordance with 37 CFR 1.821 through 1.825 are provided in MPEP § 2428 Sample Statements.
—Use Box SEQUENCE. See MPEP § 2422.09.
—On nucleotide sequences, since only single strands may be depicted in the sequence listing, show strands in 5′ to 3′ direction.
—The single stranded nucleotide depicted in the sequence listing may represent a strand of a nucleotide sequence that may be single or double stranded which may be, further, linear or circular. An amino acid sequence or peptide may be linear or circular.
—Numeric identifiers "<140>, Current Application Number," "<141>, Current Filing Date," "<150>, Prior Application Number," and "<151>, Prior Application Filing Date," should appear in the sequence listing in all cases. If the information about the current application is not known or is unavailable at the time of completing the sequence listing, then the lines following numeric identifiers <140> and <141> should be left blank. This would normally be the case when the sequence listing is included in a newly filed application. Similarly, if information regarding prior applications is inapplicable, or not known at the time of completing the sequence listing but will be later filed, then the numeric identifiers <150> and <151> should appear with the line following the numeric identifiers left blank.
—The mandatory items of information that must be included in a sequence listing are identified in the table of numeric identifiers set forth in 37 CFR 1.823(b). See also MPEP § 2424.02.
—Pursuant to 37 CFR 1.83(a), sequences that are included in sequence listings should not be duplicated in the drawings. However, significant sequence characteristics that are not readily conveyed by the data in the sequence listing may be depicted in a drawing figure. However, the sequence information so conveyed must still be included in a sequence listing if the sequence falls within the definition set forth in 37 CFR 1.821(a), and the sequence identifier ("SEQ ID NO:X") must be used, either in the drawing or in the "Brief Description of the Drawings." See MPEP § 2422.02 for additional information.
—Extra copies of computer readable forms should not be sent to examiners.
—Inosine may be represented by the use of "I" in the features section, otherwise use "n."
—Stop codons that are represented by an asterisk are not permitted in amino acid sequences.
—Punctuation should not be used in a sequence to indicate unknown nucleotide bases or amino acid residues or to delimit active or functional regions of a sequence. These regions should be noted as Features of the sequence per 37 CFR 1.823(b) (see numeric identifiers <220> - <223>.
—The presence of an unnatural amino acid in a sequence does not have the same effect as the presence of a D-amino acid. The sequence may still be subject to the rules even though one or more of the amino acids is not naturally occurring.
—Cyclic and branched peptides are causing some confusion in the application of the rules. Specific questions should be directed to Sequence Systems Service Center of the Scientific and Technical Information Center at 571-272-2510.
—A cyclic peptide with a tail is regarded as a branched sequence, and thereby exempt from the rules, if all bonds adjacent to the amino acid from which the tail emanates are normal peptide bonds.
—Sequences that have variable-length regions depicted as, for example, Ala Ala Leu Leu (Xaa Xaa)n Ile Pro where n=0-234 or agccttgggaca(nnnnn)mgtcatt where m=0-354 or Ser Met Ala Xaa Ser where Xaa could be 1, 2, 3, 4 and/or 5 amino acids must still comply with the Sequence Rules. The method to use is to repeat the variable-length region as many times as the maximum length and specify in the Features section that the amino acid (or nucleotide) at a specified position is either absent or present. The variables Xaa and n may stand for only one residue, hence the need to repeat the variable. The correct way to submit the third example is Ser Met Ala Xaa Xaa Xaa Xaa Xaa Ser combined with an explanation in the Features section of the listing that any one or all of amino acids 4-8 can either be present or absent.
—Single letter amino acid abbreviations are not acceptable within the sequence listing but may appear elsewhere in the application.
—Zero (0) is not used when the numbering of amino acids uses negative numbers to distinguish the mature protein.
—Subscripts or superscripts are not permitted in a sequence listing.
—The exclusive conformance requirement of 37 CFR 1.821(b) requires that any amendment of the sequence information in a sequence listing be accompanied by an amendment to the corresponding information, if any, embedded in the text of the specification or presented in a drawing figure.
—A mandatory feature is required to cover every "n" or "Xaa" used in a sequence. The feature consists of numeric identifiers <220>, <221>, <222>, and <223>. Numeric identifier <220> should remain blank, numeric Identifier <221> should be selected from "WIPO Standard ST.25 (1998), Appendix 2," numeric identifier <222> should identify the location of the "n" or "Xaa" within the sequence, and numeric identifier should <223> specify what the "n" or "Xaa" can be. When all of the "n" or "Xaa" variables in a sequence are equal to the same thing, a range of the entire sequence can be given for numeric identifier <222> to cover all of the "n" or "Xaa" designators in one feature.
—Remove all non-ASCII characters from the.txt file. For example, an α symbol should be spelled out as "alpha."
—Tabs are non-ASCII characters. Do not use tabs in sequence listing.txt files.
—Make all explanations in a feature section consistent with the molecule type in numeric identifier <212>. For example, if the sequence is type "PRT" do not describe the sequence in a feature section as a "synthetic oligonucleotide."
—A response for numeric identifier <130>, "File Reference," is mandatory if the numeric identifier <140> is not present, e.g., when the sequence listing is filed before the application number has been assigned. At least one of a numeric identifier <130> with docket number or numeric identifier <140> with current application number must be in the sequence listing. This information is used to ensure that CRF files are correctly matched to their corresponding applications.
—The format "YYYY-MM-DD" should be used for dates.
—If a sequence listing is modified by the addition or deletion of sequences, remember to update the total number of sequences in numeric identifier <160>.
—Numeric identifier <213> can only be one of three choices: Scientific name (i.e. Genus/species), Unknown, or Artificial Sequence. Do not add any extraneous information about the sequence, such as a gene names, in this field. Do not use common names for species. For example, human should be "Homo sapiens" and cow should be "Bos taurus." If a specific genus/species is unknown, use the reply "Unknown" in numeric identifier <213> and add whatever information is known into numeric identifier <223> of the feature section. For example, if only the family "Saccharomycetaceae" is known, numeric identifier <213> should state "Unknown" and numeric identifier <223> could state "fungus of the family Saccharomycetaceae."
—For all sequences using "Unknown" or "Artificial sequence" for numeric identifier <213>, a mandatory feature is required to explain the source of the genetic material. The feature consists of <220>, which remains blank, and <223>, which states the source of the genetic material. To explain the source, if the sequence is put together from several organisms, please list those organisms. If the sequence is made in the laboratory, please indicate that the sequence is synthesized.
—Only use abbreviations that are specifically defined in "WIPO Standard ST.25 (1998)" or that are well known. Do not use abbreviations that are specific to the application at issue and would not be clear to someone who had not read the invention description. When in doubt, use the full name rather than an abbreviation.
—Note that if a sequence listing CRF is rejected and an error report issued, the errors listed are exemplary and may not be a complete list of all errors in the sequence listing file. The applicant is required to review the sequence listing in its entirety and correct all instances of similar errors.
—Any inquiries regarding a specific computer readable form that has been processed by the Office should be directed to the Sequence Systems Service Center of the Scientific and Technical Information Center at 571-272-2510.