Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 1 of 23
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 1 of 23
`
`EXHIBIT E
`EXHIBIT E
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 1 of 23
`
`EXHIBIT E
`EXHIBIT E
`
`
`
`+
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 2 of 23
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 2 of 23 jk
`
`PATENT
`Customer No. 22,852
`Attorney Docket No. 7643.0042
`
`IN THE UNITED STATES PATENT AND TRADEMARKOFFICE -
`BEFORE THE BOARDOF PATENT APPEALS AND INTERFERENCES
`
`In re Application of:
`
`Russell T. DAVISetal.
`
`Application No.: 10/052,250
`
`GroupArt Unit: 2176
`
`Filed: January 23, 2002
`
`Examiner: C. Nguyen
`
`Confirmation No.: 1920
`
`For.
`
`RDX ENHANCEMENT OF
`SYSTEM AND METHOD FOR
`IMPLEMENTING REUSABLE
`DATA MARKUP LANGUAGE
`(RDL)
`
`Attention: Mail Stop Appeal Brief - Patents
`Commissioner for Patents
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`Sir:
`
`Pursuant to 37 CFR § 41 41(a)(1), Appellants present this Reply Brief in
`
`REPLY BRIEF
`
`response to the Examiner's Answer mailed on November24, 2008.
`
`
`
`,
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 3 of 23
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 3 of 23
`
`Application No.: 10/052,250
`Attorney Docket No. 7643.0042
`
`I. Response to Examiner’s Arguments in the Answer
`
`In addition to the arguments for reversal of the outstandingfinal rejection
`
`provided in Appellants’ Appeal Brieffiled on August 28, 2008, Appellants provide the
`
`following remarks regarding the Examiner's Answer(“Answer”) mailed on November 24,
`
`2008.
`
`Regarding the rejection of claims 62-64 under 35 U.S.C. § 103(a), the Examiner
`
`continues to assert that the syntax elements in Krug correspondto the claimed
`
`“software elements” (Answerat pages 18-19). The Examinerstates, “the HTML
`
`documentis transformed into a syntax tree representing the hierarchical relationship of
`the syntax elements” (Answerat page 19). This is not correct.
`In Krug, a syntax tree parser 20 “analyses the HTML syntax structure of the
`
`search result document by recognizing the HTML tags within the document and
`
`constructing a hierarchical HTML syntax tree that represents the hierarchical
`
`relationship of the syntax elements (tags)” (col. 8, lines 23-27). Krug specifically
`
`teaches that the syntax elements are the “tags” within the document(col. 8, line 27). By
`
`alleging that the syntax elements in Krug could somehowconstitute the claimed
`
`“software elements,” the Examineris asserting that the tags in Krug correspond to both
`
`the claimed “tags” and the claimed “software elements.” Therefore, according to the
`
`Examiner's statements, Krug interprets tags included in the documentto create tags.
`
`This is not correct.
`
`Krug analyzes the HTML syntax structure by recognizing tags and constructs a
`
`syntax tree that represents the hierarchical relationship of the tags. Neither the tags,
`
`syntax elements, nor any other teaching in Krug constitutes the claimed “software
`
`
`
`‘
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 4 of 23
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 4 of 23
`
`Application No.: 10/052,250
`Attorney Docket No. 7643.0042
`
`elements”at least because Krug doesnotinterpret “tags included in the one or more
`
`text documents to create software elements,” as recited in independentclaim 62.
`
`Accordingly, Krug also cannot teach or suggest determining “the hierarchy of the
`
`software elementswithin a structure representative of the one or more text documents,”
`
`as further recited in claim 62.
`
`—
`
`The Examiner also continues to assert that Hamscherdiscloses the claimed
`
`“manager”that “provides for the creation of a second hierarchy of the software
`
`elements” and “provides for the restructuring of the first hierarchy and the second
`
`hierarchy into software structures corresponding to a new text document” (Answerat
`
`page 19). This is not correct.
`
`According to page 17 of Hamscher, an XBRL instance document can be created
`
`by concatenating other XBRL instance documents. The Examiner appearsto assert
`
`that an XBRL documentcreated by concatenating other XBRL instance documents
`
`constitutes the claimed “second hierarchy of software elements.” Even assuming that
`
`this newly created document could correspond to a “hierarchy of software elements,”
`
`which Applicants do not concede, only one “hierarchy of software elements” would be
`
`created(i.e. the created XBRL document).
`
`Both Krug and Hamscherdisclose, at most, information in a single hierarchy
`
`(allegedly the hierarchical relationship in Krug and the created XBRL documentin
`
`Hamscher).
`
`\n contrast, claim 62 recites both the determination of a “hierarchy of the
`
`software elements” created by interpreting tags included in the one or moretext
`
`documents” and “the creation of a second hierarchy of the software elements”
`
`(emphasis added). The cited references do not provide for both the determination of a
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 5 of 23
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 5 of 23
`
`Application No.: 10/052,250
`Attorney Docket No. 7643.0042
`
`“hierarchy of the software elements” and the creation of a “second hierarchy”of the
`
`same “software elements,” as recited by claim 62.
`
`Therefore, Hamscherdoes not teach or suggestthe claimed “creation of a
`secondhierarchy of the software elements.” Accordingly, Hamscherdoes not teach or
`
`suggest a managerthat “provides for the creation of a second hierarchy between the
`
`software elements, and provides for the restructuring of the first hierarchy and the
`
`second hierarchy into software structures corresponding to a new text document,” as
`
`recited in claim 62.
`
`As set forth above, and contrary to the assertions of the Examiner, the
`
`combination of Krug and Hamscherdoesnot teach or suggestall elements of claim 62.
`
`In view of this mischaracterization of the references, the Office Action has neither
`
`properly determined the scope and contentof the prior art nor properly ascertained the
`
`differences betweentheprior art and the claimed invention. Therefore, no reason has
`
`been clearly articulated as to why the claim would have been obvious to one of ordinary
`
`skill in view of the prior art and a prima facie case of obviousness has not been
`
`established.
`
`Claim 62is allowable for at least these reasons, and claims 63 and 64 are also
`
`allowable at least due to their depending from claim 62.
`
`Regarding the rejection of claims 1-6, 11-21, 24-34, 37-46, 49-57, and 59-61
`
`under 35 U.S.C. § 103(a), the Examiner again relies on Hamscherto allegedly disclose
`
`“a managerthat provides for the creation of a second hierarchical relationship between
`
`the software elements and the restructuring of the first hierarchical relationship and the
`
`
`
`‘
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 6 of 23
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 6 of 23
`
`Application No.: 10/052,250
`Attorney Docket No. 7643.0042
`
`secondhierarchical relationship into software structures corresponding to a new text
`
`document” (Answerat page 20). This is not correct.
`
`As established above, Hamscher doesnot teach the claimed “creation of a
`
`second hierarchy of the software elements.” Thus, Hamscher cannot teach or suggest
`a “manager that provides for the creation of a second hierarchy betweenthe software
`
`elements and the restructuring of the first hierarchy and the second hierarchyinto
`
`software structures corresponding to a new text document,” as recited in independent
`
`claim 1.
`
`Accordingly, and contrary to the assertions of the Examiner, the combination of
`
`Saxton, Polizzi, and Hamscher doesnot teach or suggestall elements of claim 1.
`
`In
`
`view of this mischaracterization of the references, the Office Action has neither properly
`
`determined the scope and contentof the prior art nor properly ascertained the
`
`differences betweenthe prior art and the claimed invention. Therefore, no reason has
`
`been clearly articulated as to why the claim would have been obviousto oneof ordinary
`
`skill in view of the prior art and a prima facie case of obviousness has not been
`
`established with respect to claim 1.
`
`Claim 1 is allowable for at least these reasons, and claims 2-6, and 11-16 are
`
`also allowable for at least the same reasons as claim 1. Independent claims 17, 29, 30,
`
`42, and 54, though of different scope than claim 1, recite limitations similar to those set
`
`forth above with respect to claim 1. Claims 17, 29, 30, 42, and 54 are therefore
`allowable for at least the reasons presented above. Claims 18-21, 24-29, 31-34, 37-41,
`
`43-46, 49-53, 55-57, and 59-61 are also allowable at least due to their dependence from
`
`claims 17, 29, 30, 42, and 54 respectively.
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 7 of 23
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 7 of 23
`
`Application No.: 10/052,250
`Attorney Docket No. 7643.0042
`
`Regarding the rejection of claims 8-10, 23, 36, 47, 48, and 58, which depend
`
`from claims 1, 17, 30, 42, and 54, Appellants continue to submit that C/lancey does not
`
`cure the deficiencies of Saxton, Polizzi, and Hamscherfor at least the reasons
`
`presented in Appellants’ Appeal Brief.
`
`ll. Conclusion
`
`For the reasons given above, and those reasons provided in Appellants’ Appeal
`
`Brief, Appellants respectfully submit that the rejections of the claims are in error and
`
`should be reversed.
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 8 of 23
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 8 of 23
`
`Application No.: 10/052,250
`Attorney Docket No. 7643.0042
`
`If there are any fees due under 37 C.F.R. §§ 1.16 or 1.17 which are not enclosed
`
`herewith, please charge suchfees to our Deposit Account No. 06-0916.
`
`Respectfully submitted,
`
`FINNEGAN, HENDERSON, FARABOW,
`GARRETT & DUNNER, L.L.P.
`
` Dated: January 22, 2009
`
`By:
`
`Jeffrey A. Berkowitz
`Reg. No. 36,743
`
`
`
`}
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 9 of 23
`
` 4-cv-00859-RTH Document 82-5, Filed 04/29/22 Page 9 of 23
`
`Customer No. 22,852
`Attorney Docket No.: 07643.0042-00
`Application No.: 10/052,250
`
`AMENDMENTSTO THE CLAIMS:
`
`This listing of claims will replace all prior versions andlistings of claims in the
`
`application:
`
`1.
`
`(Currently Amended) A data processing system for developing a report,
`
`comprising:
`
`a parser that receives one or more text documents and creates software
`
`elements having a formatwith a hierarchal relationship between the software elements
`
`based on the one or more text documents;
`
`a managerthat provides for the creation of a second hierarchical relationship
`
`between the software elements and the restructuring of the first hierarchical relationship
`
`and the second hierarchical relationship into software structures corresponding to a new
`
`text document;
`
`an editor that develops a report by referencing the software elements created
`
`from the one or more text documents to form a structure of the report and retrieves data
`
`from one or more sourcesto represent one or more values within the report([,]];and
`
`wherein-a mapperthatgenerates a relationship between the data from the one or
`
`more sources and the one or more valuesto be placed within the report.
`
`2.
`
`(Original) The data processing system of claim 1, wherein the format with the
`
`hierarchal relationship between the software elements is a Numerator Document Object
`
`Model (NDOM).
`
`-2-
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 10 of 23
`Case 1:19-cv-00859-RTH Document 82-5 ,Filed 04/29/22 Page 10 of 23
`
`Customer No. 22,852
`Attorney Docket No.: 07643.0042-00
`Application No.: 10/052,250
`
`3.
`
`(Original) The data processing system of claim 1, wherein the one or more text
`
`documents are XBRL documents.
`
`4.
`
`(Original) The data processing system of claim 1, wherein the parser creates the
`
`software elements having the format with the hierarchal relationship by interpreting tags
`
`included in the one or more text documents.
`
`5.
`
`(Original) The data processing system of claim 1, wherein a manager
`
`manipulates the software elements.
`
`6.
`
`(Original) The data processing system of claim 5, wherein the manager
`
`manipulates the software elements by browsing, editing, loading, and storing the
`
`software elements.
`
`7.
`
`(Canceled)
`
`8.
`
`(Original) The data processing system of claim 1, wherein one or more templates
`
`are used to develop the report.
`
`9.
`
`(Original) The data processing system of claim 8, wherein the one or more
`
`templates contain data that is directly inserted into the report and instructions enabling
`
`data from the one or more sourcesto be inserted into the report.
`
`-3-
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 11 of 23
`Case 1:19-cv-00859-RTH Document82-5 , Filed 04/29/22 Page 11 of 23
`
`Customer No. 22,852
`Attorney Docket No.: 07643.0042-00
`Application No.: 10/052,250
`
`10.
`
`(Previously Presented) The data processing system of claim 9, wherein the one
`
`or more templates provide instructions to the mapperto retrieve the datathatis directly
`
`inserted into the report and data from local or remote sources.
`
`11.
`
`(Previously Presented) The data processing system of claim 1, wherein the
`
`mapperlinks the report and the one or more sourcesthatwill present one or more
`
`values within the report.
`
`12.
`
`(Original) The data processing system of claim 11, wherein the report and the
`
`one or more sourcesare linked through a “drag and drop” process.
`
`13.
`
`(Original) The data processing system of claim 1, wherein the editor provides for
`
`the software elements to be modified to create a new combination of software elements
`
`representative of a new text document.
`
`14.
`
`(Original) The data processing system of claim 1, wherein the editor provides for
`
`modification of one or more parameters associated with the software elements.
`
`15.
`
`(Original) The data processing system of claim 1, wherein the software elements
`
`are transformed to new software elements and are imported into an RDL system.
`
`-4-
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 12 of 23
`Case 1:19-cv-00859-RTH Document 82-5. ,Filed 04/29/22 Page 12 of 23
`
`Customer No. 22,852
`Attorney Docket No.: 07643.0042-00
`Application No.: 10/052,250
`(Original) The data processing system of claim 15, whereinthe software
`
`16.
`
`elements are transformed to the new software elements by retrieving a tag associated
`
`with each of the software elementsin a dictionary and invoking a translation routine
`
`associated with the tag.
`
`17.|(Currently Amended) A method in a data processing system for developing a
`
`report, comprising:
`
`receiving one or more text documents;
`
`creating software elements having a format with a hierarchalrelationship
`
`between the software elements based on the one or more text documents;
`
`creating a second hierarchical relationship between the software elements;
`
`restructuring the first hierarchical relationship and second hierarchical
`
`relationship into software structures corresponding to a new text document;
`
`developing a report by referencing the software elements created from the one or
`
`more text documents to form a structure of the report and retrieving data from one or
`
`more sources to represent one or more values within the report; and
`
`generating a relationship between the data from one or more sources and the
`
`one or more valuesto be placed within the report.
`
`18.
`
`(Original) The method of claim 17, wherein creating the software elements from
`
`the one or more text documentsincludes representing the software elements in a
`
`Numerator Document Object Model (NDOM).
`
`-5-
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 13 of 23
`Case 1:19-cv-00859-RTH Document 82-5 ,Filed 04/29/22 Page 13 of 23
`
`Customer No. 22,852
`Attorney Docket No.: 07643.0042-00
`Application No.: 10/052,250
`
`19.
`
`(Original) The method of claim 17, wherein creating the software elements
`
`includes creating software elements from one or more XBRL documents.
`
`20.
`
`(Original) The methodof claim 17, wherein creating the software elements
`
`having the format with the hierarchal relationship includes interpreting tags included in
`
`the one or more text documents.
`
`21.
`
`(Original) The method of claim 17, further comprising manipulating the software
`
`elements by browsing, editing, loading, and storing the software elements.
`
`22.
`
`(Canceled)
`
`23.
`
`(Original) The method of claim 17, further comprising developing the report from
`
`one or more templates, which contain data that is directly inserted into the report and
`
`instructions enabling data from the one or more sourcesto be inserted into the report.
`
`24.
`
`(Original) The method of claim 22, wherein the relationship is generated through
`
`a “drag and drop” process.
`
`25.
`
`(Original) The methodof claim 17, further comprising modifying the software
`
`elements to create a new combination of software elements representative of a new text
`
`document.
`
`-6-
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 14 of 23
`Case 1:19-cv-00859-RTH . Document 82-5 Filed 04/29/22 Page 14 of 23
`Customer No. 22,852
`Attorney Docket No.: 07643.0042-00
`Application No.: 10/052,250
`
`26.
`
`(Original) The methodof claim 17, further comprising modifying the software
`
`elements by editing one or more parameters associated with the software elements.
`
`27.
`
`(Original) The methodof claim 17, further comprising transforming the software
`
`elements to new software elements for importing into an RDL system.
`
`28.
`
`(Original) The method of claim 27, wherein transforming the new software
`
`elements includes retrieving a tag associated with each of the software elements in a
`
`dictionary and invoking a translation routine associated with the tag.
`
`29.
`
`(Currently Amended) A data processing system for developing a report,
`
`comprising:
`
`meansfor receiving one or more text documents;
`
`meansfor creating software elements having a format with a hierarchal
`
`relationship between the software elements based on the one or more text documents;
`
`meansfor creating a second hierarchical relationship between the software
`
`elements;
`
`meansforrestructuring the first hierarchical relationship and the second
`
`hierarchical relationship into software structures corresponding to a new text document;
`
`meansfor developing a report by referencing the software elements created from
`
`the one or more text documentsto form a structure of the report and retrieving data
`
`from one or more sourcesto represent one or more values within the report; and
`
`-7-
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 15 of 23
`Case 1:19-cv-00859-RTH Document 82-5 ,Filed 04/29/22 Page 15 of 23
`
`Customer No. 22,852
`Attorney Docket No.: 07643.0042-00
`Application No.: 10/052,250
`
`meansfor generating a relationship between the data from the one or more
`
`sources and the one or more valuesto be placed within the report.
`
`30.
`
`(Currently Amended) A computer-readable medium including instructions for
`
`controlling a processor to perform a method for developing a report, the method
`
`comprising the stepsof:
`
`receiving one or more text documents;
`
`creating software elements having a format with a hierarchal relationship
`
`betweenthe software elements based on the one or more text documents;
`
`creating a second hierarchical relationship between the software elements;
`
`restructuring the first hierarchical relationship and the second hierarchical
`
`relationship into software structures corresponding to a new text document:
`
`developing a report by referencing the software elements created from the one or
`
`more text documents to form a structure of the report and retrieving data from one or
`
`more sourcesto represent one or more values within the report; and
`
`generating a relationship between the data from the one or more sources and the
`
`one or more values to be placed within the report.
`
`31.
`
`(Original) The computer-readable medium of claim 30, wherein creating the
`
`software elements from the one or more text documents includes representing the
`
`software elements in a Numerator Document Object Model (NDOM).
`
`-8-
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 16 of 23
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 16 of 23
`Customer No. 22,852
`Attorney Docket No.: 07643.0042-00
`Application No.: 10/052,250
`
`32.
`
`(Original) The computer-readable medium of claim 30, wherein creating the
`
`software elements includes creating software elements from one or more XBRL
`
`documents.
`
`33.
`
`(Original) The computer-readable medium of claim 30, wherein creating the
`
`software elements having the format with the hierarchal relationship includes
`
`interpreting tags included in the one or more text documents.
`
`34.
`
`(Original) The computer-readable medium of claim 30, further comprising
`
`manipulating the software elements by browsing, editing, loading, and storing the
`
`software elements.
`
`35.
`
`(Canceled)
`
`. 36.
`
`(Original) The computer-readable medium of claim 30, further comprising
`
`developing the report from one or more templates, which contain data thatis directly
`
`inserted into the report and instructions enabling data from the one or more sourcesto
`
`be inserted into the report.
`
`37.
`
`(Original) The computer-readable medium of claim 35, wherein the relationshipis
`
`generated through a “drag and drop” process.
`
`-9-
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 17 of 23
`Case 1:19-cv-00859-RTH Document 82-5 ,Filed 04/29/22 Page 17 of 23
`Customer No. 22,852
`Attorney Docket No.: 07643.0042-00
`Application No.: 10/052,250
`
`38.
`
`(Original) The computer-readable medium of claim 30, further comprising
`
`modifying the software elements to create a new combination of software elements
`
`representative of a new text document.
`
`39.
`
`(Original) The computer-readable medium of claim 30, further comprising
`
`modifying the software elements by editing one or more parameters associated with the
`
`software elements.
`
`40.
`
`(Original) The computer-readable medium of claim 30, further comprising
`
`transforming the software elements to new software elements for importing into an RDL
`
`system.
`
`41.
`
`(Original) The computer-readable medium of claim 40, wherein transforming the
`
`new software elements includesretrieving a tag associated with each of the software
`
`elements in a dictionary and invoking a translation routine associated with the tag.
`
`42.
`
`(Currently Amended) A data processing system for developing a report,
`
`comprising:
`
`a parserthat receives one or more text documents and creates software
`
`elements having a format with a hierarchal relationship between the software elements
`
`based on the one or more text documents;
`
`a managerthat manipulates the software elements, provides for the creation of a
`
`second hierarchical relationship between the software elements, and providesfor the
`
`-10-
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 18 of 23
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 18 of 23
`
`Customer No. 22,852
`Attorney Docket No.: 07643.0042-00
`Application No.: 10/052,250
`
`restructuring of the first hierarchical relationship and the second hierarchical relationship
`
`into software structures corresponding to a new text document;
`
`an editor that develops a report by referencing the software elements created
`
`from the one or more text documents to form a structure of the report; and
`
`a mapperthat retrieves data from one or more sources to represent one or more
`
`values within the report and generates a relationship betweenthe retrieved data and the
`
`one or more valueswithin the report.
`
`43.
`
`(Original) The data processing system of claim 42, wherein the format with the
`
`hierarchal relationship between the software elements is a Numerator Document Object
`
`Model (NDOM).
`
`44.
`
`(Original) The data processing system of claim 42, wherein one or moretext
`
`documents are XBRL documents.
`
`45.
`
`(Original) The data processing system of claim 42, wherein the parser creates
`
`the software elements with the format with the hierarchal relationship by interpreting
`
`tags included in the one or more text documents.
`
`46.
`
`(Original) The data processing system of claim 42, wherein the manager
`
`manipulates the software elements by browsing, editing, loading, and storing the
`
`software elements.
`
`-11-
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 19 of 23
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 19 of 23
`
`Customer No. 22,852
`Attorney Docket No.: 07643.0042-00
`Application No.: 10/052,250
`
`47.
`
`(Original) The data processing system of claim 42, wherein the report is
`
`developed from one or more templates, which contain data that is directly inserted into
`
`the report andinstructions enabling data from the one or more sourcesto be inserted
`
`into the report.
`
`48.
`
`(Original) The data processing system of claim 47, wherein the one or more
`
`templates providesinstructions to the mapperto retrieve the data thatis directly
`
`inserted into the report and data from local or remote sources.
`
`49.
`
`(Original) The data processing system of claim 42, wherein the report and the
`
`one or more sourcesare linked through a “drag and drop” process.
`
`50.
`
`(Previously Presented) The data processing system of claim 42, wherein the
`
`editor provides for the software elements to be modified to create a new combination of
`
`software elements representative of a new text document.
`
`51.
`
`(Previously Presented) The data processing system of claim 42, wherein the
`
`editor provides for modification of one or more parameters associated with the software
`
`elements.
`
`52.
`
`(Original) The data processing system of claim 42, wherein the software
`
`elements are transformed to new software elements and are imported into an RDL
`
`system.
`
`-12-
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 20 of 23
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 20 of 23
`
`Customer No. 22,852
`Attorney Docket No.: 07643.0042-00
`Application No.: 10/052,250
`
`53.
`
`(Original) The data processing system of claim 52, wherein the software
`
`elements are transformed to the new software elements byretrieving a tag associated
`
`with each of the software elements in a dictionary and invoking a translation routine
`
`associated with the tag.
`
`54.
`
`(Currently Amended) A method for data processing, comprising:
`
`receiving one or more text documents;
`
`creating software elements having a format with a hierarchal relationship
`
`between the software elements based on the one or more text documents;
`
`~ manipulating the software elements,
`
`creating a secondhierarchical relationship between the software elements;
`
`restructuring thefirst hierarchical relationship and the second hierarchical
`
`relationship into software structures corresponding to a new text document;
`
`developing a report by referencing the software elements created from the one or
`
`more text documents to form a structure of the report;
`
`generating a relationship between data from one or more sources and one or
`
`more values to be placed within the report; and
`
`retrieving data from the one or more sources to represent the one or more values
`
`within the report.
`
`-13-
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 21 of 23
`Case 1:19-cv-00859-RTH | Document 82-5 Filed 04/29/22 Page 21 of 23
`
`Customer No. 22,852
`Attorney Docket No.: 07643.0042-00
`Application No.: 10/052,250
`
`55.
`
`(Original) The methodof claim 54, wherein creating the software elements from
`
`the one or more text documents includes representing the software elementsin a
`
`Numerator Document Object Model (NDOM).
`
`56.
`
`(Original) The methodof claim 54, wherein creating the software elements from
`
`the one or more text documents includes creating software elements from one or more
`
`XBRL documents.
`
`57.
`
`(Original) The method of claim 54, wherein creating the software elements
`
`having the format with the hierarchal relationship includes interpreting tags included in
`
`the text documents.
`
`58.
`
`(Previously Presented) The methodofclaim 54, further comprising developing
`
`the report from one or more templates, which contain data thatis directly inserted into
`
`the report and instructions enabling data from the one or more sourcesto be inserted
`
`into the report.
`
`59.
`
`(Previously Presented) The methodofclaim 54, further comprising modifying the
`
`software elements to create a new combination of software elements representative of a
`
`new text document.
`
`-14-
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 22 of 23
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 22 of 23
`Customer No. 22,852
`Attorney Docket No.: 07643.0042-00
`Application No.: 10/052,250
`
`60.
`
`(Previously Presented) The methodofclaim 54, further comprising modifying the
`
`software elements by editing one or more parameters associated with the software
`
`elements.
`
`61.
`
`(Original) The methodofclaim 54, further comprising transforming the software
`
`elements to new software elements for importing into an RDL system.
`
`62.
`
`(Currently Amended) A data processing system, comprising:
`
`a parser that:
`
`receives one or more text documents,
`
`interprets tags included in the one or more text documents to create
`
`software elements, and
`
`determinesthe hierarchy of the software elements within a structure
`
`representative of the one or more text documents|[.]],and
`
`a managerthat:
`
`provides for the creation of a second hierarchy of the software elements,
`
`» = Qa
`
`provides for the restructuring of the first hierarchy and the second
`
`hierarchy into software structures corresponding to a new text document.
`
`63.
`
`(Original) The data processing system ofclaim 62, wherein the structure is a
`
`Numerator Document Object Model (NDOM).
`
`-15-
`
`
`
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 23 of 23
`Case 1:19-cv-00859-RTH Document 82-5 Filed 04/29/22 Page 23 of 23
`
`Customer No. 22,852
`Attorney Docket No.: 07643.0042-00
`Application No.: 10/052,250
`
`64.
`
`(Original) The data processing system of claim 62, wherein the one or moretext
`
`documents are XBRL documents.
`
`-16-
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
