Ex Parte Balabhadrapatruni et alDownload PDFPatent Trials and Appeals BoardJan 22, 201914923803 - (D) (P.T.A.B. Jan. 22, 2019) Copy Citation UNITED STA TES p A TENT AND TRADEMARK OFFICE APPLICATION NO. FILING DATE 14/923,803 10/27/2015 37945 7590 01/24/2019 DUKEW. YEE YEE AND AS SOCIA TES, P.C. P.O. BOX 802333 DALLAS, TX 75380 FIRST NAMED INVENTOR Venkatuday M. Balabhadrapatruni UNITED STATES DEPARTMENT OF COMMERCE United States Patent and Trademark Office Address: COMMISSIONER FOR PATENTS P.O. Box 1450 Alexandria, Virginia 22313-1450 www .uspto.gov ATTORNEY DOCKET NO. CONFIRMATION NO. CAM920140036US2 3062 EXAMINER LYONS, ANDREW M ART UNIT PAPER NUMBER 2191 NOTIFICATION DATE DELIVERY MODE 01/24/2019 ELECTRONIC Please find below and/or attached an Office communication concerning this application or proceeding. The time period for reply, if any, is set in the attached communication. Notice of the Office communication was sent electronically on above-indicated "Notification Date" to the following e-mail address(es): ptonotifs@yeeiplaw.com mgamez@yeeiplaw.com PTOL-90A (Rev. 04/07) UNITED STATES PATENT AND TRADEMARK OFFICE BEFORE THE PATENT TRIAL AND APPEAL BOARD Ex parte VENKATUDAY M. BALABHADRAPATRUNI, MELVINE. FOWLER II, MICHAELS. FULTON, GARYI. MAZO, and BRIAN W. SVIHOVEC Appeal2018-002742 Application 14/923,803 Technology Center 2100 Before JOHN A. JEFFERY, DENISE M. POTHIER, and JUSTIN BUSCH, Administrative Patent Judges. JEFFERY, Administrative Patent Judge. DECISION ON APPEAL Pursuant to 35 U.S.C. § 134(a), Appellants 1 appeal from the Examiner's decision to reject claims 1-20, which constitute all the claims pending in this application. We have jurisdiction under 35 U.S.C. § 6(b ). We affirm. 1 Appellants identify the real party in interest as International Business Machines Corporation. App. Br. 2. Appeal2018-002742 Application 14/923,803 STATEMENT OF THE CASE Appellants' invention tracks control for computing tasks by (1) receiving a reference to a control file specifying a computing task; (2) receiving an identifier for a performance of the specified computing task in accordance with a control file; (3) storing information associating the identifier and the reference; and (4) returning the reference in response to receiving a request for information associated with the identifier. See generally Abstract; Spec. ,r 4. Claim 1 is illustrative: 1. A computer-implemented method of tracking control for computing tasks comprising: receiving a reference to a control file specifying a computing task; submitting the specified task for performance on a computing system in accordance with the control file and receiving an identifier for the performance of the task; receiving a request from a user to link the identifier with the control file; in response to the request, storing information associating the identifier and the reference; receiving a request for information, the request including the identifier and in response returning the associated reference. THE REJECTIONS The Examiner rejected claims 1, 2, 5-8, 17, and 18 under 35 U.S.C. § 103 as being unpatentable over Nalis et al. (US 9,111,037 Bl; Aug. 18, 2015) and Headley et al. (US 7,386,586 Bl; June 10, 2008). Final Act. 3- 8.2 2 Throughout this opinion, we refer to (1) the Final Rejection mailed Aug. 11, 2017 ("Final Act."); (2) the Appeal Brief filed Nov. 8, 2017 ("App. Br."); (3) the Examiner's Answer mailed Dec. 29, 2017 ("Ans."); and (4) the Reply Brief filed Jan. 11, 2018. 2 Appeal2018-002742 Application 14/923,803 The Examiner rejected claim 9, 19, and 20 under 35 U.S.C. § 103 as being unpatentable over Nalis, Headley, and Sirota et al. (US 2014/0330981 Al; Nov. 6, 2014). Final Act. 9-14. The Examiner rejected claims 3 and 4 under 35 U.S.C. § 103 as being unpatentable over Nalis, Headley, and Archie et al. (US 5,021,997; June 4, 1991). Final Act. 14--16. The Examiner rejected claims 10-14 under 35 U.S.C. § 103 as being unpatentable over Nalis, Headley, Sirota, and Archie. Final Act. 16-19. The Examiner rejected claim 15 under 35 U.S.C. § 103 as being unpatentable over Nalis, Headley, Sirota, Archie, and Patil (US 2003/0051188 Al; Mar. 13, 2003). Final Act. 19-20. The Examiner rejected claim 16 under 35 U.S.C. § 103 as being unpatentable over Nalis, Headley, Sirota, Archie, and Campion et al. (US 2009/0007074 Al; Jan. 1, 2009). Final Act. 20-21. RELATED APPEAL Appellants identify a related appeal for Application No. 14/665,379 (Appeal No. 2018-002579). App. Br. 3. THE OBVIOUSNESS REJECTION OVER NALIS AND HEADLEY The Examiner finds that Nalis discloses many recited elements of independent claim 1 including, among other things, receiving a reference to a control file specifying a computing task. Final Act. 3; Ans. 21-22. The Examiner also finds that Nalis receives an identifier for the performance of the computing task. Final Act. 3. Although the Examiner acknowledges that Nalis does not receive a request from a user to link the identifier with 3 Appeal2018-002742 Application 14/923,803 the control file and store information associating the identifier and the reference responsive to the request, the Examiner nonetheless cites Headley for teaching this feature in concluding that the claim would have been obvious. Id. at 4--5. Appellants argue that the Examiner's reliance on Nalis is misplaced because, among other things, Nalis' Job Control Language (JCL) test is not a "control file" as claimed. App. Br. 9. According to Appellants, Nalis' JCL test is a computing task that is to be performed in accordance with a control file. App. Br. 9; Reply Br. 3. Appellants further argue the Examiner cannot change the mapping of the claimed "reference" from being Nalis' location of a JCL test to Nalis' "Job Name." App. Br. 10. According to Appellants, Headley's submission of a job by a user is not equivalent to (1) requesting that an identifier be linked to a control file, and storing information associating the identifier and the reference responsive to the request. Id. at 11-12. ISSUES I. Under§ 103, has the Examiner erred by finding that Nalis and Headley collectively would have taught or suggested: (1) receiving a reference to a control file specifying a computing task as recited in claim 1? (2) receiving a request from a user to link an identifier with the control file and storing information associating the identifier and the reference in response to the request as recited in claim 1? (3) the reference including a storage location of the control file as recited in claim 1 7? 4 Appeal2018-002742 Application 14/923,803 ( 4) the returned associated reference including the storage location of the control file as recited in claim 18? II. Is the Examiner's proposed combination supported by articulated reasoning with some rational underpinning to justify the Examiner's obviousness conclusion? ANALYSIS Claims 1, 2, and 5---8 Claim 1 recites, in pertinent part, "receiving a reference to a control file specifying a computing task." As noted previously, Appellants dispute the Examiner's reliance on Nalis' JCL test for teaching the recited "control file specifying a computing task." According to Appellants, Nalis' JCL test is not a control file, but rather the computing task that the control file specifies. App. Br. 9; Reply Br. 3. We, therefore, begin by construing the term "control file." Notably, Appellants' Specification does not define the term "control file." As shown in Appellants' Figure 1, "control files 116 (e.g., JCL files)" specify requests to run jobs. Spec. ,r 13 (emphasis added). Paragraph 11 of Appellants' Specification further explains "controls ... (e.g., batch scripts, programs, processes, etc.) [are used to perform the computing tasks.]") (emphasis added). Despite Appellants' arguments to the contrary (App. Br. 9; Reply Br. 3), our emphasis underscores that these forms of control files disclosed in Appellants' Specification are merely exemplary. Accord App. Br. 9 (recognizing the term "control file" as described in paragraph 10 of Appellants' Specification may be a script, program, process, etc.). 5 Appeal2018-002742 Application 14/923,803 The plain meaning of the term "file" is "a basic unit of storage that enables a computer to distinguish one set of information from another. A file is the 'glue' that binds a conglomeration of instructions ... into a coherent unit that a user can retrieve." MICROSOFT COMPUTER DICTIONARY 211 (5th ed. 2002). Nalis' primary database includes a test repository that stores a JCL test. Nalis col. 5, 11. 5-9; col. 6, 11. 15-20. Nalis' mainframe computing system obtains the JCL test from the test repository. Id. col. 6, 11. 20-22. This functionality, then, at least suggests Nalis' JCL test is a control file. Moreover, Nalis' obtained JCL test is executed by the mainframe computing system. See id. col. 6, 11. 18-24. This functionality, then, at least suggests Nalis' JCL test further specifies a computing task. Claim 1 further recites two separate instances of the term "reference"-(A) receive a reference to a control file specifying a computing task and (B) return the associated reference in response to a request for information. Appellants contend the Examiner erred in finding step (A)'s reference as being Nalis' location of a JCL test and step (B)'s reference as being Nalis' "Job Name." App. Br. 10; Reply Br. 4. We, therefore, construe the term "reference." Notably, Appellants' Specification does not define the term "reference." Paragraph 18 of Appellants' Specification explains "a reference (e.g., a URL, filename, etc.) to the control file 116 ... specifies the instructions to be performed for the job." ( emphasis added). Appellants' Figure 4 illustrates "[an] example reference 420 to a job's control file." Spec. ,r 26 ( emphasis added). Our emphasis underscores that, although these descriptions inform our construction of the term "reference," they do not limit our interpretation. 6 Appeal2018-002742 Application 14/923,803 Thus, under its broadest reasonable interpretation consistent with Appellants' Specification, we interpret the term "reference" according to its plain meaning, namely something that refers. See MERRIAM-WEBSTER'S COLLEGIATE DICTIONARY 982 (n. def. 3) (10th ed. 1993) (defining a "reference" as "something that refers."). With this construction, we see no error in the Examiner's finding that Nalis' JCL "test name and/or location are the reference to the control file." Final Act. 3 ( emphasis added); see also id. at 9; Ans. 3, 9. We emphasize "and/or" here because, contrary to Appellants' argument (App. Br. 10; Reply Br. 4), the Examiner maps Nalis' test name or location----or both-to the claimed reference. Nalis' testing client selects a JCL test to run on a mainframe computing system, and sends a request for a location of the selected JCL test to a primary database. Nalis col. 5, 1. 65---col. 6, 1. 4. In response, a record for a test result is created in the primary database including a test name and JCL location for the selected JCL test. Id. col. 6, 11. 7-9. This functionality, then, at least suggests Nalis' test name or JCL location as being something that refers to the selected JCL test. Nor do we find availing Appellants' argument that the claimed reference can be either Nalis' test name or location of the selected JCL test, but not both. App. Br. 1 O; Reply Br. 4. We find it is reasonable for the Examiner to combine Nalis' test name and location of the selected JCL test to satisfy the claimed reference. In other words, the Examiner's interpretation of the two prior art elements, i.e., Nalis' test name and JCL location as being something that refers to the selected JCL test. Nor do Appellants persuasively rebut the Examiner's reliance on Headley for at least suggesting receiving a request from a user to link an 7 Appeal2018-002742 Application 14/923,803 identifier with a control file and, in response to the request, storing information associating the identifier and a reference, as recited in claim 1. See App. Br. 11-12; Reply Br. 4. As the Examiner indicates, in response to Headley's user creating a job, an Explorer view displays (1) all jobs, (2) the runs for each job, (3) the location for eachjob in a job directory, and (4) the ID for eachjob. Final Act. 4--5 (citing Headley col. 5, 11. 24--27, 44---67; col. 7, 11. 36-48; col. 8, 1. 49-col. 10, 1. 15; col. 15, 11. 32--48; col. 24, 11. 18--40). Headley's system allows a user to schedule a new job. Headley col. 5, 11. 41--43; col. 9, 11. 46-50. In response, Headley's new job is saved in a central repository and local repository. Id. col. 7, 11. 40--46. This functionality, then, at least suggests that Headley's new job is a control file. Headley discloses generating a unique job ID for the new job. Id. col. 13, 11. 50-56. This functionality, then, at least suggests receiving a request for a new job (the claimed "request") from a user to link the new job's unique job ID (the claimed "identifier") with the new job (the claimed "control file"). Headley's user views jobs and the runs for each job in an Explorer view. Id. col. 24, 11. 20-21. Headley's Figure 32 illustrates a hierarchy of folders that sort jobs and their runs. Id. col. 24, 11. 25-36; Fig. 32. Headley's Figure 36 shows in one embodiment a column format when using an Explorer view and is reproduced below. 8 Appeal2018-002742 Application 14/923,803 Director Exolorer View - ProVision Jobs file 1;clit Yiew Iools Window tlelp ID 1~19l II\? IIEl 8-'fm i>r~Vhbn Jobs ... JOB ID I DESCRI PT!ON = B46 i=o AllJD~s 864 DAO CompaEisoo -LI Jobs By Group 875 DAO Output - Callection · ORA73CAO DEJECT 03-~;.R-98 [;!-·CJ Jobs By rJode 882 fleurg Oracl~ Table - [ "CONS_DD] I EJ--QI dicnUilla 1\83 Rec19 Oracl~ l"aole • [ FCOfiS_DO i : : ~-OIAII Jobs Any Sta111.s ,... !ll!E Rearg Oracle Table - [ FCONS_DO I : , • -r:J All Ru ~s Hy Status ~ 890 fleorg Drncle Table - I FCOP.:S_DD I ' : fil-CJ: '1eld Joos 952 Qualrell Reorg : : _,-CJ Scheduled Jo~s 957 JEST ! If'· dimultrawlv ::;; ~~ ~~l$11 Reorg ti I I• 0 I Ready FIG. 36 Q~[g] I PRODUCT I J0:3 GROUP 1..- 820 TSTI/U 1 DAO 2.0.0 1 DAO 2.0.0 ,- 0 TSR2.2 G :SR2.2 0 TSR 2.2 0 TSR 2.2 2 TSfi ~ 831 TST\'1 0.0 2 TSR ~ ~-~ :• ,--. " ... r • Headley's column format in Figure 36. Headley's Figure 36 illustrates a left panel including the hierarchy of folders illustrated in Figure 32. Id. col. 25, 11. 43---63; col. 26, 11. 15-50. Headley's Figure 36 further illustrates that when a user selects text of the "All Jobs Any Status" folder in the hierarchy of folders, a right panel displays columns including a unique job ID number and description of each job in the "All Jobs Any Status" folder. Id. col. 26, 11. 44--50. This functionality, then, at least suggests that responsive to receiving a request for a new job (the claimed "request"), information associating the unique job ID of the new job (the claimed "identifier") and a description of the new job ( the claimed "reference") is stored. Lastly, we find no error in the Examiner's articulated reason to combine the references, namely modifying N alis' tracking system by ( 1) organizing data regarding each job and/or run, and (2) enabling user access to such information using an Explorer view. Final Act. 5. These proposed enhancements to Nalis use prior art elements predictably according to their established functions to yield a predictable result. See KSR Int 'l Co. v. 9 Appeal2018-002742 Application 14/923,803 Teleflex Inc., 550 U.S. 398, 417 (2007). Despite Appellants' arguments to the contrary (App. Br. 12-13), the Examiner's proposed combination is not based solely on impermissible hindsight, but rather supported by articulated reasoning with some rational underpinning to justify the Examiner's obviousness conclusion. Therefore, we are not persuaded that the Examiner erred in rejecting claim 1, and claims 2 and 5-8 not argued separately with particularity. Claim 17 We sustain the Examiner's obviousness rejection of claim 17 (Final Act. 7; Ans. 27-28), which recites, in part, the reference includes a storage location of the control file. According to the Examiner, Nalis' location of a JCL test is retrieved upon selecting the JCL test for execution. Ans. 28 (citing Nalis Fig. 6). We, therefore, presume the Examiner finds Nalis' location of a JCL test as including the selected JCL test. We see no error in the Examiner's finding in this regard given the scope and breadth of the term "including" which is not defined in the Specification and, therefore, is construed with its plain meaning. The term "include" is defined as "[t]o take in as a part." THE AMERICAN HERITAGE DICTIONARY OF THE ENGLISH LANGUAGE 913 (v. def. 1) (3rd ed. 1992). Given this broad definition, the location of a JCL test nonetheless takes in as a part the JCL test when the location of the JCL test is retrieved in response to selecting the JCL test. The Examiner further finds Headley' s node at which a specifically identified job is stored teaches a storage location. Ans. 27 ( citing Headley Figs. 34, 37); see also Final Act. 4--5. We see no error in the Examiner's 10 Appeal2018-002742 Application 14/923,803 reliance on Headley merely for this limited purpose. Accordingly, contrary to Appellants' arguments (App. Br. 13-14), the Examiner's rejection is not based on Headley alone, but rather the collective teachings ofNalis and Headley-the former's teachings regarding the location of a JCL test as including the JCL test. In short, Appellants do not persuasively rebut the Examiner's finding that modifying Nalis' selected JCL test (the claimed "control file") to include a storage location, such as that in Headley, would have been at least an obvious variation. Therefore, Appellants' arguments regarding Headley's individual shortcomings in this regard do not show nonobviousness where, as here, the rejection is based on the cited references' collective teachings. See In re Merck & Co., Inc., 800 F.2d 1091, 1097 (Fed. Cir. 1986). Therefore, we are not persuaded that the Examiner erred in rejecting claim 17. Claim 18 We sustain the Examiner's obviousness rejection of claim 18 (Final Act. 7-8; Ans. 28-29), which depends from claim 17 and adds that the returned associated reference includes the storage location of the control file. Contrary to Appellants' arguments (App. Br. 14--15), the Examiner's "rejection of claim 18 is not based on the disclosure of Headley alone, but instead ... the combination ofNalis and Headley" (Ans. 28}-the former's teachings regarding "the use of a control file" (id.). In short, Appellants do not persuasively rebut the Examiner's finding that modifying Nalis' selected JCL test (the claimed "control file") to include a storage location, such as that in Headley, would have been at least an obvious variation. Therefore, 11 Appeal2018-002742 Application 14/923,803 Appellants' arguments regarding Headley's individual shortcomings in this regard do not show nonobviousness where, as here, the rejection is based on the cited references' collective teachings. See Merck, 800 F.2d at 1097. Therefore, we are not persuaded that the Examiner erred in rejecting claim 18. THE OBVIOUSNESS REJECTION OVER NALIS, HEADLEY, AND SIROTA We also sustain the Examiner's obviousness rejection of claims 9, 19, and 20. Final Act. 9--14. Although Appellants nominally argue these claims separately, Appellants reiterate arguments similar to those made in connection with claim 1. See App. Br. 15. We are not persuaded of error in this rejection for the reasons previously discussed. THE OBVIOUSNESS REJECTION OVER NALIS, HEADLEY, AND ARCHIE Claim 3 We sustain the Examiner's obviousness rejection of claim 3 (Final Act. 14--15; Ans. 30) reciting, in pertinent part, determining that the control file has been modified since submitting the specified task. In the rejection, the Examiner finds Archie's test is downloaded to a target processor that runs the test. Ans. 30. Notably, the Examiner finds Archie's "MODIFIED field" includes information regarding "whether the test has been modified since it was submitted for execution (i.e., on the target processor)." Id. (citing Archie col. 10, 11. 13--48). The Examiner 12 Appeal2018-002742 Application 14/923,803 proposes to combine this teaching with Nalis and Headley's method. Final Act. 14--15. Archie's test is stored in a test storage hierarchy. Archie col. 5, 11. 50- 51; Fig. 1. Archie's BDLOAD process then places the test in an output file for downloading to a target processor. Id. col. 5, 11. 62---65; Fig. 1. Archie's BRUN process then executes the downloaded test on the target processor. Id. col. 5, 11. 65---67. Archie's BS TORE process then stores the test results in a results database in a RUNINFO record. Id. col. 6, 11. 1--4; col. 9, 11. 18-20; Fig. 5. Archie's RUNINFO record includes a component TYPE field that assigns a "MODIFIED" identifier to the component TYPE field if the test was modified since being downloaded. Id. col. 9, 11. 32-36. Thus, Archie's assignment of the "MODIFIED" identifier, then, at least suggests a determination that the test has been modified since being downloaded. Appellants' contention that Archie's determination ( that its test was modified) occurs before the test's execution (App. Br. 17 (citing Archie col. 15, 1. 65---col. 17, 1. 2)) is unavailing, because it does not address the Examiner's findings. That is, claim 3 recites determining "that the control file has been modified since the submitting of the specified task," which the Examiner explains is similar to Archie's downloading of a test to a target processor. See Ans. 30. Thus, Archie's execution of a test is comparable to Appellants' unclaimed step of performing the task, not the claimed submission of a task for performance. Appellants provide no persuasive argument why the Examiner erred in finding Archie's disclosure of assigning a "MODIFIED" identifier if "the test had been modified since it was downloaded from the test storage hierarchy" (Archie col. 9, 11. 32-36 ( emphasis added)) teaches or suggests the disputed limitation of determining 13 Appeal2018-002742 Application 14/923,803 "that the control file has been modified since the submitting of the specified task." Appellants' argument that Archie's determination that the test was modified is before the execution of the test does not demonstrate error in the Examiner's finding that Archie's determination that the test was modified occurs since the test was downloaded. Nor do we find availing Appellants' contention that Archie's test is not a control file that has been modified since the submitting of a specified task. App. Br. 17. Notably, the Examiner's rejection is not based on Archie alone, but rather the collective teachings ofNalis, Headley, and Archie- Nalis' teachings including a selected JCL test (the claimed "control file") and a task the JCL test specifies as noted above. Therefore, such individual attacks on Archie's alleged shortcomings in this regard do not show non- obviousness where, as here, the Examiner's rejection relies on the cited references' collective teachings. See Merck, 800 F.2d at 1097. Therefore, we are not persuaded that the Examiner erred in rejecting claim 3. Claim 4 We sustain the Examiner's obviousness rejection of claim 4 (Final Act. 15-16; Ans. 30), which recites, in part, returning the associated reference comprises returning an indication that the control file has been modified since the submitting of the specified task. Despite Appellants' arguments to the contrary (App. Br. 18), we see no error in the Examiner's 14 Appeal2018-002742 Application 14/923,803 finding that Archie at least suggests returning an indication that the control file has been modified since the submitting of the specified task. To be sure, Archie does not state explicitly that this data is returned as Appellants indicate. Nevertheless, we see no error in the Examiner's findings in this regard given the scope and breadth of the term "returning" which is not defined in the Specification and, therefore, is construed with its plain meaning. The term "return" is defined as "to send back." MERRIAM- WEBSTER'S COLLEGIATE DICTIONARY 1001 (vb. def. 3a). Archie's user is prompted as to which fields of a RUNINFO record the user wishes to display. See Archie col. 13, 11. 30-34; Fig. 8. Archie, then, at least suggests sending back the RUNINFO record to the user when the RUNINFO record is displayed to the user. As discussed above, Archie's RUNINFO record includes a component TYPE field that is assigned a "MODIFIED" identifier if the test was modified since being downloaded. Id. col. 9, 11. 32-36. Archie, then, at least suggests sending back a component TYPE field that is assigned the "MODIFIED" identifier if the test was modified since being downloaded, and when the RUNINFO record is displayed to the user. Therefore, we are not persuaded that the Examiner erred in rejecting claim 4. THE OBVIOUSNESS REJECTION OVER NALIS, HEADLEY, SIROTA, AND ARCHIE We also sustain the Examiner's obviousness rejection of claims 10- 14. Final Act. 16-19. Although Appellants nominally argue these claims separately, Appellants reiterate arguments similar to those made in 15 Appeal2018-002742 Application 14/923,803 connection with claim 3. See App. Br. 19--20. We are not persuaded of error in this rejection for the reasons previously discussed. THE OTHER OBVIOUSNESS REJECTIONS We also sustain the Examiner's obviousness rejections of claims 15 and 16. Final Act. 19--21. Because Appellants do not contest these rejections, they are summarily sustained. See MANUAL OF PATENT EXAMINING PROCEDURE (MPEP) § 1205.02 (9th ed. Rev. 08.2017, Jan. 2018) ("If a ground of rejection stated by the examiner is not addressed in the appellant's brief, appellant has waived any challenge to that ground of rejection and the Board may summarily sustain it, unless the examiner subsequently withdrew the rejection in the examiner's answer."). CONCLUSION The Examiner did not err in rejecting claims 1-20 under 35 U.S.C. § 103. DECISION The Examiner's decision to reject claims 1-20 is affirmed. No time period for taking any subsequent action in connection with this appeal may be extended under 37 C.F.R. § 1.136(a)(l ). See 37 C.F.R. § 1.136(a)(l )(iv). AFFIRMED 16 Application/Control No. Applicant(s)/Patent Under Patent Appeal No. Notice of References Cited 14/923,803 2018-002742 Examiner Art Unit 2191 U.S. PATENT DOCUMENTS * Document Number Date Country Code-Number-Kind Code MM-YYYY Name A US- B US- C US- D US- E US- F US- G US- H US- I US- J US- K US- L US- M US- FOREIGN PATENT DOCUMENTS * Document Number Date Country Code-Number-Kind Code MM-YYYY Country Name N 0 p Q R s T NON-PATENT DOCUMENTS * Include as applicable: Author, Title Date, Publisher, Edition or Volume, Pertinent Pages) u The American Heritage Dictionary of the English Language V Microsoft Computer Dictionary Fifth Edition w Merriam Webster's Collegiate Dictionary Tenth Edition X *A copy of this reference is not being furnished with this Office action. (See MPEP § 707.05(a).) Dates in MM-YYYY format are publication dates. Classifications may be US or foreign. U.S. Patent and Trademark Office PT0-892 (Rev. 01-2001) Notice of References Cited Part of Paper No. Page 1 of 1 Classification Classification i.:;: .... ~-...~ ~·,,r ..... ~~ ...... - ~" ~:·' :·.:.;_:· ... ,/-?":·::·i :.::.:·:, ~:}:-;: .. ;·~·::::.: . .:)r: :.:,i: :_.:·.••:' ~-~·:).:: .~.=~ l~:,.:·r ...... ,_, ·. : ... > .,., .... ,:-...... : ":,,:; :~·= :.~·: :·:·~: ,~·r ;.~~-.· ~- .:.~. ~ ~: ·~.:.: :·.:-{:<·~~ ~~-; : ...... : ......... :; : ........ : ... <: ..... ; :.;. .. ,._._ .. ·~ ~-~··· r/:,~~1(~·~;.;_t:·~.: \? ;:~3 ::~~t;;;;~.:...':~'.:.~·~~t i {;,::"" s::.:f[:>d.:ty ::.:.:. =:~-~-=~~- :·~·:.::.::\::~·:·::::~·:··k. (\~p::-·r.:./:·:,~ ,..,... :·~:::-~~ by g,_: .. ~:f1:t(,?~ :'J;·:t?:~c ;·~~:· ... ~.;::p~~i\'/ \L ~-~gJ).t .. ; ~·\'::·.:;<::·:,::·:·} . .. ,?:·::.:·: ::--!· b~· .:=:::.:.:,.· ~:::•:·:J::·:,"3 ~:/.::.:...-:·:·::,:_:·r:;..:· ·)t ·:·:,_:_:.:'(·1.~n;~:·:.::-L \~:(l(.:/:.i:r:g :"'.';:":·: ,::.;~:.:>::·>~-; :3~·~d r,:·<·•>:'('.\~·:·;:r ,)':· ).::·y ;:{':"(/ r~~f:·;.r_~::.":.~:\:-:;:~·i :;:~;)r:::'.g<· ::-.;: -~ (:·:.::j.r·"-;. :·.-·--; :·· ... "> "'-.;"' \ ~-; :.~ ~. \.h::: r,::-.'~\)~ :,,:,.,·:·~ ;J.•::-::';. ..... ·.::.·~-.:<,_..:. :'.ti.:')h.:;; (':·.:·:::·:p~-:r:.,:-· ~.,_::::,~s:: ·.-~x::::.h -:..~,::\.;·· .:.~~ :.:: .. /~.d~·3 ~·{;··$'$ :\····:-·: ·.:.·.:.'/_~-= _.:\.~·~:;..:~~·i:::.~:_~-:_ h~:ri~::~:::.::.:·· .-3_~;~:~·i:::·:·_;:::::·y ,:::.f :·.~·::':· ~-:~~- .... -~·. :_; .:.~ .. · .. :-:-·-~·-~:.-.:', ... :_:fd fd .:: :.hz~· {~"\;.::_..':,:· (:'£ :·~}~; :.::i(•,\;_: ~':'~{'~~. :~ ..• '~ ::~':::.::.i,:~.:.:;:')' ~ ::: :·:~·:::{~(; :·);·; t.} • ., . ..;:., ,-.v,·. ~.-.·,· ''-' '-'-'-·. :,-· ~ -• .. ·.:''S)}:;;;,;i:;:i;.· ···:·-, .. ···-~ :·,:- :· .:~;::' -:~. ·:.:·. ·.·.: ~-- :~•:-::: ~r~ ... ·d~sd~ (;.~ ... x: :·:-:·:(: ,· :- :::· · -,~~k~d .. :-:)~~· .. "~~k:-d .. ~~~~-· ---~~k:·~~~~, ~ .. ·::>·: ~;>~:-,: .:.:-;_ ;:.-:..:-: !· •• :.·= . • -•.. ·.: ..••• ~ '"·.::. ::-:-· :, y~~:-::-:::~-:.:·,. ~. ·r .. :-. ·'"'"·'·:-·>.-.. }, .- ~:~-.:~ ...... ~:,~,::~·: .. ,_._; :.:::..:..~:-:_:.::·:·::.~·-,::: ··_. · .• :::: .. -<'•.;,..__ ~~-- -~~(:::,:,,·.:-~,~:~,:'>' .. '.;fr.._·.··~·;:--~~,:..·-:: m-. ::.,::·: ~·:•:-::::· :,::z~Y,,,,•,,, .:~.:'d -~~'\\.._',-' ,, .. :,'-' 0:,:•: -•. .-- .... :.-., .... ·. ;:~:: :_:·~:::{~:-·,'.::-: ,,·:_::.:!-:..~ :-:~~~::::; :::~:::.~ :::·:-:: !:.:-::: . .:. :~:-~···::.:' ~;,-_:,.,::.:::~~r<.: ~:-::;,~> ;-..,:(,.:... :--.-:::::::. ~;(~..:_. :::~-:·.:~•:- >•i-:::--:.·:-: :~~· .::.-~)~').._.~~r;s,~. :·.::·):: r:·:-...: .. :.r:::·;:,.':·~; ~-:.z-::-:. : .,:,.~"<-·- •. :·.··~·"· :: :':,:,:::~·::::::. -~. ?.,~.:,:-~2::.;:~:-,:.-:.~:;.>:. _:~.-,:·:~~~·.-_~ :,;,:.: ,. .. ,,~ :, ..... v . .,,· ......... ·.··-· ..... :-:. -~ ~:. . '-. ' ::- . :-; ,:•: ., .. ;.~~:l ,:~·-~~?(,. ~t~,·~-:ts.~··:E·J::..~n -i!:·: .. ::d(;.: .. ;-::·h.-:·:~~ ~;.. ~~ T~~·:.: :.,-..-~ ···? ;·::· ~~~~~:t:::: , ... , :~,r ·:·::.:: ,·,: ;_._:: :·):'-:.::,? ~~· .. -:: ! ::,:1~:._-:. ·:~. ~:::·::-:x·::::::-:.;: ·::·,·· L:-.}~ .. -.~. ~::_ (;~-:-.·~,:.-~;;:.,.· :-~ i~, ·' (~)ij· ·· r~~ ·· t~1 h~~,~:-.~.. '..\.': ~:; , .. ..- .. ,:. ~ ~n ,• ~~-:.-:-.ij V ~i ,•t,~ ~~~,~)~, ~-;,:::.~: ,.,: .--~: . .,;5"~):!-':-. ~. -~,::.:.:· h1 .. (:{.~ij ~ S"~~ ~' ~"'~::,~-~ ::~:~--;·" .-.~~~~i- '..'.'·"~~-~~ .-y( ::: ..:-;·z~:::~:!:-::-:_.;.;;- :::·::~··:::·.:;.:: :-:: :,·,;_:,:t:~:.-:~i::·-:- :-: ~ :)f ~-:~v· :~v·••· fr~ ... ~-:.:~~~ ... -h~~~- ., ~~f~<:-::~ ::~:-: .• :::.:>. :::;;,;- :.,i:•:::: ·: ~' ~~v ··x~ h:.:·::~;: it:·.~:..:::.~·,-~·.,;:,. ~. ~.:_:·:::::.,: t_~;,:;,::::.r .-.(~~, .. .--~-. ~~"~·,·~--:.ts,h*r, ... ~3:-n .. (y ,~~-~ i-:<:--h~, .~: .. :-'"-~.-::, ~: :.:·i. ,-~:i,;,.;;·~.- :·:::·:,: ~J~'- ::it•:-.::...,:--)" { :·!: ~:· ,··::: h:3·,·::(r·· .::_~: , ..................................................................................................................................................... ... PlIBLISHED BY MKrn.·ml't Press A 01~.-i;:io:s1 of 1Itr:ro~:oft c~.)tpo'.r,\fion One :Mic:ros1)ft 'i:V2y Redutond_. '\\! ~r:Jhngi on 93GS2--6?,99 ... 411 -right:; reteri;.?ed. i{o p~ut t)f the ctu~tents· of ~1si~: hook n:~.J)' .. De re·prDd~r:ed t~ uan.:;rnHted in at~y fon:n or hy .3.fiY ·n-1e3n·: '!.~:it.~{H3.t the ,,:-ritte11 pt;."n.ti-s.sian cf tht" _p:ubli:her. P- C~3l- :t3B!{ 0-7.3~~6--149:5-4 AQ76.5. 1fi2267 :?li02 004~_D3--.dc21 2:G'Dl-19714. 2 3 4 5 6 7 8 9 Q\VT 765432 1.flr:nJ:}oft :Press hook~ ~tre ~1v0:;J~1W.e diro~Jgb. book:e.He::::s ~3lid thstri:bnto:r::. ~':-'orkh~~~~. ~For frtrther in.fot1n~i-· tion Jbot1~ intetn~:honzi1 et.hJior~::;~ cont~ct yo·u.r lo.:::.:J ~.fic1uGoft Ccrtport~faon oft1c·e or [':Qntact l\.:ticro-soft P1e~-3. Ir~te:rn:1tic1uli direr.tty ;)J fRx (-425) 936-7~~2.9" '\.!i~::it Oltr \'\teb :ite &t ~v\~"''\,··.tnic.n:.t~oft:.t·ru1:1i1n::-.:1).tf''3.'3 .. Acfave: De~:i-;.top, ... ~4,c.ti~:·e. Directory, Acti~:e1ioYie~ .. :\~ti~ .. :e:3to1e~ .. :\cti'..-~:3yn~. i~ctir.,_;:e}C .lluthel1facod~ .. BackOffice:. BizTalk~ CJearT'YJ...~- Direct}fJ: Dift:-';-ti~~in1ati011, DirectDr~~Y1/: Dife:e.th:~p::;3.t~ Direct1·hDic-, Di:i:ec:tP1:l)'.. DiH-:ctS:l:ii:}w .. DfrectSmi.m\ Direc:tX. EntaRrn.ge .. FoxP:rn, FrmitFage, Hotmz:i.1- In,erl.iP.ye. fateili.MotVie. fotelliSe1,5t, JS(·n:pt, MapPci!tt, 11:icrnwft ~b::1·0-,oft Pre-,-,., Mobile Expla.re;;, M'.:l-DOJ, MS?{ M:i.1~k Ce.11t1:&L NeHVIeefing, Cfotfonk. PhataDrnw, Pm.'T. Xb:c:s: a,:e eit.hertegistered n.,,,:knu1·k, or tr:1dl:'B1Mk; of Minosaft Cm:pm:z:fio.a isi. th~ lfo.i;ed State,; 1i11e/m: Gfaer ;::mmn::ie:, .. Othl:'1 _prndiKt and r:{n:npa:ny nZ!:n~2 inentior1ed.hereirl inay be the tradei-nark:::- of their respe.c.tive tn~=·n.erss, T11e exan!p1e co1~lJ.l=Jrties~ org~:sniz~~~ion::.: .. ps·odiJ.rt:s. tlon1~~ll1 na1:nes.~ e-sr~.ail ;1dd1esse:::. logos~ people·. p1~'.:ces. .. ~ui{i e:,:ent::: de_pi.r:3~d .h~rein J.:s-e fictitions No &~~rn::iJt°Snn \~.jth 2n1y· .1eal co:nipn:.n.y: .. 01gr~11.iz.:::.:ti-rn1. produ.[:t, da:ff~3i.n 1i.,;1rne~ r.-·n1z1il ~~~·Jdre::.:::.:, logo .. pes·s.on. p·h-...ce .. or e·,)eltt.i.-s intended t:ff :hou1rl be Utfe·n~d. AcqnhH:hm:s Editor: Alex Bfa.rikm Prnjed Editor: S.:ll1dr,2 Hayne:, {~.x;_=unpk---~ alpJ1~:i.fx--:ti<'. ntnnt':ri~: ! ~::,r fhiancj.a{) ttH~f -c:an bt"'= pktt::fx~ ~J~ therB~ ~rhe f~K·tH~y ft)rcit::::1th1gth{.°!~e s.pl~cHica-· tio.ns BsuaHy b: .c:Qnh:d:ne:J. ~n ahe dI~ta Jx">:fi.nihon tinguage (f)[H .. }, tfi ~"t~!at3Qna~ .£f:.:H~tl'$:at~i fnan~~~e.n1e~tt \'fstens:.;~ :fie~ds are c~~lh:.~ -c-Dh1.uu.u. 2, :~ ~pace iJ:1 an .on--3~""-ft'·en forrn \)"-/ht":re the: H$er cBn enh::~r a. ~p~ific :~t.~fB c~f ~:afcwrnat~-on .. f}eld..ette:d transistor n. See FE'L Field PtogrnnirmdJ!e Gate At·rn}' fl. Se<' FPGA. field·ptograrmnahle logic army n. i\n iim'grnk'J cin:uit i::ontaining an ,::1-n·ay of k,git .. -: .::;in .. -:~J~ts ~n \~:h~ch the: c:on- nedkms betwee11 U1e l.11iiivhiu;.iJ ~,irenits. and Hm1-: thr: h.J:g)c. funchork~ of the :arn1y, can b~ pnJgn.unn1.:::.i:J after n1~u1ufac:ture .. t}ph:::-~ttJ::t a~ the tin1e \~f insh:iJJ~~t:i(~n :ln th~ neld. Prqgr~~HHs1~n.g .i:;an bt· pt':rforn1~d only .o·n:i:..~.e~ lypi- £:.aHy hy pas:~:ing high -current through fus~hk: U:nts. OJ'."t ~he= chip. /i(:rr;;::~ytn: FP1 .... i).(,, .AL~<.t f·a.Jlt."'d:= PL}\ .. pro,gr~~3n- field separ.~tot n . . :\ny chHtpt(t dt~\··:k:e .. file allocation tah!e n A,. table or H,t mainti>in,xl by sorn;;:: n·per&ting s.:v~~lt"::rns. tn nKtn.age dt:,;k ~pace us.ed fnr file stontg.e. f'He.!": Pn .a dh.:k afe s.:tnfecl:... a~ ~.pac::: a~Jo,\,·s., h.1 fix;;::d-5.iz;;:: groups. .:)f b~{te~ (ch.arac.ten;} rather th~n ·trnrn beg~nnSng to end u:s ('"C';:nt(guous string\ pf te:xt -or :ntunhe:rs.. i\. 5-Engk~ fd~ t~an. thus. t:.::~ ~c-~~u:.::.:-r<:·d in pk~(.:~s. .::n:r:r In~tn)• ~:e-p~u1~te s:torage ru"ea_~:. :A fde aH~x-~~~i.::Jn ta:b]e n1aps. ~e,,aH- ;;hk Jhk .$trn:ai:i't 'Spa.:~ "'-(;. that lt ;;;u, i:nark Hmvt:d st:g- n10nts that ~-.JK;.uki. not ~: Bs.ed ~1:nd s-.... -:;..1:n fir::. ,;;he ,,r ,1 file for tran~;·n~i~.;~.;fnn or ~:ti::rage .. :-'5°l~,~ l.i/::.<:J data cornpn~-:;s.:fort me cm,tm! hltH::k n, A sma.H bk,ck of nwmMy kmp,)- nffHy a~s~gned. b)' ~i ctHTiputer"$ or,~r~~ting ~yst:::rn to hc~}d lflforrnmfon nhow .an ,,p.:,n,;,d file, .A !'ik U)fli:wl t.k,d: typ- ic::::1-i~~:t cont.a~n~ ~u:eh in.frHTB~1tion ~1:f,. ~h(!: fiie~s id::::ntific.~:.:rt~on~ it:,,; k:tcatS('tB -CJn I~ disk~ and. a p·c·:i.nter that .n~arks the us:.e(·~ ntrn~m: (;.:1 pri-- n1Hri~y \Y~fu n1ainfr~n11e c·)atYq~uters) to i\S(]l ch;;1r;;1c:tt"'.:r~;. Se,,' aho ASCII. EBCDlC. fl!e form,:1t n. The strm::ture of a file th;it dd'\m.,& the ,.'>'!' fr,t.'c spa;;.:e ~arge .:::ni:)ugh to ho{i:J th:.'!fft:~ FEh: i~ragn1ent:::1tk~n ~~ nt"ft an ~nteg-fity prohlefi~" -~~hh.;.)B_gh h can -eventu.:~H} s:kr\v ri:<3.:d ;1_ad ..,_~,.ril.::: at-:c.:::~:~: !i_as,;;~; tf the ~Ji~-ik i~ vt~r;:· ~l~Jl fHl.~-ai:--0 produ{'t"& Hre ;;r~:~iH~ih~e for n ... ~ii!';~rHtuttng (rc:phsni1.iLB§J {He $tor-ag~· to redu'-:e fE .. \_~~nt~n- Hih·OH~ 2. In i.l dat~~h~rs.c~ ~:l s~tuf~hon in \~·hic.h R~.(.~ord& an.~. n~Jt !':ot:ored tn their <>ptfina~ ai;,_-:(:C~$.: ~-t:q:~~eni:e be,t;_\u:..;;.:: of at:(:H- n1utated ~~dtiftio:n:,; and <<<< .,,.:,.:-:,.:-:-..,,,,,,-...,-..-..,.,,.,,.,.,.,.,.,.,.,.,. .................................... :,.:,.:,.:-x,,,,,,-... ... -...,-...,-..-..,,,,.,.,.,.,.,,.,.,.,. ....................................... :,.:,.:,.:,.:,.:,.:.,,,,,,,,,,'-"'''"'"''""""""""""""""""""""" T.ENTH EDITIO_ ,v 11, Ji O WM~,, Ji!!, l©tl, w;,,ts, •mi I · 11111!1!1!11!1!1111 I •• -·,········ic!II!Ii:::::1,1 "~""··· ... "'_._1111111111111111111!11111 ·tf~r::s::.~y <:.f (\J~:frt:~.,;: (:~;J:..:.~tD. ····· {SJ$N ~}-~:77~?~}. 7~(\-2 tJ~.-:h:.:H:}.. ... ,. !S:HN' ~:~-~7T?~'.,7(fl.<~ 0.fr:nh~z.t.\::f~ z;.:._1~,~~d. 1 'E(1t~~d~ t~ns·:.s~::if::····l'Jktfr.::~~::.xri~':~, i. ~itn-S·:E:..ri>.~-\\\~~~st~:·:-} t;x;. PE~t~J~~-f--·t~f, 1.9~}~; i? ~ ,t:- .. !O ~ J.~.~f>~f~{ ! :·>:· ~!!·} ;.~~~~:.:~>)::;:{c ..•. ~ ,:..,:::··~· H~~~t 5x ~::~:'{:~:·:::,i ?~[@\~::::..:,'::~::::-~X::(~~.~ !·~, L /'., ............ ~~'-'., :-·:-· ··< .,,,., ~'.~\~~i~~>fr, :--.:.:-::-\:,,_. -~- ~:-.:}.:-r,:- ,.":,:, ..:.~fr,·s.:· .,,~ ::::~,:::::s.' ;:,;:. I\J;~1~It~t~~;;;~:i il~;;J;~t~;i~~1i\g~i:~'.i~:~~':,~~~ii~}~,t~~ttS fl(\~i\ =-:: {;:~~;,:3-;, ~ ~x::-;~_-._:-R:·:,::_-:{f:·~· ·@::::::::::~.: .. X~w:..,. ,:,3. S{.,,, ... ~-:, . . ,k.;,., :· ,,:.;:,. b,z:.,:;:-.~~-=- ':3'>:-f!:,.<: 11\1\r~~r t~t.\~:~! ;;i;t~~;~~:f~:~~::~;}~\\{.f, ,;:-~:c;:~.~ .. i:-:~, 11:};t;::~ri:::f i~ttt:,1::\ti~li1tt;~;; :~i: ti;Wft!/;,;:::}~:'I::,, t ,,t·,.:\\G ;;~/t/t;~, H'i .}~ff.f::. ~~r, ~~~:~~~x~ ~~~') ~·g, ..:.:,.-: .. ~~~~ :::::,:~K -~)~~, ::·:-~..:.k• "''''"':·· :!§:.%{%:,:>ti<)ll \,.,.,,,r:/ik,,,,,;,,:s,\,: ()i:',,) ·,: ,,,,, ~~~:;:::~~~') :: H~·:- ~~-:-:~}:.:fa:,:~ ·:-:.:~t:k :-:-~ fa:: :...: :fff~):::~:~t· :!-{ ;.:·•\:-..:-::~~ ~:-t !:·~::-:t-.:.:~,:~W . .- ...... .-::-. !~~~l~~~~t~~~~;~~,f ~1~;;~:::; ';~r~~ :{:;;~~'.~\ ,:;x,,L'.,;' ;;~ ~;~L,,,;~,;;;:': , .. ,,..,;;,,.<;- .',.,,.L:. ..,m·, .\·}:-,ts:·.:~}':o:;x:. ': \~: .. 3:-<:-:~~\ -..~:# ~L ~~:,:~~:=-~~·:-.::.:. --~-:;:,"):.~. ~:.~ t:::~~··ff~::~~-.-..,~:~~ :·.~~~. ~ -?~\: ·~:~:i~);i~I1:::~\f;:\;r~11'.Ir~:t\':,i::,?~.:.~:,I~.:.i~.~-,., .. _.i.t,: .... t.t.,;_.~;_·f~~;,'f ... '..: .. '..f.'_t,.:;_.;_: .. ,.',,, :,,~:c~~;:. ,~S· ~):'· ~')~:~.:.~~~&~~.:.~::r•:::-::,: $•~~\ -.:,::v:.::fW: ~... • ... , -..--.. •• • ., ·-.. ,.., l]il~~~i~~:i;~'~;;i£~~i~~ .-. -.~·~·-··-~S.:·., ,,_, , ..•.. ~-.. ,..,., ..... K ·;;:·,'.~ . ·~~',:,'.:_;;,·_; •• ,.~,'_ .. :\_,,:_-.:~.~_:{,.,'.-~,.··~.:,_:: ~ .. t;~~~~~~;~:::.~f·(:;.:t~~-(~\;~ .. ·· ·:~ :. '-~ -.::.::-:k ~5~:,. fr. \tf. ~r. ~--;;,·. ,:~..,;::::..~:-.:~·· ~<:- ~.r::.~.x; r:·:r:";:· :::::::· · ......... . \.:~~\~~;:\\~~~:~?:;~ {~}:;~:/~~~::? \h:~,~ ,::/;{; •. , . !~"-·': X ,.,.::,_.-,,:_~, fr. tr:::--...:.. -~ ~-.: ~-.~~; ::. ~,.~".'. :>:· .,:,;~,·~::~'~·.,\.• .•. :.'.\.i.~.~,:_~<:,:_··:_;,?_:~~-~;.··\.,,~?.>~.:·.~-~-~.--~.:ir,:~.;-~ (~;'>~.-.~ 'S :' ~-}..~-: ~~{:~1:·fo:,t· i~«,:.:::-_.,-...<-..,~i :;l ·--- , . . • ..... · , ,, , ' ,. ,•";::, -.> ,~·:; ?•C:t ,~: ·:<.:-~,~~: ~·x-.-:~ ~,.'.:~ ..... ·3'.;:~~.-::- {::,:·~:~~~ :2:· :. ~:f- t;~~~:\~~~l;~ 11i1:Pt!t1!;\f !~~'.1{1f i:I0'. 1 ~l\,.\t.'._~.i_;_:_~',\_lE_;1_:;t~.:.: .. ;,_,}\::-:.\:.·?. ::.:1.~_.::_}.\,~. ):..;:;-::;.:~- , i:"iS.!::· .... :..:.-::·::. n::-:X~ ;:_-;~::., , - , ..... - , ... . . ,,. h: ~·x::- :s•>•.c:\:,': : ·{~~:::)) $i' '-;,, ~·=· ,-:~\~J.\' ·:~ ;··~:~~~-;\/t :·,:~_:\~} :[:_}~,):, ;",,:,",-...:h~lY"~n' ~' ' ~.~1:,: }.~ ... }. :,..,, ~~1:1::· ~:'.{_g~,i~:;t]~;~~sf ~~l\;~;;~:,'J 1:\:I~it~:~~\1;I!t1~Jf t;:~ii;1: !!~ittlf ~l:~!!~l~tf ~:!I~~~ :-'•·''-'"~~·-:.. -~: x0.~•·. ·. ~~~.:..::·~~11-:~ .. :~H~:-,v~ .. :-:.,!.-~ -:~·::-:5::!·.:~~ :{~~::::. ,:-:-:-~3 s.":-::.:::::n~p~~~~r.:~.- :...:.,~..:..~ ~~~L~'.-~~~g~r~~\~J:.2\~~:~~ ~\·:~ !~t~i~~ :~Ir::/\?tL~;~t!t:~;::::~tt~~~r:~~~~~~~~f: ::_,,.s)hfo:~~ ':·f d .:-: :":"~<;,;:$i,:·!~ ,:_,:: i~'·'.-~)f• ,:§ :r::d~~~~~;:::: b .: X ~;.;:s~~' ;-_~!-;;..:.,~ .• -:,.1-: ~;~~'~;~'.m1~~;~;;?:;~t~;:~;~;;~~,~~;%r;~~1~~~,,~;';~E,~~;~::~::·:;,:~'ti:\~'.r:'.)i :.m·~ -.: ... :.:L•.• (:~1 ;:_,,:' : ... "::·->•; .... : .· .. :.x,r>:· .. t :;;;;~~~;;;;~.il~i~t\~~~-\~:~.; ... :;;:.·~;~}('·· :· ~.~; : ::•:·t~i.:.::; r:;;.;~~~:··~~: ~:~ .,~:- ~~;~:···~I~~~:~~:~~i-~~;\~~~/· ~-~· ~~ \ ~ :~«};~{~~~~ :·:-~~··.~ r~:.:;·~~~~~~ •.".'~~~..:..:~ '\~~;~·~. ~,'.:::n~::~~~; :::-: .. ~:..x :.-.w: ... ~ h. ~::,,~-=~-.-~<:: •. ~ Z :, 0 .. •.~.-.m· .. t:-:' \.:/:.. :.,:::.,~~~ ,._:,, ;:}f~·~:.~. :r :·s:.~(:.~!- ':.:.;:::"\ i~r::h::::r \:-~: ~~:~~~ \;";:\ :,~:~: 'X: ~1-:<'.:-h :::~:s~- ,~~,-... . .::-::::: \~:~::\ d::~:; ,,::-~ :-:,,f:: ';,}\ ~:.::::.~· \.;::. }:::~ ~;i, :~:~~- ':~\ ~:~,::: \!\ j:t~ ,~~\ ::-!::~~:. i,/:\ ;~:-"!- ";/:~ ~~~- ::~h ::,,:..;))' \::~~: ~~:.:~ \:_t:i., ~-~::-: \fr-:.1-:~"~ \;/\ :\..:-:..,~· ,,y\ :?:~:. <~}:.:\ \;:~~~:):~ \~. ~-· =·,, ;.::,:,.. <~:: ','\::,. <~:;. :·~ . . :,:,-~: ($'!~~k ::> t~'>:,~':-:::.:.-..-::.s:::::•:·~ Copy with citationCopy as parenthetical citation