|
February 27, 2004
Trademark Daily XML Files - Weekly Status Report
Inquiries can be made to: Ed Johnson at Ed.Johnson@uspto.gov - (703) 306-2621 or Marva Dubar at Marva.Dubar@uspto.gov - (703) 305-1669 or sent to OEIP@uspto.gov.
The following is a status update on new inquiries and outstanding items.
New This Week:
*The status on the availability of the 2003 Annual Trademark (Retrospective) files is as follows:
-The 2003 Annual Trademark Assignment file will be available the week ending March 5, 2004.
-The 2003 Annual Trademark TTAB file will be available the week ending March 5, 2004.
-The 2003 Annual Applications (Live and Dead) files will be available the week ending March 12, 2004
There are 2 new inquiries in this Weekly Status Report. Reference New Inquiries:
There are 11 inquiries dating back to June 6, 2003.
*2 have been resolved. Reference (2), and (5).
*3 remain open with any current action to these inquiries being evaluated. Reference Inquiries (6), (7) and (11).
*5 are being analyzed to ensure that valid UTF-8 characters are being used and corrected provided by March 30, 2004. Reference Inquiries (3), (4), (8), (9) and (10).
*1 is open with the appropriate staff analyzing a resolution (1).Inquiries that have been resolved will have the resolution in black, bold, italicized and underlined.
Any inquiries that require additional research and/or response are considered outstanding inquiries and will appear in red, bold and italicized.
~~~
New Inquiries:
Inquiry - 02/26/2004: (1)
In the tt040225.zip file, there are three numbers (proceeding-entry) with no property-information. They are 92042952, 91159572 and 91159577. Using BISX on the USPTO website, none of these are available. We've been having about three of these a day within the TTAB daily feed -- they are different proceeding numbers but it is almost a daily occurrence that we see a proceeding number with no property-information present.
These records have been created in error and should not be present. We are in contact with the appropriate TTAB staff in an effort to eliminate these errors from occurring and appearing on the daily files. Please note: Proceeding numbers associated with these errors will never be valid.
~~~
Inquiry – 02/24/2004: (2)
The 24 Hour Box files (hr040105 and hr040106) contain a <type-code> of MK in the <case-file-statement>. MK is not defined as being a possible <type-code> choice in the 24 Hour Box. Is this something we should/could expect to see in the future for the 24 Hour Box?
The 24 Hour Box DTD’s have not changed. MK should not be present. DM "Description of the Mark" should be present for these records.
~~~
Outstanding Inquiries:
Inquiry – 02/05/2004:(3)
Characters such as diacritical marks appear not to be handled properly. In the daily file dated 20040120 two examples (SN 79000127 and SN 7900022) the umlauted lu (ü) and the circumflexed a (â) that appear in the city names Zürich and Neuchâtel are not provided as ISO entity variables "ü" and "â" respectively. Meanwhile, other characters, such as punctuation, are rendered correctly, e.g. the ampersand "&" is sent as "&".
All 3 Trademark Daily DTD’s are being analyzed to ensure that valid UTF-8 characters are being used and corrected by March 30, 2004.
~~~Inquiry – 02/06/2004:(4)
While processing XML File xml\040205\ap040205.xml an invalid UTF-8 character (Unicode: 0x4) was found in the element content of the document.
All 3 Trademark Daily DTD’s are being analyzed to ensure that valid UTF-8 characters are being used and corrected by March 30, 2004.
~~~
Inquiry – 01/20/2004:(5)
In the apb040120 and apb040121 there is a new type-code included in the case-file-statement section -- it is TNSF. Can you tell us what this is?
*TNSF is a new type-code that identifies Transformation Information. When a birth arrives in the US from the International Bureau (IB) a US serial number is assigned making the International Registration Number no longer valid. The applicant elects to have the application become a US National Application. Thus the transformation. Reference the type-code in the Trademark-Applications-Documentation-v.12.doc under Trademark Daily XML Documentation "B" of the TDXF DTD's, Documentation, and Sample Data page.
*The TNSF entries present in the apb040120 and the apb040121 files were erroneous/premature.
*The above erroneous/premature TNSF entries were corrected to reflect that they were not TNSF entries in the daily application file dated February 26, 2004. Please note: No TNSF data records have been processed to date.
~~~
Inquiry – 11/12/2003:(6)
1. Using the Serial Number 78244966 as an example, this application has made a request for extension under Madrid Protocol to another country. Out on TARR you have the following Madrid Protocol Information:
USPTO Control Number: Z1230001
International Registration Number:
International Registration Date: (DATE NOT AVAILABLE)
Original Filing Date with USPTO: 2003-11-02
Priority Claimed: No
Date of Section 67 Priority Claim: (DATE NOT AVAILABLE)
International Registration Status: Application For
International Registration Certified
Date of International Registration Status: 2003-11-03
International Registration Renewal Date: (DATE NOT
AVAILABLE)
Date of Automatic Protection: (DATE NOT AVAILABLE)
Date International Registration Cancelled: (DATE NOT
AVAILABLE)
Date of Last Irregularity: (DATE NOT AVAILABLE)
First Refusal: NoWill we be receiving this information on an existing application/registration that has requested protection outside the U.S.? If so when and where? Will the IB Update the information that states (DATE NOT AVAILABLE) with the appropriate information? and will that then be received in the daily feeds?
There appear to be three fields listed here that are not included in the Applications DTD v0.10 -- they are USPTO Control Number, Original Filing Date with USPTO, and Date of Last Irregularity. And the last issue with this particular Serial Number, have you sent this record to WIPO yet, as it is not on the WIPO's Madrid Express database?
Responses for this inquiry are being coordinated with Trademark Operations and action to this inquiry is being re-evaluated.
~~~
Inquiry – 10/31/2003:(7)
Correspondent and owner information are provided.
It is requested that the telephone number, the fax number and email address, if available information, for the correspondent and owner be provided.
Current action to this inquiry is being evaluated.
~~~
Inquiry – 10/9/2003:(8)
The TTAB daily file continues to contain illegal characters. I thought this issue would be resolved by now. Here is an excerpt from my log: 2003-10-09 02:09:14 tt031008.xml error: Parse error occurred - An invalid XML character (Unicode: 0x12) was found in the element ...
All 3 Trademark Daily DTD’s are being analyzed to ensure that valid UTF-8 characters are being used and corrected by March 30, 2004.~~~
Inquiry – 9/17/2003:(9)
All the XML files are supposed to be in UTF-8 format.
The following file TTAB tt030701.xml has ASCII value 146 twice in the following line.
ADMIN</charge-to-employee-name><status-update-date>20021008</status-
update-date><status-code>9</status-code><party-
information><party><identifier>260024</identifier><role-code>D</role-
code><name>PAT O'BRIEN'S BAR, INC.</name><property-
information><property><identifier>245280</identifier>
The single quotes being sent to us are not in UTF-8 format.
This type of error can also be found in other TTAB xml files:
tt030515.xml
tt030711.xml
This is brought up because the TTAB files are still being produced with invalid charactersAll 3 Trademark Daily DTD’s are being analyzed to ensure that valid UTF-8 characters are being used and corrected by March 30, 2004.
~~~
Inquiry - 7/16/2003:(10)
Here is some more information/errors....
Processing XML File ==> xml\030620\tt030620.xml
start:: Wed Jul 16 12:05:31 EDT 2003
[Fatal Error] tt030620.xml:145:67181: An invalid XML character (Unicode: 0x12)
was found in the element content of the document.
error: Parse error occurred - An invalid XML character (Unicode: 0x12) was
found in the element content of the document.[Fatal Error] tt030621.xml:144:390195: An invalid XML character (Unicode: 0x12) was found in the element content of the document.
error: Parse error occurred - An invalid XML character (Unicode: 0x12) was found in the element content of the document.Processing XML File ==> xml\030625\tt030625.xml
start:: Wed Jul 16 12:14:58 EDT 2003
[Fatal Error] tt030625.xml:141:728318: An invalid XML character (Unicode:
0x12) was found in the element content of the document.
error: Parse error occurred - An invalid XML character (Unicode: 0x12) was
found in the element content of the document.Processing XML File ==> xml\030626\tt030626.xml
start:: Wed Jul 16 13:05:46 EDT 2003
[Fatal Error] tt030626.xml:143:292294: An invalid XML character (Unicode:
0x12) was found in the element content of the document.
error: Parse error occurred - An invalid XML character (Unicode: 0x12) was
found in the element content of the document.
All of the characters 0 through 31 and character 127 are nonprinting control
characters. With the exception of characters 09, 10, and 13, (Ox09,
Ox0A, and Ox0D) the others may NOT appear anywhere in an XML document.All 3 Trademark Daily DTD’s are being analyzed to ensure that valid UTF-8 characters are being used and corrected by March 30, 2004.
~~~
Inquiry - 6/06/2003:(11)
In reviewing the country codes for each of the 3 XML files and discovered the following
*Trademark-Applications XML
Uses 3 digit code from TWTF file
*Trademark-Assignments XML
Uses no codes at all, they expand all codes (Spelling out countries)
*Trademark-Proceedings XML
Uses officially designated country as prescribed by the World Intellectual Property Organization (WIPO) Standard ST.3
This inquiry has been forwarded to the Office of Data Architecture and Services for evaluation.
~~~
If you have any questions or need additional information please contact one of the following individuals:
Ed Johnson Marva Dubar Information Products Division Information Dissemination Data Dissemination Branch Systems Division (703) 306-2621 (703) 305-1669 (703) 306-2737 Fax (703) 308-5164 Fax Ed.Johnson@uspto.gov Marva.Dubar@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 Email 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.
|
|