U.S. Patent and Trademark Office
Information Products Division
Data Dissemination
Trademark Daily XML Migration

October 29, 2004

Trademark Daily XML Files - Weekly Status Report

The following is a status update for all inquiries.

Inquiries can be made to: Ed Johnson at Ed.Johnson@uspto.gov - (703) 306-2621 or Jazmin Rexrode at Jazmin.Rexrode@uspto.gov - (703) 306-2626 or sent to OEIP@uspto.gov.

*The format of the Weekly Status Report will appear as follows:
1. Each inquiry is given a USPTO Control # for tracking purposes.
2. The summary portion of “Status of Inquiries” will be “grouped” by the current status.
3. The detail portion of the report will be in sequence Control # (for easier reference).

~~~

Any inquiries that require additional research and/or response are considered outstanding inquiries and will appear in red, bold and italicized.

Inquiries that have been resolved will have the resolution in black, bold, italicized and underlined.

~~~

For Your Information – FYI:

10/29/2004:

Control #96:

Servers and other hardware are being moved to the USPTO Data Center in Crystal City in preparation of the subsequent move to the Alexandria Campus.

The majority of the equipment maintained by OEIP is used to produce the CASSIS line of optical disc products and the equipment that is used to disseminate the daily trademark files is being replaced.

Phase 1: September 20, 2004 - Hardware used to produce CASSIS products was successfully moved.

Phase 2: September 23, 2004 - Hardware used to produce USAApp and USAPat products was successfully moved.

Phase 3: September 29, 2004 - Hardware used to produce NTAF products was successfully moved.

Phase 4: October 2004 - New hardware to support the Data File Delivery (DFD) FTP system has been ordered and will be installed and configured in the USPTO Data Center in Crystal City.

~~~

08/13/2004:

Requirements and Proposed Schedule for the updated Trademark Daily Applications product – Control #61

Requirements:

Proposed Schedule:

• September 1, 2004 – The updated Daily Application DTD and Documentation to be released. Test files will be made available during the month of September 2004.
  
• October 8, 2004 – Proposed parallel process to include the updated Daily Application product along with the current production product to take place October 8, 2004 through December 31, 2004.

10/29/2004:

It has been noted that the data content has been cleaned up significantly in the updated/new Applications “C” files. Inquires continue to arrive. These inquiries will continue to be thoroughly addressed throughout the parallel process.

• January 3, 2005 – Proposed deployment of the updated Daily Application product into production.

NOTE: Once the updated Daily Application product is accepted and placed into production, the Monthly Status File and the Monthly Contractor Reports will be discontinued in a timely manner.

~~~

04/16/2004:

"The U.S. Patent and Trademark Office is processing paper Madrid filings within a week of receipt and electronic applications within hours. Information is generally viewable on the USPTO website within 24 hours of the completion of Trademark processing. In addition to the work done on Madrid filings at the USPTO, there is also processing at the International Bureau of WIPO. Thus, in certain circumstances pendency is influenced by any backlogs that might develop at WIPO."

~~~

Availability of Files:

10/29/2004:

All files for the week ending October 29, 2004 were available on time.

~~~

Control #95 – 09/27/2004:

These applications 78133250 and 78358000 appear as new application images in the 24 Hour Box without associated XML data.

10/29/2004:

78133250 and 78358000 were both rescanned and placed back in the 24 Hour Box. - The reason that they were rescanned was due to the fact that the image residing at the USPTO was corrupt in some manner and was being replaced.

Note: The documentation for the Trademark 24 Hour Box will be updated to include: If an image appears in the 24 Hour Box “root directory” without associated xml data it can be assumed that this image is replacing an existing image.

The subsequent cropping of rescanned images remains under investigation.

~~~

Status of Inquiries:

10/29/2004:

Closed: Control #108, Control #121, Control #127, Control #128, Control #129, Control #137

In Process:

Control #61, Control #95, Control #96

~~~

Inquiry – 08/13/2004: Control #61 – Requirements Trademark Daily Applications “C” version.

1. The updated Trademark Daily Applications product will include all data fields provided in the current product. Reference the “B” Trademark Applications Daily XML DTD Element Documentation (v1.2) located on the TDXF DTD's, Documentation, and Sample Data page. - Completed.

2. Provide all MADRID PROTOCOL INFORMATION (including Madrid History and Multiple transactions) for applications going to the International Bureau (IB). - Completed.

3. Provide all MADRID PROTOCOL INFORMATION for applications received from the International Bureau (IB). - Completed.

4. Provide status code changes on a daily basis that are now only provided in the Monthly Status file. - Completed.

5. Provide the <location-date> equating to the “Date In Location” on TARR. Provide <law-office-assigned-location-code> equating to Law Office Assigned on TARR. Reference translation on page 15 Trademark-Applications-Documentation-v2.0-10152004.doc on the TDXF DTD's, Documentation, and Sample Data page.
- Completed.

NOTE: The availability of “Current Location” has been presented to the Trademark Business area.

6. Provide the Abandonment-Date and Mis-Assigned Numbers. This information is currently only available in the Monthly Contractor Reports. - Completed.

NOTE: The Abandonment Date is being provided and Mis-Assigned Numbers are provided with a status-code of “622”.

7. Provide 2-character WIPO Standard ST. 3 country codes in the <nationality> field and the <country> field of the <case-file-owner>. Note: The data in the Correspondent Address is free form text and will remain that way.

The use of Table 2 – US States, Countries and Other

Table 2A will contain a 2-position code of all US States.

Table 2B will contain a 2-position code of all Countries.

Table 2C will contain “Other Codes” a 2-position or 3-position code as defined below.

If the third character is a "C", the code is a province of Canada. (e.g., ABC for Alberta and PQC for Quebec).

If the third character is a number, the code is a geographic region of the code that is in the first two positions (e.g., GB1, GB2, CN1, OM1).

If the third character is anything other than a "C" or a number, the code is a Government Agency code (e.g., USA, USN, USF for U.S. Army, Navy, and Air Force). Additionally if the code is only two characters, it can be a Government Agency code (e.g., UA, UN, UF for U.S. Army, Navy, and Air Force).

Note: The country code for Ukraine is “UA” and will appear in the <country> tag. The code for the U.S. Army is also “UA” and will appear in the <other> tag.

The code “XP” can be present in the <country> tag, the <state> tag and the <other> tag and denotes “Stateless” that a Country Code or State Code was not provided.

NOTE:
(1). The <country> tag within <foreign applications> will only contain a 2-position country code from Table 2B.
(2). Within the <nationality> tag the <state> tag using Table 2A, or the <country> tag using Table 2B or the <other> using Table 2C can be present and will be implemented with the Applications “C” dated November 1, 2004.

8. <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> - Completed.

The above statement will be included inside the XML files but not the current “B” version of the Daily Applications file.

9. Reference Control #’s 85, 86, 91 and 97 that were closed in the Trademark Status Report of Friday 10/01/2004. These control numbers are being applied to the daily applications requirements.

#85 - Note: name-1, name-2, name-3, name-overflow will be removed and replaced by: name

The party type and entry-number handle different owner names.

And, if there were a second owner the <entry-number> would equal 02 and the <party-type> would still equal 10.

If there were a subsequent owner that caused a new party-type the <party-type> would increment accordingly and the <entry-number> would start anew at 01. - Completed.

#86 – A valid party-type code will be included with the correspondent party-type. - Completed.

#87 – The <!ELEMENT madrid-international-filing-record will include a international-renewal-date? field and the <!ELEMENT madrid-history-event will include a number field. - Completed.

#88 - The following element <Madrid-international-filing-request> will be renamed to <Madrid-international-filing-requests> - Completed.

#89 –

1. The data elements listed in the international-registration group are for incoming requests from the IB. The new group madrid-international-filing-requests is for outgoing requests to the IB.

2. Records that have abandonment dates are present in the test data file: TestData-v2.0-10082004.xml

3. Table 2 in the Applications Documentation will be updated to accommodate the 2-position Country and State Codes. This table will be edited until all codes are properly identified.
- Completed.

#91 – The correspondent change of Control #91 will be included in the new requirements. If you want to
review the entire Control #91 please reference the weekly status report dated October 01, 2004.
- Completed.

#97 –

1. Missing status-date element: Serial No.: 71/194337, 72/123294

Note: This was corrected in the test data dated and provided 09/24/2004.

2. The <correspondent> group doesn't contain the following tag <person-or-organization-name>

Note: All of those <correspondent> tags are missing and instead <address-1>, <address-2>, <address-3>, <address-4>, <address-5> are used.

The DTD will refer to five lines of address (person-or-organization-name has been changed). It cannot be guaranteed that the value found in this field contains a person or organization. The field name has been changed to address-1. Reference Control #91.

3. The <case-file-owner> contains a tag named <party-name> this should display as <name>. Reference Control #85.

Note: This has been corrected in the test data dated and provided 09/24/2004.

4. The <correspondent> group doesn't match what had been discussed in Control #91

The Status Report should have been updated to reflect the tag names that are being used in the DTD and the Documentation. They are not in sync at the moment. I am referring to #3 and 4 in my list above.

Note: The DTD dated and provided 09/24/2004 has been updated accordingly. - Completed.

10. The international-renewal-date? field has been included and the number field will contain an ascending sequence number. Reference Control #87 that was closed in the Trademark Status Report of Friday 10/01/2004.
- Completed.

11. <Madrid-international-filing-requests>. The “s” has been added to be consistent with the naming convention being used. . Reference Control #88 that was closed in the Trademark Status Report of Friday 10/01/2004.
- Completed.

12. Empty optional tags will not be present in the 2.0 XML data. Reference Control #98 that was closed in the Trademark Status Report of Friday 10/01/2004.
- Completed.

13. The <employee-name> will be provided. Reference Control #100 that was closed in the Trademark Status Report of Friday 10/01/2004. - Completed.

14. Control #107 remains open to resolve Country and State Code issues. - Completed.

15. In each daily XML file the End Of Line character will be a UNIX Linefeed character, hexadecimal “0A”, the decimal 10 - Completed.

NOTE: This will be consistent in all 3 Trademark Daily XML files (Applications, Assignments and TTAB).

16. The dates being sent in <location-date> always contains 2 Leading zeros. All 5093 applications with location dates from apc041012.xml are like this.

Example:

Warning:: DateFormat.isValid() bad date :: 00910404
Warning:: DateFormat.isValid() bad date :: 00910114
Warning:: DateFormat.isValid() bad date :: 00900305
Warning:: DateFormat.isValid() bad date :: 00890925
Warning:: DateFormat.isValid() bad date :: 00891012
Warning:: DateFormat.isValid() bad date :: 00940816
Warning:: DateFormat.isValid() bad date :: 00910617
Warning:: DateFormat.isValid() bad date :: 00950504
Warning:: DateFormat.isValid() bad date :: 00890629
Warning:: DateFormat.isValid() bad date :: 00920313
Warning:: DateFormat.isValid() bad date :: 00890509
Warning:: DateFormat.isValid() bad date :: 00890821
Warning:: DateFormat.isValid() bad date :: 00961130
Warning:: DateFormat.isValid() bad date :: 00890720
Warning:: DateFormat.isValid() bad date :: 00920720
- Completed.

17.

a. The October 17, 2004 “C” daily file contained 1,294 transactions while the “B” daily file for October 17, 2004 contained 2,097 transactions – Why did the “B” contain more transactions? The October 16, 2004 “C” contained more transactions than the “B” for October 16, 2004. 9,295 vs. 3.076 which seems very appropriate.

b. After downloading and processing the “C” version files I have encountered a possible problem specific to the file apc041010.xml. The version "B" for that date had 1501 applications while version "C" had 344 applications. I didn't think the number of applications would decrease when comparing the “B” version and the “C” version for a given date.

The files provided on October 10, 2004 and October 17, 2004 were “weekend data” and the time of day that the “B” file and the “C” were extracted on the weekend appears to be the problem. Further investigation is being conducted.

18. Can you say when the “C” daily files will be available consistently around 12:00 p.m. ET, and is it possible to regenerate any of the prior “C” now that the data content has been cleaned up significantly?

a. The week ending October 29, 2004 saw an improvement on the time of day the “C” file was available and this will continue to improve.

b. It is possible to regenerate prior “C”. Please remember subsequent status changes could make the applications different.

19. The “C” daily file has many more transactions/records than the “B” daily file. Is this due to receiving status changes on a daily basis – while the “B” status changed were received monthly? -Yes.

20. The following code OM7 appears inside <law-office-assigned-location-code> tags and is not documented. The code exists on the following Serial Numbers 76/491065 and 78213916. These marks both have transaction dates of 2003/03/07. The TARR online system displays the law office as M7D -TMO Law Office 116 – Docket Clerk

This will be investigated to determine where the error exists – data or documentation.

~~~

Inquiry – 10/08/2004: Control #108 “C”

This is a consolidation of all inquiries concerning the use of the Nationality, the Country and the State fields.

10/29/2004:

Control #108 is being closed please refer to Control #61 – Requirements for Trademark Daily Applications “C” version, item #7 for the use of Country Codes, State Codes and Other Codes.

~~~

Inquiry – 10/06/2004: Control #121

The tt040930.xml daily XML has 472 bad due dates all of them with the following erroneous data:

<due-date>00011010</due-date>

Example:

<prosecution-entry>
<identifier>38</identifier>
<code>900</code>
<type-code>T</type-code>
<due-date>00011010</due-date>
<date>20020727</date>
<history-text>OPP NO. 119,557 NO ASWER IS REQ AT THIS TIME; CONS OF OPPS; SUSP OF CONS PROC FO</history-text>
</prosecution-entry>

10/29/2004:

There was a problem on how the due date was being received from the applicant. A blanket fix was applied resulting in the erroneous data. This has subsequently been corrected and the corrected records disseminated.

~~~

Inquiry – 10/12/2004: Control #127 “C”

1. There seem to be a lot of elements that do not have any data except a space. For example if I search the document apc041007.xml for the occurrence of "> <" (not including the quotes) I get over 10 000 matches.

<attorney-docket-number> </attorney-docket-number>
<international-registration-number> </international-registration-number>
<mark-identification> </mark-identification>
<registration-number> </registration-number>

This tag name is also affected but occurs with 2 spaces and occurs 946 times:

<country> </country>

10/29/2004:

Space or 2 spaces are present in the data being extracted.

2. The following tag names were sent empty (27 occurrences total):

<entity-statement></entity-statement>
<dba-aka-text></dba-aka-text>
<composed-of-statement></composed-of-statement>
<transaction-date></transaction-date>

<entity-statement></entity-statement>

10/22/04:

This tag being provided empty has been corrected.

<dba-aka-text></dba-aka-text> and the <composed-of- statement></composed-of-statement>

10/22/04:

This tag being provided empty has been corrected.

3. Here are the Serial Numbers with the empty <transaction-date></transaction-date>

<case-file>
<serial-number>78701770</serial-number>
<registration-number>0000000</registration-number>
<transaction-date></transaction-date>
...
<case-file>
<serial-number>78846169</serial-number>
<registration-number>0000000</registration-number>
<transaction-date></transaction-date>

10/22/2004:

This tag being provided empty has been corrected.

~~~

Inquiry – 10/13/2004: Control #128

After downloading and processing the “C” version files I have encountered a possible problem specific to the file apc041010.xml. The version "B" for that date had 1501 applications while version "C" had 344 applications. I didn't think the number of applications would decrease when comparing the “B” version and the “C” version for a given date.

10/29/2004:

This is being closed and investigated with Control #61, item #17.

~~~

Inquiry – 10/13/2004: Control #129 “C”

1. I have processed file apc041012.xml and have encountered bad date records.

Warning:: DateFormat.isValid - bad date :: 9981001

Warning:: DateFormat.isValid - bad date :: 20806

Warning:: DateFormat.isValid - bad date :: 2030100

10/29/2004:

These have been corrected and disseminated.

2. The files apc041008.xml and apc041007.xml application counts are identical which seems suspicious. They both have 16631 applications. I found that we received the same list of serial numbers on the 8th as we did for the 7th. The only difference being that the file on the 8th had data (case-file-event-statements) for the 12th of October (the day it was processed).

10/29/2004:

Research of these 2 files did not find the identical information being reported. Please resubmit if problem is still present.

~~~

Inquiry – 10/20/2004: Control #137

Would you please identify the sequence that assignment information within a given trademark serial number is displayed on the USPTO Assignments on the web.

Example: Serial #: 75280451 has a total of 3 assignments. What data fields are used to sequence these 3 assignments?

10/29/2004:

Trademark assignments on the USPTO website are displayed in ascending sequence by the Execution Date (Exec Dt) followed by the Reel/Frame.

~~~

If you have any questions or need additional information please contact one of the following individuals:

Ed Johnson	Jazmin Rexrode
Office of Electronic Information Products	Office of Electronic Information Products
(703) 306-2621	(703) 306-2626
(703) 306-2737 Fax	(703) 306-2737 Fax
Ed.Johnson@uspto.gov	Jazmin.Rexrode@uspto.gov