PRODUCTS   
Products and Services > Trademark Daily XML Files - Weekly Status Report
U.S. Patent and Trademark Office
Information Products Division
Data Dissemination
Trademark Daily XML Migration

January 17, 2005

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 - (571) 272-5471 or Jazmin Stanback at Jazmin.Stanback@uspto.gov - (571) 272-5477 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:

11/05/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/December 2004 – A new server to support the Data File Delivery (DFD) FTP system has been delivered, installed and configured.

Note: All Trademark Daily XML Files have been disseminated through this new server since Tuesday, December 14, 2004.

~~~

08/13/2004:

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

Requirements:

Proposed Schedule:

~~~

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:

01/17/2005

All Trademark Daily XML Files have been disseminated through a new server since Tuesday, December 14, 2004.

~~~

Status of Inquiries:

1/10/2004:

In Process:

Control #61 – Requirements for Applications “C” version, Items 27, 43 and 44 are opened.

~~~

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). - Control #16, #41 and #55 - 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. - Control #51 and #76 - 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. - Control #68 - Completed.

Note: The <current-location> tag containing the text as it appears in TARR is now present in the Trademark-Applications-DTD-v2.0-11052004 and will be present in the Daily Applications XML file dated November 8, 2004 - Control #134 – Completed.

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

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

- Control #66 - Completed.

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, Territories and Agencies.

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. - Completed.

Control #21 – Completed

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

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

- Control #84 - Completed.

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.

- Control #87 - 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.

- Control #88 - 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.

- Control #98 - Completed.

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

- Control #100 - Completed.

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

- Control #107 - Completed.

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

- Control #125 - Completed.

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

- Control #135 - 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” production file and the “C” parallel files were extracted caused the difference in the volume of transactions.

- Control #128 - Completed.

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.

- Control #139 - Completed.

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 - Control #138 - Completed.

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

The code “0M7” has been added to the documentation.

Control #140 - Completed.

21. Reference the apc041101 file. There appears to be an issue with the classification dates. Sometime included are the 8 digit while other times only 7 digits are present. There are many within this file that have only 7 digits. As an example SN 74409984 has the following data included <first-use-in-commerce-date>9340000</first-use-in- commerce-date>. As you see this is not a valid century.

This is a data content problem and the data provided was what was available. The data field being identified numeric allows any length. The trademark business area must resolve this data content problem.

Control #145 – Completed.

22. There seems to be some issue sending multibyte characters (UTF-8 encoding) with the XML "C" daily version.

The XML "B" daily files currently in production appears OK. But there appears to be a difference between the "B" version and the "C" version.

Version “B” encodes characters (UTF-8 encoding).

Example:
<address-1>29, rue du Faubourg Saint-Honoré</address-1>

Version "C" encodes characters (XML Escape Sequences).

Example:
<address-1>29, rue du Faubourg Saint-Honor&#233;</address-1>

Control #147 – Completed.

23. The file apc041108.xml gives the following error:

Fatal Error at file apc041108.xml, line 5707122, char 42
Message: Expected entity name for reference

Here is the portion of the file showing an improper use of an ampersand character

<case-file>
<serial-number>78508904</serial-number>
<registration-number>0000000</registration-number>
<transaction-date>20041108</transaction-date>
<foreign-applications>
<foreign-application>
<registration-date>20031202</registration-date>
<registration-expiration-date>20131202 </registration-expiration- date>
<entry-number>1</entry-number>
<country>AU</country>
<registration-number>980593 & 986</registration-number>
<foreign-priority-claim-in>F</foreign-priority-claim-in>
</foreign-application></foreign-applications>

The program was not escaping characters properly and has been corrected as of the APC file dated November 15, 2004.

Control #148 – Completed.

24. Words are being squeezed together in the XML daily. Serial No. 78/508904 is an example. This Serial No. on TARR appears correct.

<case-file-statement>
<type-code>GS0281</type-code>
<text>Play articles and accessories for use in swimming, swimming pools and beach useincluding masks, snorkels, fins, combined mask, snorkel and fins; flippers for swimming, swimming webs (flippers); inflatable including kickers, bubbles being swimming aids, EVA (ethylene vinyl acetate) bubbles being swimming aids, rings tubes, kiddie floats, balls, pools including inflatable pools and shade pools, repair kits for pools, squirting/spraying novelty devices, floating toys, water slides, floating mats, floating boards, floating boats, plastic oars, dive sticks and seahorses, water game sets, foam toys, foam pool noodles, inflatable pool toys, plastic buckets, plastic rakes, plastic spades, plastic sand moulds, plasticwatering cans, plastic sieves, flying disks, plastic shapes, plastic shovels, plastic hoes, plastic sandpits, kickboards, surf boards, body boards, body board leashes, mini soft balls, playthings made of foam, ring games, pool games, gymnastic articles and assorted novelty pool toys</text>
</case-file-statement>

This is how the data content is being provided.

Control #149 – Completed.

25. It seems that the <dba-aka-text> field (which is part of the <case-file-owner> field) is being excluded from the latest Trademark-Applications "C" files. I could not find this field in the following Trademark-Applications "C" files:

apc041108.xml, apc041109.xml, apc041110.xml, and apc041111.xml. But I was able to find this field in all of the following Trademark-Applications "B" files: apb041108.xml, apb041109.xml, apb041110.xml, and apb041111.xml.

For example, in the recent Trademark-Applications "B" file named apb041108.xml, Serial Number 76618555 contains a <dba-aka-text> field (where the value is "TA Sony Computer Entertainment Inc.") for the <case-file-owner> field where the Party Type is equal to 10. For the same Serial Number in the apc041108.xml file, a <dba-aka-text> field cannot be found.

The program has been fixed and a replacement file will be provided.

Control #150 – Completed.

26.

A. I wanted to confirm that there are no "new" records in the apb041111.zip file: i.e., there are no new trademark filings today. Normally we get from 500-1500 new records daily. Today's file showed zero new and 5979 updated records.

B. As a suggestion for future development, it would be a great help if the header of each file (apb, asb and tt) would provide stats on the total number of records in the file. In this way, we can verify that the counts we load into our Oracle database are correct against the counts in the file header.

The applications file dated November 11, 2004 was for Thursday, Veterans Day. No new applications were processed that day.

All files being disseminated including to the USPTO’s TESS and TARR databases are created in the same manner with the same transactions each day. To provide totals as header information would be a major undertaking and will not be considered at this time.

Control #151 – Completed.

27. The file apc041118.xml contained Serial No.: 76/520716 with its trademark defined using the following XML Escape Sequences:

<case-file>
<serial-number>76520716</serial-number>
<registration-number>0000000</registration-number>
<transaction-date>20041118</transaction-date>
<case-file-header>
<filing-date>20030527</filing-date>
<status-code>602</status-code>
<status-date>20040621</status-date>
<mark-identification>&#165;&#191;$</mark-identification>
<mark-drawing-code>5000</mark-drawing-code>

The escape sequence &#191; is an 'Inverted Question Mark', this application is supposed to have a 'Euro' symbol displayed at that location:

(words only): ¥€$

Please look at TARR for the correct mark-identification text:

http://tarr.uspto.gov/servlet/tarr?regser=serial&entry=76520716&action=Request+Status

Control #156 – 01/17/2004, this continues to be investigated in an event to have characters on TARR and those disseminated daily to be the same.

28. We are expecting to receive OG related transactions on Wednesday morning (after 2 am). However we have been seeing these type of transactions on the “C” file that we receive on Monday morning with dates that are in the future 20041221 for registration dates, publication dates etc. Is this what we should be expecting?

The OG related transactions are only available through each Monday night. It is being disseminated on the Application “C” file dated each Monday and be available each Tuesday morning at 2:00 a.m. ET.

The OG related transactions present on the Application “B” file was/is extracted each Friday for disseminated each Tuesday morning at 2:00 a.m. ET.

Control #157 – Completed

29. Just wanted to point out that within the Applications ELEMENT DOCUMENTATION sent out on 11/19/04 -- you have that TABLE 5 PROSECUTION HISTORY EVENT CODE LIST is new in version 'C'. It has been updated and sorted differently but it's TABLE 6 that is new in version 'C'.

12/27/2004

Table 5 was updated and Table 6 is new (table 5 will be shown in green. The red codes will remain because of the volume of codes to investigate between old and new).

Note: The Trademark-Applications-Documentation-v2.0-12142004 contain this change.

Control #158 – 12/27/2004, Completed

30. There are now 2 formats for the USPTO Reference Number - Z123nnnn and Annnnnnn. Will the "Z" prefix be used on manual filings and the "A" prefix on electronic filings? Will the USPTO reintroduce the requirement that all Madrid filings be done electronically?

Control #159 – 01/10/2005, “Z” prefix are manual filings and the “A” prefix are electronic
filings. All electronic filings is a goal.

31. Control #147 is being re-opened as Control #160

There continues to be some issue sending multibyte characters (UTF-8 encoding) with the XML "C" daily
version.

The XML "B" daily files currently in production appears OK. But there appears to be a difference between the
"B" version and the "C" version.

Three records from the apc041203.xml file are:
75807059, 75924261, 76388317

The untranslated chars appear as follows: &#nnn; where nnn represents a 3-digit number. I found 62 different
strings in this file alone.

Note: The databases that contain the source data that is input to the Applications “C” file does
not support mult-byte characters. Therefore, the Applications “C” will contain XML Escape
Sequences.

Control #160 – 12/27/2004, Completed

32. The “C” data file apc041205.xml contained 0 records (data-available-code=N). When the "B" data file apb041205.xml had 2054 applications for the same day. How can this happen during a parallel process?

The timing that the “B” file is extracted for weekend files all flags have been re-set for the subsequent extraction of the “C” file.

Control #161 – Completed

33.

1. What is the holiday schedule for the USPTO delivery of files?

The Trademark Daily Applications, Assignments and the TTAB files will be available on the Federal Holidays for Christmas and New Years. As is the current practice if a file has no transactions for a given day 0 records will be identified.

The Trademark 24 Hour Box being a 5 day a week file will not be available on Saturday, December 25, 2004 or Saturday January 1, 2005.

2. Will we receive another MOST in January for the December transactions?

A December Monthly Status File (MOST) will be available on Tuesday, January 4, 2004.

3. Is the January 3rd still the targeted deployment date for the "C" version into production.

If the Daily Application “C” file is completely stable and accepted by January 3, 2005 the file dated Monday January 3, 2005 available Tuesday, 2:00 a.m., January 4, 2005 would be considered the first Application “C” production file.

Please Note: At a minimum the Daily Application “B” file will be available through the file dated Friday, January 14, 2005.

Control #162 – Completed

34. Serial Number 76621221 from the apc041206 file has a Action-key of TX but doesn't have date-filed, mark-
identification, owner information. There are some 2700 records in the file that are similar to this one:

a. It has been stated that these "TX" transactions are pre "NA" and eventually become "NA" transactions with all appropriate data fields completed.

b. In the past when we have notified the USPTO about 5 or 10 records in the current daily file being like these, we have been told that they should not have been disseminated to the clients and stopped these from being disseminated in the daily files. How are these 2700 records different? This seems like unnecessary processing on the USPTO side.

To ensure that everything present in TESS and TARR and all daily status changes are being disseminated, the daily XML Applications “C” file is subject to contain data records that all fields are not populated.

Control #163 - Completed

35. Using the apc041206 file, there is an action-key of 05. This is not a valid action-key. There are 1930 records with this action-key.

Note: Action-Key 05 is an invalid OG category. These records should have been disseminated as TX records.

Control #164 – 12/27/2004 - Completed

36. The <first-use-anywhere-date> in the following example "76183105" of the apc041206 file contains the value 50000.

<case-file>
<serial-number>76183105</serial-number>
<registration-number>0000000</registration-number>
<transaction-date>20041206</transaction-date>
<case-file-header>
...
<first-use-anywhere-date>50000</first-use-anywhere-date>
...

This registration is based on Section 44(e) - ownership of a registration issued by another country that is a member of the Paris Convention (a treaty the USPTO is a member of) - so there are no use dates. All use date values should be “0.”

Control #165 – 01/10/2005, This was corrected on the filed dated 12/22/2004.

37. The following example is from the apc041206 file, however this is happening on the apb files as well. We are seeing that the section-2f-in and the section-2f-in-part-in fields are both having a 'T'. It's our understanding that you can file either a partial Section 2f or a Section 2f, but not both of these. Could you confirm that this is true?

This is a new application filed via TEAS. It has assigned to an examining attorney, but it has not yet been examined.

The applicant submitted a 2(f) claim and a 2(f)-in-part claim via the TEAS form. The form does not contain an edit prohibiting this, but the mark may not be approved for publication until one of the claims is deleted. The examining attorney will require that one of the 2(f) claims be deleted prior to allowance for publication.

Control #166 – Completed

38. The following status codes and description have been included in the attached Trademark-Applications-Documentation-v2.0-12142004.doc.

657 - "PRIORITY ACTION COUNTED NOT MAILED"
658 - "PRIORITY ACTION MAILED"
822 - "SU - PRIORITY ACTION COUNTED NOT MAILED"
823 - "SU - PRIORITY ACTION MAILED"

Control #167 – Completed

39. The following error was present in the apc041205 file.

[Fatal Error] apc041205.xml:269:3:

The element type "application-information" must be terminated by the matching end-tag "</application-information>". error: Parse error occurred - The element type "application-information" must be terminated by the matching end-tag "</application-information>".

The software has been corrected and the apc041205 file re-created and disseminated on 12/06/2004.

Control #168 – Completed

40. Please clarify something for me. Will the “C” version contain the status changes that we used to only receive within the Monthly Status Tape? And, will these transactions will be included in the C version with a action-key of TX (miscellaneous change)?

The answer to both inquiries is – Yes.

Control #169 – Completed

41. We continue to see issues related to the <case-file-owner> field in the latest Trademark-Applications "C" files.

1. The <dba-aka-text> field (which is part of the <case-file-owner> field) continues to be excluded from the latest Trademark-Applications "C" files. I could not find this field in the following Trademark-Applications "C" files: apc041211.xml and apc041212.xml. But I was able to find this field in the following Trademark-Applications "B" files: apb041211.xml and apb041212.xml.

2. The <composed-of-statement> field (which is part of the <case-file-owner> field) continues to be excluded from the latest Trademark-Applications "C" files. I could not find this field in the following Trademark-Applications "C" files: apc041211.xml and apc041212.xml. But I was able to find this field in the following Trademark-Applications "B" files: apb041211.xml and apb041212.xml.

3. The <entity-statement> field (which is part of the <case-file-owner> field) continues to be excluded from the latest Trademark-Applications "C" files. I could not find this field in the following Trademark-Applications "C" files: apc041211.xml and apc041212.xml. But I was able to find this field in the following Trademark-Applications "B" files: apb041211.xml and apb041212.xml.

4. For an <address-1> field (which is part of the <case-file-owner> field) which happens to exceed 40 characters in length, no more than the first 40 characters of the <address-1> field is being provided by the latest Trademark-Applications "C" files. This is not the case for the Trademark-Applications "B" files (which do provide the entire <address-1> field when it does exceed 40 characters in length).

5. The Section 2(f) Limitation Statement is being excluded from the latest Trademark-Applications "C" files for some reason. The Section 2(f) Limitation Statement is found in the <text> field for the occurrence of the <type-code> field where the first two characters are equal to "TF" for the appropriate <case-file-statement> field. I could not find the Section 2(f) Limitation Statement in the following Trademark-Applications "C" files: apc041211.xml and apc041212.xml. But I was able to find this field in the following Trademark-Applications "B" files: apb041211.xml and apb041212.xml.

Items 1 through 5 above have been corrected beginning with the Applications “C” file dated 12/21/2004. A corrected supplemental file, containing data records for October 7, 2004 through December 20, 2004 was available on the FTP site January 11, 2005.

6. Multi-byte characters (that currently appear in the Trademark-Applications "B" files) are now showing up as XML Escape Sequences in the Trademark-Applications "C" files.

Item 6. The databases that contain the source data that is input to the Applications “C” file does not support multi-byte characters. Therefore, the Applications “C” will contain XML Escape Sequences.

Control #170 – 12/27/2004, Completed

42. Fatal Error at file C:\usr3\us\pto\xml\041227\as041227.xml, line 99, char 285

<reel-no>2997</reel-no><frame-no>0136</frame-no>
<person-or-organization-name>CHASTITY M. TURI?</person-or-organization-name>

Fatal Error at file
C:\usr3\us\pto\xml\041229\as041229.xml, line 226, char 277

<reel-no>2999</reel-no><frame-no>0202</frame-no>
<person-or-organization-name>ARTURO P?EZ- GUERRERO</person-or-organization-name>

Correction applied to the software January 6, 2005.

Control #176 – Completed

43. The file apc041229.xml which contains Serial No.: 75/507712 does not have the <attorney-name> element, in
fact none of the serial numbers in this particular file have that element. The attorney name information seems to
have disappeared.

This was corrected with the applications “C” file dated January 5, 2005.

A supplemental file containing corrected data records for the period November 1, 2004 through January 4, 2005 will be provided.

Control #177 – Awaiting a supplemental corrected file.

44. I checked the status file against the data we received in December and the Monthly Status File had 111 status
dates updated on December 5th, 2004, yet the XML "C" daily for the 5th of December contained NO Serial
Numbers. They are included in the list below.

The status file also contained 19 Serial Numbers which had their status updated on December 16th, 2004, we
have never received any XML "C" daily data to update those. They are also included in the list below.

A list of Serial Numbers is attached with our current transaction date, and status date which contains the
value from the monthly status file. The transaction date should be greater than or equal to the status date
received in the monthly status. The list is sorted by STATUS_DATE, SERIAL_NUMBER.

Control #179 – 1/17/2005 investigation continues

45. Invalid transaction dates (22,768) appear in the Supplemental File that was to correct records as defined
in item 41.

$ grep '<transaction-date>' apc-fixed.xml
<transaction-date>22-fixed</transaction-date>
<transaction-date>22-fixed</transaction-date>
<transaction-date>22-fixed</transaction-date>
<transaction-date>22-fixed</transaction-date>
<transaction-date>22-fixed</transaction-date>
<transaction-date>22-fixed</transaction-date>
<transaction-date>22-fixed</transaction-date>
<transaction-date>22-fixed</transaction-date>
<transaction-date>22-fixed</transaction-date>
<transaction-date>22-fixed</transaction-date>
<transaction-date>22-fixed</transaction-date>
<transaction-date>22-fixed</transaction-date>
<transaction-date>22-fixed</transaction-date>
<transaction-date>22-fixed</transaction-date>
<transaction-date>22-fixed</transaction-date>
<transaction-date>22-fixed</transaction-date>

A corrected supplemental file, containing data records for October 7, 2004 through December 20, 2004 was available on the FTP site January 11, 2005.

Control #180 – Completed

46. We've found on the files (apc050103 and apc041220) action-keys of 00 (Published for Opposition) with records that do not have a published-for-opposition-date. After further investigation we found that these have a status-code of 692 (Withdrawn from Publication). We believe that these should be action-key of TX.

These records were disseminated correctly. They were planned for publication and were withdrawn, hence the status of 692 and no published for opposition date.

Control #181 - Completed

47. What is the effect of an International Registration cancellation on a basic application?

Is the basic application cancelled upon the cancellation of the International Registration? (Status 400-403).

The U.S. basic application stands or falls based only on U.S. Law; the cancellation of the International
Registration has no effect on the basic application. Of course, the primary reason for canceling an
International Registration is the death of the underlying basic application.

Control #184 – Completed

48. Using the apc050110.zip file we have the following issues that we'd like to have you address. Some of these are issues that you are aware of and identified in Control #163, but wanted to show that it's still happening within
the latest files.

There are 3257 records disseminated with the USPTO STATUS CODE = 630 and DATE_FILED is not present.

To ensure that everything present in TESS and TARR and all daily status changes are being disseminated, the daily XML Applications “C” file is subject to contain data records that all fields are not populated.

Control #185 – Completed

~~~

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

Ed Johnson Jazmin Stanback
Office of Electronic Information Products Office of Electronic Information Products
(571) 272-5471 (571) 272-5477
(571) 273-0110 Fax (571) 273-0110 Fax
Ed.Johnson@uspto.gov Jazmin.Stanback@uspto.gov

Is there a question about what the USPTO can or cannot do that you cannot find an answer for? Send questions about USPTO programs and services to the USPTO Contact Center (UCC). You can suggest USPTO webpages or material you would like featured on this section by E-mail to the webmaster@uspto.gov. While we cannot promise to accommodate all requests, your suggestions will be considered and may lead to other improvements on the website.

 
|HOME | SITE INDEX| SEARCH | eBUSINESS | HELP | PRIVACY POLICY