Red Book ICE (Grants and Applications) Open Issues

Products and Services > Red Book ICE (Grants and Applications) Open Issues

Red Book ICE (Grants and Applications) Open Issues
Weekly Status Report - April 29, 2005
Item Number Date Reported Description and Status

1
December 14,
2004
Private use area Unicode characters cannot be rendered in Red Book (Patent Grants and Patent Applications)
January 14, 2005 - Investigating cause and resolution.

February 1, 2005 - Caused by data capture contractor using a version of Mathematica that uses a MathML version based on a outdated version of Unicode where some math symbols were assigned private use area code points.

March 10, 2005 - Data capture contractor is exploring options with Wolfram Research, publishers of Mathematica.

April 15, 2005 - Starting with the patent grant Red Book issue May 10, 2005, and the patent application Red Book issue May 12, 2005, private use area Unicode characters will be captured as images and will be included within the XML instance as either a custom-character element or processing instruction.

April 22, 2005 - Resolution as cited above remains in place.

April 29, 2005 - The data capture contractor has identified all private use characters in the Grants Issued 20050510 and Application Published 20050512. The source of these characters is the wipo.ent and the mmlextra.ent entity files provided with the ICE DTDs. The data capture contractor has also proposed replacement markup utilizing embedded images and combined Unicode characters for the wipo.ent derived characters, and descriptive text markup for the mmlextra.ent characters.

The USPTO needs to evaluate these recommendations and understand the impact on search systems and USPTO customers. Consequently the elimination of private use characters from Red Book has been postponed until the replacement markup has been approved and USPTO customers notified of the changes.

2 March 3,
2005
MathML contains invalid line end characters in Red Book (Patent Grants and Patent Applications)

March 10, 2005 - MathML as generated by Mathematica includes character entities for line end/line feed that are converted inappropriately during the general conversion of named character entities to hexadecimal Unicode character entities.

April 15, 2005 - This is still being investigated.

April 22, 2005 - Data capture contractor is planning to resolve this issue internally and it will not be necessary to work with Wolfram Research.

April 29, 2005 - The data capture contractor has identified a set of mathml characters impacted by the hexadecimal Unicode conversion requirement. They are characters such as:

&NewLine;
&IndentingNewLine;
&RawReturn;

Newline has a unique mapping problem since the mmlextra.ent entity file (for both Mathml1 and Mathml2) equates this to either 
 or 
, both of which are resolved by the transformation scripts to a line break/line feed.

ICE Red Book mathml processing requirements need clarified prior to resolving this item. If the requirement is for searching content, then these characters can be replaced with a descriptive form and eliminate the private use characters. If the requirement is to render using available COTS mathml tools, and these tools utilize the private use characters, then any altering of the entities is a potential problem. If the requirement is to be able to re-import the mathml model back into Mathematica, then again altering the entity content creates problems.

3 March 4,
2005
Some num attribute values include the word “header-“ as a prefix in Red Book (Patent Grants and Patent Applications)

April 29, 2005 - This has been resolved. Please reference the Red Book ICE Status Report dated April 22, 2005.

4 March 8,
2005
Num attribute values not consistent between Patent Application Red Book and Patent Grant Red Book

April 29, 2005 - This has been resolved. Please reference the Red Book ICE Status Report dated April 22, 2005.

5 March 14,
2005
Table “footnotes” no longer tagged as such in Red Book (Patent Grants and Patent Applications)

April 29, 2005 - Please reference the Red Book ICE Status Report dated April 22, 2005

6 March 16,
2005
References to non-US patent documents missing “/” in some positions in Red Book (Patent Grants and Patent Applications)

April 1, 2005 - Caused by a conversion step in creating Red Book (Patents Grants and Patent Applications) ICE, which has been in effect since at least October 2004. Red Book Viewer compensates by inserting “/” in the correct position. Data capture contractor investigating the reason for the deliberate removal of the slash.

April 29, 2005 - This continues to be investigated.

7 March 18,
2005
The appearance of the International Patent Classification (IPC) in the Patent Grant Data/XML v4.0 (ICE) beginning February 8, 2005 and in the Patent Application Data/XML v4.0 (ICE) beginning February 10, 2005 changed

April 29, 2005 - This has been resolved. Please reference the Red Book ICE Status Report dated April 15, 2005.

8 April 4,
2005
Legacy descriptive text markup(e.g., <city>Schw{hacek over (a)}bisch Gmünd</city> ) in Red Book (Patent Grants and Patent Applications)

April 5, 2005 - There are a significant number of legacy descriptive text markup instances that can be converted to Unicode, but not without potentially large labor costs. USPTO is investigating the appropriate course of action. Reference FAQ 61. In fact, there are far more instances of descriptive text markup than was apparent at that time.

April 15, 2005 - This is still open to a possible resolution.

April 22, 2005 - This continues to be investigated.

April 29, 2005 - The data capture contractor has proposed combined Unicode characters as a possible replacement for some of the single character descriptive text markup. The proposal is being reviewed by the USPTO.

9 April 5,
2005
Synchronizing num attribute values between Yellow Book (Patent Grants and Patent Applications) and Red Book (Patent Grants and Patent Applications)

April 5, 2005 - It has been reported that the values of the num attribute are not always consecutive, and that they do not always match Yellow Book.

This is a combined consequence of the conversion of markup from Red Book ST.32 to Red Book ST.36 (ICE) and the differences in markup practice between the two.

April 5, 2005 - Starting the week of April 18, 2005, num attribute values will be consecutive, except where they are not to be displayed at rendering. Where the num attribute value is not to be displayed, the value is set to “0000”. See below for further details.

April 5, 2005 - Effective the week of April 18, 2005, Grant Red Book ICE Issues will implement the following changes:

ICE element us-patent-grant attribute status now contains the value of "PRODUCTION".

The heading-paragraph markup now utilizes the id attribute instead of the num attribute, and is in the form of <p id="h-nnnn" num="0000">.

If a paragraph or list item contains only unordered-list content or starts off with an unordered-list, the num attribute contains zeroes and is not to be displayed (num="0000").

All p & li num attributes are now padded to 4 characters.

The abstract and heading-paragraph num attribute is always "0000".

Attributes id and num in elements p, li, ul, and heading are now always lower case, and have been renumbered per the specifications defined below.

Attributes id and num renumbering specifications within elements heading, p, ul, and li:

attribute id specifications in p, heading, ul, and li:

1. headings and heading-paragraphs are numbered sequentially as encountered in the document using the form of id="h-nnnn"
2. remaining paragraphs are numbered sequentially as encountered in the document using the form of id="p-nnnn"
3. unordered lists are numbered sequentially as encountered in the document using the form of id="ulnnnn"
4. list items are numbered sequentially as encountered within its parent unordered list using the form of id="ulnnnn-nnnn". The 2nd nnnn starts with 0001 for each unordered list.

attribute num specifications in p and li:

1. heading-paragraphs always have a value of num="0000".
2. abstract paragraph(s) always have a value of num="0000".
3. If a paragraph starts with an unordered list, it will have a value of num="0000".
4. If a list item starts with an unordered list, it will have a value of num="0000".
5. All remaining paragraphs and list items are numbered sequentially in the form of num="nnnn".

Sample data and style sheet for Patent Application Red Book

Sample data and style sheet for Patent Grant Red Book

April 15, 2005 - We are still investigating to ensure that the num attribute in Yellow Book images matches the num attribute text in Red Book text.

April 29, 2005 - This continues to be investigated.

July 18, 2006 - Text revised.

10
April 19,
2005

There were no prior publication data for 20050000097 in Red Book ICE although there are 3 documents present in the Yellow Book 2 image file.

April 22, 2005 - This will be corrected beginning with the application publication of May 5, 2005.

April 29, 2005 - Resolution as cited above remains in place.

11 April 19,
2005
There is an inconsistency between Red Book ICE and Yellow Book 2 in indentification of References Cited by Examiner and References Cited by Others.

April 29, 2005 - This continues to be investigated.

XML Resources at USPTO

Red Book ICE Information

FAQ for ICE

Red Book ICE (Grants and Applications) Open Issues
Weekly Status Report - April 29, 2005
Item Number	Date Reported	Description and Status
1	December 14, 2004	Private use area Unicode characters cannot be rendered in Red Book (Patent Grants and Patent Applications) January 14, 2005 - Investigating cause and resolution. February 1, 2005 - Caused by data capture contractor using a version of Mathematica that uses a MathML version based on a outdated version of Unicode where some math symbols were assigned private use area code points. March 10, 2005 - Data capture contractor is exploring options with Wolfram Research, publishers of Mathematica. April 15, 2005 - Starting with the patent grant Red Book issue May 10, 2005, and the patent application Red Book issue May 12, 2005, private use area Unicode characters will be captured as images and will be included within the XML instance as either a custom-character element or processing instruction. April 22, 2005 - Resolution as cited above remains in place. April 29, 2005 - The data capture contractor has identified all private use characters in the Grants Issued 20050510 and Application Published 20050512. The source of these characters is the wipo.ent and the mmlextra.ent entity files provided with the ICE DTDs. The data capture contractor has also proposed replacement markup utilizing embedded images and combined Unicode characters for the wipo.ent derived characters, and descriptive text markup for the mmlextra.ent characters. The USPTO needs to evaluate these recommendations and understand the impact on search systems and USPTO customers. Consequently the elimination of private use characters from Red Book has been postponed until the replacement markup has been approved and USPTO customers notified of the changes.
2	March 3, 2005	MathML contains invalid line end characters in Red Book (Patent Grants and Patent Applications) March 10, 2005 - MathML as generated by Mathematica includes character entities for line end/line feed that are converted inappropriately during the general conversion of named character entities to hexadecimal Unicode character entities. April 15, 2005 - This is still being investigated. April 22, 2005 - Data capture contractor is planning to resolve this issue internally and it will not be necessary to work with Wolfram Research. April 29, 2005 - The data capture contractor has identified a set of mathml characters impacted by the hexadecimal Unicode conversion requirement. They are characters such as: &NewLine; &IndentingNewLine; &RawReturn; Newline has a unique mapping problem since the mmlextra.ent entity file (for both Mathml1 and Mathml2) equates this to either or , both of which are resolved by the transformation scripts to a line break/line feed. ICE Red Book mathml processing requirements need clarified prior to resolving this item. If the requirement is for searching content, then these characters can be replaced with a descriptive form and eliminate the private use characters. If the requirement is to render using available COTS mathml tools, and these tools utilize the private use characters, then any altering of the entities is a potential problem. If the requirement is to be able to re-import the mathml model back into Mathematica, then again altering the entity content creates problems.
3	March 4, 2005	Some num attribute values include the word “header-“ as a prefix in Red Book (Patent Grants and Patent Applications) April 29, 2005 - This has been resolved. Please reference the Red Book ICE Status Report dated April 22, 2005.
4	March 8, 2005	Num attribute values not consistent between Patent Application Red Book and Patent Grant Red Book April 29, 2005 - This has been resolved. Please reference the Red Book ICE Status Report dated April 22, 2005.
5	March 14, 2005	Table “footnotes” no longer tagged as such in Red Book (Patent Grants and Patent Applications) April 29, 2005 - Please reference the Red Book ICE Status Report dated April 22, 2005
6	March 16, 2005	References to non-US patent documents missing “/” in some positions in Red Book (Patent Grants and Patent Applications) April 1, 2005 - Caused by a conversion step in creating Red Book (Patents Grants and Patent Applications) ICE, which has been in effect since at least October 2004. Red Book Viewer compensates by inserting “/” in the correct position. Data capture contractor investigating the reason for the deliberate removal of the slash. April 29, 2005 - This continues to be investigated.
7	March 18, 2005	The appearance of the International Patent Classification (IPC) in the Patent Grant Data/XML v4.0 (ICE) beginning February 8, 2005 and in the Patent Application Data/XML v4.0 (ICE) beginning February 10, 2005 changed April 29, 2005 - This has been resolved. Please reference the Red Book ICE Status Report dated April 15, 2005.
8	April 4, 2005	Legacy descriptive text markup(e.g., <city>Schw{hacek over (a)}bisch Gmünd</city> ) in Red Book (Patent Grants and Patent Applications) April 5, 2005 - There are a significant number of legacy descriptive text markup instances that can be converted to Unicode, but not without potentially large labor costs. USPTO is investigating the appropriate course of action. Reference FAQ 61. In fact, there are far more instances of descriptive text markup than was apparent at that time. April 15, 2005 - This is still open to a possible resolution. April 22, 2005 - This continues to be investigated. April 29, 2005 - The data capture contractor has proposed combined Unicode characters as a possible replacement for some of the single character descriptive text markup. The proposal is being reviewed by the USPTO.
9	April 5, 2005	Synchronizing num attribute values between Yellow Book (Patent Grants and Patent Applications) and Red Book (Patent Grants and Patent Applications) April 5, 2005 - It has been reported that the values of the num attribute are not always consecutive, and that they do not always match Yellow Book. This is a combined consequence of the conversion of markup from Red Book ST.32 to Red Book ST.36 (ICE) and the differences in markup practice between the two. April 5, 2005 - Starting the week of April 18, 2005, num attribute values will be consecutive, except where they are not to be displayed at rendering. Where the num attribute value is not to be displayed, the value is set to “0000”. See below for further details. April 5, 2005 - Effective the week of April 18, 2005, Grant Red Book ICE Issues will implement the following changes: ICE element us-patent-grant attribute status now contains the value of "PRODUCTION". The heading-paragraph markup now utilizes the id attribute instead of the num attribute, and is in the form of <p id="h-nnnn" num="0000">. If a paragraph or list item contains only unordered-list content or starts off with an unordered-list, the num attribute contains zeroes and is not to be displayed (num="0000"). All p & li num attributes are now padded to 4 characters. The abstract and heading-paragraph num attribute is always "0000". Attributes id and num in elements p, li, ul, and heading are now always lower case, and have been renumbered per the specifications defined below. Attributes id and num renumbering specifications within elements heading, p, ul, and li: attribute id specifications in p, heading, ul, and li: 1. headings and heading-paragraphs are numbered sequentially as encountered in the document using the form of id="h-nnnn" 2. remaining paragraphs are numbered sequentially as encountered in the document using the form of id="p-nnnn" 3. unordered lists are numbered sequentially as encountered in the document using the form of id="ulnnnn" 4. list items are numbered sequentially as encountered within its parent unordered list using the form of id="ulnnnn-nnnn". The 2nd nnnn starts with 0001 for each unordered list. attribute num specifications in p and li: 1. heading-paragraphs always have a value of num="0000". 2. abstract paragraph(s) always have a value of num="0000". 3. If a paragraph starts with an unordered list, it will have a value of num="0000". 4. If a list item starts with an unordered list, it will have a value of num="0000". 5. All remaining paragraphs and list items are numbered sequentially in the form of num="nnnn". Sample data and style sheet for Patent Application Red Book Sample data and style sheet for Patent Grant Red Book April 15, 2005 - We are still investigating to ensure that the num attribute in Yellow Book images matches the num attribute text in Red Book text. April 29, 2005 - This continues to be investigated. July 18, 2006 - Text revised.
10	April 19, 2005	There were no prior publication data for 20050000097 in Red Book ICE although there are 3 documents present in the Yellow Book 2 image file. April 22, 2005 - This will be corrected beginning with the application publication of May 5, 2005. April 29, 2005 - Resolution as cited above remains in place.
11	April 19, 2005	There is an inconsistency between Red Book ICE and Yellow Book 2 in indentification of References Cited by Examiner and References Cited by Others. April 29, 2005 - This continues to be investigated.

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.