Attachment 17e - (dtd) -ExportTOC1.txt

TXT text file 10 KB Posted

Attached to
Patent Data and Document Management Federal contract opportunity
Solicitation number
ACQ-20-0057
Issued by
Department of Commerce US Patent and Trademark Office

About this file

This document provides details on a federal contract opportunity with the United States Patent and Trademark Office. The solicitation seeks indexing and scanning services for all paper patent application documents, as well as data capture and composition services to convert electronically filed applications into formats suitable for publication and patent issuance. Additional requirements include quality review of electronic submissions, customer support, and processing of post-allowance documents and correspondence. The contractor must deliver indexed images and composed application data on weekly schedules in accordance with technical standards to ensure patent applications can be properly published and patents granted. Key deliverables include conversion of pending and allowed applications prior to publication and issuance, as well as composition of various patent certificates on a daily basis.

Text of this file

<?xml version='1.0' encoding='UTF-8' ?>

<!--Generated by Turbo XML 2.3.1.100.-->

<!--#DOCUMENTATION:Purpose:

This DTD describes instances of a Table of Contents file for shipments of files from the PTO to PaDaCap Contractor. The shipment files contain either images (in CCITT Group 4 format) of USPTO patent application source docuements, or XML data exported from PTO systems. The shipment files and directory structure will be in one media, be it a tape, CD, or a ZIP or TAR file, or some other format.-->

<!--#DOCUMENTATION:Caveats:

1. Although this DTD contains elements describing PreGrant shipments, the current PreGrant process does not support shipments in this form yet.

2. This DTD could be used to create a TOC for sending replacement files as well as initial shipments, but no method of distinction between the two is provided for.

3. This DTD could be used to create a TOC for sending partial as well as complete shipments, but no method of distinction between the two is provided for.--> <!--#DOCUMENTATION:The list of all applications exported in this instance.--> <!ELEMENT ExportList (ExportID , ExportDate , AppCount? , Application+ , AppCount?)>

<!--#DOCUMENTATION:The ExportType is based on whether the export is an (E)arly capture, (P)reGrant, (I)nitial, (F)inal, or (Q)uery export.

An Early Capture export contains applications that are being captured for delivery to PTO examination databases.

A PreGrant export contains applications that are intended to be published as PreGrant.

An Initial export contains allowed applications that have not been previously exported and are not ready for publication.

A Final export contains applications that were previously exported and/or are ready for publication.

A Query export contains specifically requested applications that were previously exported unsuccessfully.--> <!ATTLIST ExportList ExportType (E | P | I | F | Q) #REQUIRED>

<!--#DOCUMENTATION:A unique ID (possibly across all shipments) assigned by the PTO.

This ID and the ExportDate element value will enable the identification of this shipment in any communications between PTO and PaDaCap Contractor personnel.--> <!ELEMENT ExportID (#PCDATA)>

<!--#DOCUMENTATION:The date this export was created.

This date and the ExportID element value will enable the identification of this shipment in any communications between PTO and PaDaCap Contractor personnel.

The format is yyyymmdd.

<!ELEMENT ExportDate (#PCDATA)>

<!--#DOCUMENTATION:The number of applications exported in this instance.--> <!ELEMENT AppCount (#PCDATA)>

<!--#DOCUMENTATION:The metadata for an individual application.--> <!ELEMENT Application (ApplicationNumber , FilingDate , GroupArtUnit , (EarlyCaptureApplication | PreGrantApplication | AllowanceApplication | AfterAllowanceApplication))>

<!--#DOCUMENTATION:The Application Number is the 2 digit Series Code concatenated to the 6 digit Serial Number.

It is assigned by the PTO when the application was filed.

Ex: scnnnnnn.--> <!ELEMENT ApplicationNumber (#PCDATA)>

<!--#DOCUMENTATION:The date the application was filed at the PTO.

The format is yyyymmdd.--> <!ELEMENT FilingDate (#PCDATA)>

<!--#DOCUMENTATION:The Group Art Unit the application was assigned to at the PTO.

<!ELEMENT GroupArtUnit (#PCDATA)>

<!--#DOCUMENTATION:The export information for a PreGrant application.--> <!ELEMENT PreGrantApplication (PPD , Package+)>

<!--#DOCUMENTATION:The FilingType is based on whether the application is for a Utility or Plant patent.

This attribute is kept as a comment to document that it is superfluous in PreGrant since this information is included in the Bib.xml or Supp.xml file for PreGrant applications.--> <!ATTLIST PreGrantApplication FilingType (UTILITY | PLANT ) #REQUIRED> <!--#DOCUMENTATION:The ApplicationType is based on the publication kind code to be used.

This attribute is kept as a comment to document that it is superfluous in PreGrant since this information is included in the Bib.xml or Supp.xml file for PreGrant applications.--> <!ATTLIST PreGrantApplication ApplicationType (NEW | CORRECTED | REPUBLICATION ) #REQUIRED> <!--#DOCUMENTATION:The Projected Publication Date for the PreGrant application.

The format is yyyymmdd.-->

<!ELEMENT PPD (#PCDATA)>

<!--#DOCUMENTATION:The export information for an Early Capture application.--> <!ELEMENT EarlyCaptureApplication (Package+)>

<!--#DOCUMENTATION:The FilingType is based on whether the application is for a Utility, Design or Plant patent.--> <!ATTLIST EarlyCaptureApplication FilingType (UTILITY | DESIGN | PLANT ) #REQUIRED>

<!--#DOCUMENTATION:The ApplicationType is based on the publication style to be used in the masthead.

If more than one ApplicationType is appropriate for a single application, the main type is the first one.

For instance, in the case of a Reissue of a Reexam of a Utility, the value of this attribute would be Reissue.--> <!ATTLIST EarlyCaptureApplication ApplicationType (REGULAR | REISSUE | REEXAM ) #REQUIRED>

<!--#DOCUMENTATION:The export information for an Allowance application.--> <!ELEMENT AllowanceApplication (Recycled? , AllowanceDate , Package+)>

<!--#DOCUMENTATION:The FilingType is based on whether the application is for a Utility, Design or Plant patent.--> <!ATTLIST AllowanceApplication FilingType (UTILITY | DESIGN | PLANT ) #REQUIRED>

<!--#DOCUMENTATION:The ApplicationType is based on the publication style to be used in the masthead.

If more than one ApplicationType is appropriate for a single application, the main type is the first one.

For instance, in the case of a Reissue of a Reexam of a Utility, the value of this attribute would be Reissue.--> <!ATTLIST AllowanceApplication ApplicationType (REGULAR | REISSUE | REEXAM ) #REQUIRED>

<!--#DOCUMENTATION:The export information for an AfterAllowance application.--> <!ELEMENT AfterAllowanceApplication (Recycled? , AllowanceDate , Package+)>

<!--#DOCUMENTATION:The FilingType is based on whether the application is for a Utility, Design or Plant patent.--> <!ATTLIST AfterAllowanceApplication FilingType (UTILITY | DESIGN | PLANT ) #REQUIRED>

<!--#DOCUMENTATION:The ApplicationType is based on the publication style to be used in the masthead.

If more than one ApplicationType is appropriate for a single application, the main type is the first one.

For instance, in the case of a Reissue of a Reexam of a Utility, the value of this attribute would be Reissue.--> <!ATTLIST AfterAllowanceApplication ApplicationType (REGULAR | REISSUE | REEXAM ) #REQUIRED>

<!--#DOCUMENTATION: (Reserved for future use) If the element is present, the application is a recycled application.

This indicates that the application may have previously been processed by PaDaCap Contractor.

If the element is not present, the application should be new to PaDaCap Contractor.

The only values currently expected are CPA (Continuing Prosecution Application) and RCE (Request for Continued Examination).--> <!ELEMENT Recycled (#PCDATA)>

<!--#DOCUMENTATION:The Allowance Date for the Allowance or AfterAllowance application.

The format is yyyymmdd.--> <!ELEMENT AllowanceDate (#PCDATA)>

<!--#DOCUMENTATION:The container for a related set of Document elements.

All the Files referred to in a package will have the same MailDate and LoadDate.

All the Files referred to in a package will be uniquely named; the combination of an image file name and the Package ID will identify a specific, unchanging image file across all exports of a given application.--> <!ELEMENT Package (PackageID , PckPages , MailDate , LoadDate? , Document+)>

<!--#DOCUMENTATION:The PackageID identifies a Package across all exports.--> <!ELEMENT PackageID (#PCDATA)>

<!--#DOCUMENTATION:The PckPages is the count of the Files in all the Documents contained in this Package.--> <!ELEMENT PckPages (#PCDATA)>

<!--#DOCUMENTATION:The Mail Date recorded in the IFW system for this set of files.

This indicates the date the files were received at PTO.

Used to determine which images contain the latest data.

If the file is not an image file, this entry will be its creation or export date.

The format is yyyymmdd.

<!ELEMENT MailDate (#PCDATA)>

<!--#DOCUMENTATION:The Load Date recorded in the IFW system for this set of files.

This indicates the date the files were loaded into the IFW system.

Used to determine which images contain the latest data, and possibly whether this document has already been received by PaDaCap Contractor.

If the file is not an image file, this entry will be its creation or export date.

The format is yyyymmdd.

<!ELEMENT LoadDate (#PCDATA)>

<!--#DOCUMENTATION:The container for a related set of files having the same Code.

Related images (comprising a set) with a given code will be grouped within an instance of this element, and the files referred to will be in sequential source order.--> <!ELEMENT Document (Code , File+)>

<!--#DOCUMENTATION:The Code delineates the area of concern for the information being exported.

For instance, if the Document contained image files for the specification, the Code value would be SPEC.

Although any value will be allowed by the DTD, only some values will be expected by PaDaCap Contractor processes. All others will be unexpected.

It will be necessary for the PTO to notify PaDaCap Contractor in the event of changes to either the list of values expected, or the nature of items included in an expected value.

The values currently expected in a PreGrantDocument are listed in "PACR Migration DocCodes.doc".

The values currently expected in an AllowanceDocument or AfterAllowanceDocument are listed in "draftOPPIB-IFWdatasourcesOct2.doc".

The current list of all known Document codes can be found in "Doc Codes (10-01-03).xls".--> <!ELEMENT Code (#PCDATA)>

<!--#DOCUMENTATION:The full path to the file in this position.

The files are expected to be in TIFF Group 4 format.--> <!ELEMENT File (#PCDATA)>

Other files for this federal contract opportunity

Other files attached to Patent Data and Document Management, newest first.
File Type Posted
Attachment 38 - IT Security Requirements - 2018-09.docx DOCX document
Attachment 23 - DataEntryManual-NON-UTILITY-2019.doc DOC document
Attachment 03b - USPTO Enterprise Workstation Naming Convention.docx DOCX document
Attachment 10b - 9611604.pdf PDF
Attachment 31 - CofC_manual_PaDaCap_2019.docx DOCX document
Attachment 26 - DCB 2019-01 (11).docx DOCX document
Attachment 17a - DPMpgpub-2019.doc DOC document
Attachment 26 - DCB 2019-01 (22).docx DOCX document
Attachment 03a - USPTO_Computer_Specs.xlsx XLSX spreadsheet
Attachment 41 - Past Performance Questionnaire.docx DOCX document
Attachment 11 - Link to Public PAIR.docx DOCX document
Attachment 17b (jpg) - u-bibdat1.jpg JPG image
Attachment 35b - PE2E-eDRS-Navigation_QRG.pdf PDF
Attachment 35b - PE2E-eDRS-User-Preferences_QRG.pdf PDF
Attachment 26 - DCB 2019-01 (23).docx DOCX document
Attachment 17c (jpg) - u-suppub8-2012-12-04.jpg JPG image
Attachment 26 - DCB 2019-01 (2).docx DOCX document
Attachment 25b - Consolidated Listing of Official Gazette Notices, 2018-01-25.pdf PDF
Attachment 26 - DCB 2019-01 (17).docx DOCX document
Attachment 10b - 9591857 Lengthy Table.pdf PDF
Attachment 05d- Historical Volumes for PG Pubs, IDC Exports and Issue Sizes for FY-16-19.xls XLS spreadsheet
Attachment 39a -Transition Plan Framework.docx DOCX document
Attachment 26 - DCB 2019-01 (21).docx DOCX document
Attachment 05b- Weekly Serialized Filings.xls XLS spreadsheet
Attachment 26 - DCB 2019-01 (27).docx DOCX document
Attachment 13a - Final FEPIB No. 2019-3 Addition to Appendix Eight Supplemental Guidance.doc DOC document
Attachment 26 - DCB 2019-01 (13).docx DOCX document
Attachment 19a - Link to USPTO PG Pub Red Book Instructions.docx DOCX document
Attachment 15 - CRF_Transfer_Participant_Manual_Final_Revision_2019-03-18.pdf PDF
Attachment 10b - PP27824.pdf PDF
Attachment 35b - PE2E-eDRS-Column-Selector_QRG.pdf PDF
Attachment 28a - Link to USPTO Grant Yellow Book Instructions.docx DOCX document
Attachment 22 - DataEntryManual-UTILITY-2019.doc DOC document
Attachment 24 - File Maintenance Final Data Capture and Issue Build 201900911.doc DOC document
Attachment 17d (jpg)- us-request-v15-2013-01-25.jpg JPG image
Attachment 10a - Sample Issued Patents and Cooperative Patent Classification.docx DOCX document
Attachment 18 - DCB 2019-None.docx DOCX document
Attachment 10b - D782781.pdf PDF
Attachment 02 - TIC_Ref_Arch_v2.2_2017.pdf PDF
Attachment 26 - DCB 2019-01 (1).doc DOC document
Attachment 10b - H002272.pdf PDF
Attachment 01a - Contractor Access to USPTO Version 3.7.pdf PDF
Attachment 26 - DCB 2019-01 (28).docx DOCX document
Attachment 17c (dtd) - u-suppub8-2012-12-04.txt TXT text file
Attachment 34 - PALM-Correspondence Processing.pptx PPTX presentation
Attachment 26 - DCB 2019-01 (24).docx DOCX document
Attachment 20b - Grant Yellow Book Documentation.docx DOCX document
Attachment 29b - Link to Patent Official Gazette Notices.docx DOCX document
Attachment 10b - 9611570.pdf PDF
Attachment 35b - PE2E-eDRS-Stamp-Annotate-Documents_QRG.pdf PDF
Show all 50

Patent Data and Document Management has more files on GovTribe.

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

File details come from the government source that posted it. Updated .