throbber
Case 1:19-cv-00859-RTH Document 69-5 Filed 01/21/22 Page 1 of 59
`
`1
`
`
` IN THE UNITED STATES COURT OF FEDERAL CLAIMS
`
`
`
`
`
`Plaintiffs,
`
`
`
`v.
`
`
`E-NUMERATE SOLUTIONS, INC. and
`E-NUMERATE, LLC,
`
`
`
`
`
`THE UNITED STATES,
`
`
`
`
`
`
`Defendant.
`
`
`
`
`
`
`
`
`
`No. 19-859 C
`
`Judge Ryan T. Holte
`
`DECLARATION OF DR. DAVID MARTIN IN SUPPORT OF DEFENDANT’S
`PROPOSED PRELIMINARY CLAIM CONSTRUCTIONS
`
`
`TABLE OF CONTENTS
`
`Personal Qualifications ........................................................................................................3
`
`Scope of Opinion and Legal Standards ................................................................................5
`
`I.
`
`II.
`
`III.
`
`Patent Backgrounds .............................................................................................................9
`
`IV.
`
`Technology Background ....................................................................................................10
`
`V.
`
`Person of Ordinary Skill in the Art ....................................................................................11
`
`VI.
`
`Terms from the ’355 Patent ...............................................................................................11
`
`A.
`
`“the step of receiving…” (claims 15, 42 of the ’355 Patent) .................................11
`
`VII. Terms from the ’816 Patent ...............................................................................................12
`
`A.
`
`B.
`
`C.
`
`D.
`
`“markup language” (claim 12 of the ’816 Patent) .................................................12
`
`“means for receiving a first markup document…of the
`second markup document” (claim 26 of the ’816 Patent)......................................13
`
`“means for automatically transforming the numerical
`values…a common format;” (claim 26 of the ’816 Patent) ...................................16
`
`“means for combining the first markup document and the
`second markup document into a single data” (claim 26, ’816
`Patent) ....................................................................................................................20
`
`Case No. 19-859C
`
`
`
`DECLARATION OF DAVID MARTIN
`
`

`

`Case 1:19-cv-00859-RTH Document 69-5 Filed 01/21/22 Page 2 of 59
`
`2
`
`
`E.
`
`“means for displaying the single data set” (claim 26 of the
`’816 Patent) ............................................................................................................21
`
`VIII. Terms from the ’383 Patent ...............................................................................................24
`
`A.
`
`B.
`
`C.
`
`“means for identifying a first markup document including
`first numerical values and first tags reflecting … associated
`with the second unit of measure” (claim 18 of the ’383
`Patent) ....................................................................................................................24
`
`“means for automatically transforming at least a portion of
`the first or second numerical values… have a common unit
`of measure” (claim 18 of the ’383 Patent) .............................................................28
`
`“means for processing at least a part of the first markup
`document and at least a part of the second markup document,
`resulting in a single markup document” (claim 18 of the ’383
`Patent) ....................................................................................................................32
`
`D.
`
`“means for causing a display of at least a portion of the single
`markup document” (claim 18 of the ’383 Patent) ..................................................34
`
`IX.
`
`Terms from the ’748 Patent ...............................................................................................37
`
`A.
`
`B.
`
`C.
`
`D.
`
`E.
`
`F.
`
`“code for storing a plurality of original documents including
`a plurality of original values, including a first document
`including first values and a second document including
`second values” (claim 11 of the ’748 Patent) ........................................................37
`
`“code for processing at least a part of the first document and
`at least a part of the second document, … of the plurality of
`original documents” (claim 11 of the ’748 Patent) ................................................39
`
`“code for receiving a user selection of one or more
`computer-readable semantic tags” (claim 11 of the ’748
`Patent) ....................................................................................................................42
`
`“code for receiving a user selection of one or more of the
`original values” (claim 11 of the ’748 Patent) .......................................................44
`
`“code for mapping the one or more of the computer-readable
`semantic tags to the one or more of the original values”
`(claim 11 of the ’748 Patent) .................................................................................47
`
`“code for outputting a report… results in a corresponding
`change in an instance of the report” (claim 11 of the ’748
`Patent) ....................................................................................................................49
`
`Case No. 19-859C
`
`
`
`DECLARATION OF DAVID MARTIN
`
`

`

`Case 1:19-cv-00859-RTH Document 69-5 Filed 01/21/22 Page 3 of 59
`
`3
`
`
`G.
`
`least one computer-readable
`“code for outputting at
`Extensible Markup Language
`(XML)-compliant data
`document… results in a corresponding change in an instance
`of the at least one computer-readable XML-compliant data
`document” (claim 11 of the ’748 Patent) ...............................................................51
`
`X.
`
`Terms from Multiple Patents .............................................................................................54
`
`A.
`
`B.
`
`“multiple hierarchical relationships between two line items
`of corresponding numerical values” (claims 7, 8, 15, of the
`’383 Patent; claim 1 of the ’748 Patent; claim 29 of the ’842
`Patent; claims 1, 10, 17 of the ’708 Patent) ...........................................................54
`
`“rule” (claims 9, 10 of the ’383 Patent; claims 1, 12, 13, 14
`of the ’748 Patent; claim 29 of the ’842 Patent; claims 1, 10,
`and 17 of the ’708 Patent) ......................................................................................58
`
`XI.
`
`Signature ............................................................................................................................59
`
`
`
`
`I, David Martin, declare and state as follows:
`
`
`
`1. I am over the age of twenty-one, competent to make this declaration and have personal
`
`knowledge of the matters stated herein. I make this declaration in support of Defendant United
`
`States’ (“U.S.” or “Government”) preliminary claim constructions.
`
`I.
`
`Personal Qualifications
`
`2. I have over 40 years of professional experience with computer software. Following
`
`informal study in computer science at Iowa State University in the late 70s, I was first hired as a
`
`programmer in 1979. After high school in 1984, I worked for two startups as a software designer
`
`and programmer and delivered custom software to Lucasfilm Ltd. under contract. I have worked
`
`with the Internet and associated technologies since the late 1980s. I began using web browsers in
`
`1993. I taught computer science to graduate and undergraduate computer science students for 10
`
`years. I earned a Ph.D. in Computer Science from Boston University in 1999. My Ph.D. research
`
`was in the area of Internet security and privacy. I earned a Bachelor of Science degree with
`
`distinction in Computer Science and Mathematics from Iowa State University in 1993. I have
`
`worked at the University of Denver as an Assistant Professor, at Boston University as a Research
`
`Assistant Professor, and at the University of Massachusetts Lowell as an Assistant Professor. In
`
`Case No. 19-859C
`
`
`
`DECLARATION OF DAVID MARTIN
`
`

`

`Case 1:19-cv-00859-RTH Document 69-5 Filed 01/21/22 Page 4 of 59
`
`4
`
`
`these positions, I performed research in the areas of computer security and privacy on the Internet.
`
`I am currently an independent software consultant.
`
`3. My experience also includes teaching courses in Introduction to Object Oriented
`
`Programming (C++); Foundations of (Theoretical) Computer Science; Computer Security I:
`
`Principles of Cryptography and Network Security; Computer Security II: Applied Computer
`
`Security; Unix Software Tools; Computer Networking; Introduction to Computer Science II
`
`(C++); Introduction to Computer Science I (C++); Special Topics in Systems: Computer Security;
`
`Advanced Unix Programming; Formal Languages and Automata; Introduction to Computer
`
`Science (C).
`
`4. I have received the following honors throughout my academic and professional career:
`
`Teaching Excellence Award for U. Mass Lowell Computer Science Department (2007); Teaching
`
`Excellence Award for U. Mass Lowell Computer Science Department (2004); One of four
`
`nominees for Outstanding Research in Privacy Enhancing Technology Award (2003);
`
`Outstanding Teaching Fellow, Department of Computer Science, Boston University (1996);
`
`University Graduate Fellowship, Boston University (1993-1994); Top Graduating Senior in
`
`Mathematics, Iowa State University, Spring (1993); Top Graduating Senior in Computer Science,
`
`Iowa State University, Spring (1993); Honorable Mention, National Science Foundation Graduate
`
`Fellowship (1993); Honorable Mention, Department of Defense Graduate Fellowship (1993); Phi
`
`Beta Kappa membership (liberal arts honor society) (1990); Phi Kappa Phi membership
`
`(engineering honor society) (1990); Pi Mu Epsilon (mathematics honor society) (1990); Upsilon
`
`Pi Epsilon (computer science honor society) (1990); Arthur Collins Foundation Scholarship,
`
`Spring (1992); Dio L. Holl Award for Outstanding Senior, Spring (1992); Shell Oil Foundation
`
`Scholarship, Spring (1991); Barry Goldwater Scholarship (1989-1990).
`
`5. I have been a member of the following professional societies: the Association for
`
`Computing Machinery and the Institute for Electrical and Electronics Engineers.
`
`6. I was first engaged as a software expert over 20 years ago. I have extensive experience
`
`analyzing software and descriptions of software. For example, I have analyzed source code from
`
`Amazon, Apple, Google, Microsoft, Samsung, Yahoo!, Zillow, and other companies, and have
`
`written expert reports and testified about their implementations.
`
`Case No. 19-859C
`
`
`
`DECLARATION OF DAVID MARTIN
`
`

`

`Case 1:19-cv-00859-RTH Document 69-5 Filed 01/21/22 Page 5 of 59
`
`5
`
`
`7. In patent litigation, I have submitted expert reports at least 11 cases, I have testified in
`
`deposition in at least 10 cases, and have testified at trial at least 5 times. I have also testified in
`
`trade secret and anti-trust litigation.
`
`8. I have done substantial work with XML. In i4i Limited Partnership v. Microsoft
`
`Corporation, I analyzed Microsoft Word’s support for “custom XML” in its source code, wrote
`
`an expert report, and testified at trial. In August of 2021 I submitted an expert report describing
`
`products and their reliance on AJAX (Asynchronous JavaScript and XML) and XHR
`
`(XMLHttpRequest). I have written and used XML software variously in my own general
`
`computing work. As a computer science faculty member, I also regularly taught a formal languages
`
`course that explored the expressiveness and capabilities of computer languages specified by
`
`different kinds of grammars. A Document Type Definition (DTD) is a grammar intended to
`
`describe a certain set of XML documents conforming to that specification.
`
`9. I am being compensated at my regular rate of $600 per hour. No part of my compensation
`
`is dependent on the outcome of this proceeding or otherwise has any influence on my opinions in
`
`this proceeding. I have no other interest in this proceeding.
`
`II.
`
`Scope of Opinion and Legal Standards
`
`10. This declaration does not set forth all my conclusions regarding the Patents-In-Suit or the
`
`claim terms found therein. However, my analysis is of the issues that appear most relevant based
`
`on the claim constructions proposed by the parties.
`
`11. I have been instructed by counsel that claim construction is for the Court to decide as a
`
`matter of law. I understand that the claims of a patent are to be interpreted according to their plain
`
`and ordinary meaning as would be understood by a person of ordinary skill in the art at the
`
`timeframe of the claimed invention. I understand that claims should be construed based on intrinsic
`
`evidence such as the claim language, the patent’s specification, and the patent’s prosecution file
`
`history. I understand I am also free to consider extrinsic evidence to help interpret the meaning
`
`and construction of the claims, including but not limited to sources such as appropriate
`
`dictionaries, the general knowledge of one skilled in the art, treatises, white papers, relevant
`
`journals, etc., as long as that extrinsic evidence does not contradict the evidence intrinsic to the
`
`patent.
`
`Case No. 19-859C
`
`
`
`DECLARATION OF DAVID MARTIN
`
`

`

`Case 1:19-cv-00859-RTH Document 69-5 Filed 01/21/22 Page 6 of 59
`
`6
`
`
`12. I understand that the claims of a patent define the scope of the rights conferred by the
`
`patent. The claims particularly point out and distinctly claim the subject matter that the patentee
`
`regards as the invention. Because the patentee is required to define precisely what the invention is
`
`claimed to be, it is improper to construe claims in a manner different from the plain import of the
`
`terms used consistent with the specification. Accordingly, a claim construction analysis must begin
`
`and remain centered on the claim language itself. Additionally, the context in which a term is used
`
`in the asserted claim can be highly instructive. Likewise, other claims of the patent in question,
`
`both asserted and unasserted, can inform the meaning of a claim term. For example, because claim
`
`terms are normally used consistently throughout the patent, the usage of a term in one claim can
`
`often illuminate the meaning of the same term in other claims. Differences among claims can also
`
`be a useful guide in understanding the meaning of particular claim terms.
`
`13. I understand that the claims of a patent define the purported invention. I understand that
`
`the purpose of claim construction is to understand how one skilled in the art would have understood
`
`the claim terms at the time of the purported invention.
`
`14. I understand that a person of ordinary skill in the art is deemed to read a claim term not
`
`only in the context of the particular claim in which the disputed term appears, but in the context of
`
`the entire patent, including the specification. For this reason, the words of the claim must be
`
`interpreted in view of the entire specification. The specification is a primary basis for construing
`
`the claims and provides a safeguard such that correct constructions closely align with the
`
`specification.
`
`15. I understand that the usual and customary meaning of a claim term can be altered by a
`
`patent applicant who takes on the role of “lexicographer” and clearly sets forth in the patent a
`
`different meaning for a claim term.
`
`16. I understand that it is improper to place too much emphasis on the ordinary meaning of the
`
`claim term without adequate grounding of that term within the context of the specification of the
`
`asserted patent. Hence, claim terms should not be broadly construed to encompass subject matter
`
`that is not supported when the claims are read in light of the invention described in the
`
`specification. Art incorporated by reference or otherwise cited during the prosecution history is
`
`also highly relevant in ascertaining the breadth of claim terms.
`
`17. I understand that claim terms must also be construed in a manner consistent with the
`
`context of the entire intrinsic record. To that end, in addition to consulting the patent’s
`
`Case No. 19-859C
`
`
`
`DECLARATION OF DAVID MARTIN
`
`

`

`Case 1:19-cv-00859-RTH Document 69-5 Filed 01/21/22 Page 7 of 59
`
`7
`
`
`specification, one should also consider the patent’s prosecution history. The prosecution file
`
`history provides evidence of how both the Patent Office and the inventors understood the terms of
`
`the patent, particularly in light of what was known in the prior art. Further, where the specification
`
`describes a claim term broadly, arguments and amendments made during prosecution may require
`
`a narrower interpretation.
`
`18. I understand that while intrinsic evidence is of primary importance, extrinsic evidence, e.g.,
`
`all evidence external to the patent and prosecution history, including expert testimony, dictionaries,
`
`and learned treatises, can also be considered. For example, technical dictionaries may help one
`
`better understand the underlying technology and the way in which one of skill in the art might use
`
`the claim terms. Extrinsic evidence should not be considered, however, divorced from the context
`
`of the intrinsic evidence. Evidence beyond the patent specification, prosecution history, and other
`
`claims in the patent should not be relied upon unless the claim language is ambiguous in light of
`
`these intrinsic sources. Furthermore, while extrinsic evidence can shed useful light on the relevant
`
`art, it is less significant than the intrinsic record in determining the legally operative meaning of
`
`claim language.
`
`19. I understand that in general, a term or phrase found in the introductory words of the claim,
`
`the preamble of the claim, should be construed as a limitation if it recites essential structure or
`
`steps, or is necessary to give life, meaning, and vitality to the claim. Conversely, a preamble term
`
`or phrase is not limiting where a patentee defines a structurally complete invention in the claim
`
`body and uses the preamble only to state a purpose or intended use for the invention. In making
`
`this distinction, one should review the entire patent to gain an understanding of what the inventors
`
`claim they actually invented and intended to encompass by the claims.
`
`20. I understand that while absolute precision is unattainable in patented claims, the
`
`definiteness requirement mandates clarity. If, a claim interpreted in light of the specification and
`
`the prosecution history fails to inform those skilled in the art about the scope of the invention with
`
`reasonable certainty then it is indefinite.
`
`21. Certain claim terms at issue in this case recite “means for” performing a particular function.
`
`Additionally, certain claim terms at issue in this case claim “code” that is programmed to perform
`
`particular functions. As explained in more detail below, the claim term “code” in such a context
`
`may amount to a mere verbal construct that is the equivalent to the use of the “means” language
`
`in a claim. Stated differently, in such contexts, the use of the term “code” is effectively a
`
`Case No. 19-859C
`
`
`
`DECLARATION OF DAVID MARTIN
`
`

`

`Case 1:19-cv-00859-RTH Document 69-5 Filed 01/21/22 Page 8 of 59
`
`8
`
`
`placeholder for any structure that is capable of performing the recited functions. I understand that
`
`for such claim terms, they should be construed under pre-AIA 35 U.S.C. § 112, ¶ 6, or, depending
`
`on the filing date of the patent, AIA 35 U.S.C. § 112(f), which recites the same language as pre-
`
`AIA 35 U.S.C. § 112, ¶ 6. Both versions state the same thing:
`
`An element in a claim for a combination may be expressed as a means or step for
`performing a specified function without the recital of structure, material, or acts in
`support thereof, and such claim shall be construed to cover the corresponding
`structure, material, or acts described in the specification and equivalents thereof.
`
`22. I have been informed that if a person of ordinary skill in the art would understand that the
`
`“code” term in a claim to refer to a conventional program or code that existed at the time of the
`
`inventions, then that term is more likely not to be construed under § 112, ¶ 6. However, if a person
`
`of ordinary skill in the art would understand the “code” in a claim to refer to generic or black–box
`
`functionality than it would more likely be construed under § 112, ¶ 6.
`
`23. To construe such claims, the claimed function must be first identified, and then a
`
`corresponding structure clearly linked to the performance of that function must be found in the
`
`specification. I understand that terms written in this format cover that corresponding structure
`
`described in the specification in addition to any equivalent structure.
`
`24. For computer-implemented means-plus-function claim terms, I am aware that a distinction
`
`is made as to whether the claimed function is of a fundamental nature such that it can be performed
`
`by a general-purpose computer without the need for special programming, or if a specially
`
`programmed computer is necessary to implement the claimed function. I understand that with the
`
`former, i.e., where the claimed function can be performed by any general-purpose computer
`
`without any special programming, disclosure of any general-purpose processor to perform the
`
`function is sufficient. On the other hand, for functions requiring specially programmed computers,
`
`I have been informed that an algorithm to perform or implement the claimed function on a
`
`computer must be disclosed in the specification.
`
`25. I am aware that algorithmic disclosures may be in any form sufficient to inform one of
`
`ordinary skill in the art, including source code, a mathematical formula, prose, a diagram or flow
`
`chart, and/or any other manner that provides sufficient structure to those of skill in the art.
`
`Case No. 19-859C
`
`
`
`DECLARATION OF DAVID MARTIN
`
`

`

`Case 1:19-cv-00859-RTH Document 69-5 Filed 01/21/22 Page 9 of 59
`
`III.
`
`Patent Backgrounds
`
`9
`
`
`26. In this litigation, e-Numerate has asserted U. S. Patent Nos. 7,650,355 (the “’355 Patent”),
`
`8,185,816 (the “’816 Patent”), 9,262,383, (the “’383 Patent”), 9,262,384 (the “’384 Patent),
`
`9,262,748 (the “’748 Patent”), 9,600,842 (the “’842 Patent”), 10,223,337 (the “’337 Patent”), and
`
`10,423,708 (the “’708 Patent”) (collectively, the “Asserted Patents” or the “Patents-in-Suit”).
`
`27. I understand that the ’355 Patent traces its priority to provisional application No.
`
`60/135,525, filed on May 21, 1999 and provisional application No. 60/183,152, filed on Feb. 17,
`
`2000.
`
`28. I understand that the ’816 Patent traces its priority to provisional application No.
`
`60/135,525, filed on May 21, 1999 and provisional application No. 60/183,152, filed on Feb. 17,
`
`2000.
`
`29. I understand that the ’383 Patent traces its priority to provisional application No.
`
`60/135,525, filed on May 21, 1999 and provisional application No. 60/183,152, filed on Feb. 17,
`
`2000.
`
`30. I understand that the ’384 Patent traces its priority to provisional application No.
`
`60/135,525, filed on May 21, 1999 and provisional application No. 60/183,152, filed on Feb. 17,
`
`2000.
`
`31. I understand that the ’748 Patent traces its priority to provisional application No.
`
`60/135,525, filed on May 21, 1999 and provisional application No. 60/183,152, filed on Feb. 17,
`
`2000.
`
`32. I understand that the ’842 Patent traces its priority to provisional application No.
`
`60/263,518, filed on Jan. 24, 2001
`
`33. I understand that the ’337 Patent traces its priority to provisional application No.
`
`60/135,525, filed on May 21, 1999 and provisional application No. 60/183,152, filed on Feb. 17,
`
`2000.
`
`34. I understand that the ’708 Patent traces its priority to provisional application No.
`
`60/263,518, filed on Jan. 24, 2001.
`
`Case No. 19-859C
`
`
`
`DECLARATION OF DAVID MARTIN
`
`

`

`Case 1:19-cv-00859-RTH Document 69-5 Filed 01/21/22 Page 10 of 59
`
`IV.
`
`Technology Background
`
`10
`
`
`35. XML, the Extensible Markup Language, is a framework for creating domain-specific
`
`languages that describe data.1 Every XML document has similar high-level structure. Elements are
`
`always specified using “tags” that include the so-called angle brackets “ < ” and “ > ”, elements
`
`may “nest” within each other, and each element that appears in a document must have both an
`
`opening tag (e.g., <author>) and a closing tag (e.g., </author>). As long as these and certain other
`
`rules are followed, the names of the tags and elements are entirely up to the creators and users of
`
`that particular kind of XML document. For example, an XML document used to describe books
`
`might include an <author> element, while an XML document used to describe corporate revenues
`
`might include various <sale> elements but no <author> elements.
`
`36. The Patents-in-Suit are generally directed to the processing of “semantic tagged” data in
`
`XML documents, in which the processing relies on the semantic information expressed with the
`
`data. For example, consider the data encoded within the XML document fragment below:
`
`<line_item
`li_unit='%'
`li_mod='of'
`li_measure='outstanding shares'>
`<data_y>
`0.65, 0.8, 0.75
`</data_y>
`</line_item>
`
`
`This abbreviated example can be understood to represent the three data values 0.65, 0.8, and 0.75,
`
`where each of these numbers is taken to indicate a percentage of outstanding shares of an
`
`associated company; the “li_unit”, “li_mod”, and “li_measure” specifiers together indicate that
`
`this is the meaning of the numbers.2
`
`37. In this context, the Patents-in-Suit claim functionalities related to semantic tagged data
`
`including performing macro (short processing instruction) operations; generating legend titles
`
`from the semantic tags; combining and converting documents to express them in similar units;
`
`
`1 See, e.g., “XML Essentials”, available from https://www.w3.org/standards/xml/core.
`
`2 A complete example adhering to the Reusable Data Markup Language (RDML) of the Patents-in-Suit would be
`similar to this abbreviated example with additional attributes and context. A longer example can be found in the ’355
`patent at 20:24-44.
`
`Case No. 19-859C
`
`
`
`DECLARATION OF DAVID MARTIN
`
`

`

`Case 1:19-cv-00859-RTH Document 69-5 Filed 01/21/22 Page 11 of 59
`
`11
`
`
`creating presentations, reports, and output documents; validating rules; adding semantic tags; and
`
`identifying data that are related by “multiple hierarchical relationships”.
`
`V.
`
`Person of Ordinary Skill in the Art
`
`38. In my opinion, the technologies described in the Asserted Patents draw on a combination
`
`of skills from the computer science and engineering arts. Further, a person of ordinary skill in the
`
`art (“POSITA”) would have a bachelor’s degree in computer science or computer engineering or
`
`a similar field and/or four years of software development experience with a focus on data
`
`manipulation and presentation including work with markup languages. Extensive experience and
`
`technical training may substitute for educational requirements, while advanced education might
`
`substitute for experience. I reserve the right to provide a narrower background for the POSITA
`
`within this range as the litigation progresses, however for purposes of this Declaration my opinions
`
`would not be affected if the POSITA’s background were within the range specified.
`
`39. I note that in four separate inter partes review (IPR) petitions, e-Numerate did not challenge
`
`the petitioner’s, Merrill Corporation, proposed background for a person of ordinary skill in the art
`
`which “would have been someone with at least a bachelor’s or graduate degree in computer
`
`science, computer engineering, or a related field, and at least 3 to 5 years of work experience in
`
`developing software for data communication, manipulation, and reporting.”
`
`40. The opinions I offer herein regarding construction of disputed terms would not be
`
`materially impacted under either POSITA standard.
`
`VI.
`
`Terms from the ’355 Patent
`
`A. “the step of receiving…” (claims 15, 42 of the ’355 Patent)
`
`41. The term “the step of receiving comprises receiving tags” appears in claims 15 and 42 of
`
`the ’355 Patent. Claim 15 in turn depends from independent claim 1 while claim 42 depends from
`
`independent claim 28.
`
`42. However, independent claim 1 recites two different “step of receiving” clauses: “receiving
`
`a series of numerical values having tags indicating characteristics of the numerical values;” and
`
`“receiving a macro defined to perform an operation on the series of numerical values.”
`
`Case No. 19-859C
`
`
`
`DECLARATION OF DAVID MARTIN
`
`

`

`Case 1:19-cv-00859-RTH Document 69-5 Filed 01/21/22 Page 12 of 59
`
`12
`
`
`43. Similarly, independent claim 15 recites “receiving a series of numerical values having tags
`
`indicating characteristics of the numerical values.” and “receiving a macro defined to perform an
`
`operation on the series of numerical values.”
`
`44. For this term, e-Numerate has proposed “In claim 15, the step referred to is ‘receiving a
`
`series of numerical values having tags indicating characteristics of the numerical values’ in claim
`
`1. In claim 42, the step referred to is ‘receiving a series of numerical values having tags indicating
`
`characteristics of the numerical values’ in claim 28.”
`
`45. However, it remains unclear which is the proper antecedent basis for the term “the step of
`
`receiving comprises receiving tags” as recited in claims 15 and 42 as it could refer to either the
`
`first or second “receiving” clause in the relevant independent claim. The first “receiving” clause
`
`makes sense, because a “series of numerical values having tags” could be sensibly supplemented
`
`with tags having further “characteristics selected from the group consisting of: (1) value, (2)
`
`semantics, (3) format, (4) measurement, (5) structure, and (6) provenance.” The second
`
`“receiving” clause also makes sense, because a “macro defined to perform an operation” could be
`
`sensibly supplemented with tags having “characteristics selected from the group consisting of: (1)
`
`value, (2) semantics, (3) format, (4) measurement, (5) structure, and (6) provenance.”
`
`46. In light of the foregoing, in my opinion a person or ordinary skill in the art would be unable
`
`to determine with reasonable certainty the scope of the term “the step of receiving” as recited in
`
`claims 15 and 42 of the ’355 Patent and therefore this term is indefinite.
`
`VII. Terms from the ’816 Patent
`
`A. “markup language” (claim 12 of the ’816 Patent)
`
`47. The term “markup language” appears in claim 12 of the ’816 Patent. Claim 12 depends
`
`from independent claim 10.
`
`48. For this term, e-Numerate has proposed “Not indefinite. Antecedent basis is implied, inter
`
`alia, by the use of the term ‘markup document’ in claim 10. No additional construction of ‘markup
`
`language’ is needed. To the extent ‘markup language’ is construed, it should be construed as
`
`Plaintiffs propose for the ’337 patent. The Defendant is referred to that construction.” The
`
`proposed construction of “markup language” being referred to in claim 1 of the ’337 Patent is “A
`
`markup language is a computer language that uses tags to define elements within a document. It is
`
`Case No. 19-859C
`
`
`
`DECLARATION OF DAVID MARTIN
`
`

`

`Case 1:19-cv-00859-RTH Document 69-5 Filed 01/21/22 Page 13 of 59
`
`13
`
`
`human-readable, meaning markup files contain standard words, rather than typical programming
`
`syntax. Examples of markup languages include HTML, XML and XBRL.”
`
`49. Firstly, a person of ordinary skill in the art would dispute e-Numerate’s contention that a
`
`markup language is differentiated from other languages by being “human-readable” and by its use
`
`of “standard words, rather than typical programming syntax.” This statement is imprecise as it is
`
`unclear as to what are “standard” words and what is “typical” syntax. Furthermore, for a person
`
`of ordinary skill in the art, all of typical programming syntax is “human-readable.” Computer
`
`programming languages are designed to be read and written by human beings while being
`
`structured in a way that permits computers to read them as well.
`
`50. Secondly, the term “markup language” does not appear in claim 10. It also does not appear
`
`in claim 12 prior to the first time it is listed as “the markup language.” Accordingly, there is an
`
`improper antecedent basis issue.
`
`51. Additionally, even if one were to presume that either the “first markup document” or the
`
`“second markup document” recited in claim 1 of the ’816 Patent was composed using a markup
`
`language, it is

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

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.

throbber

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.

Become a Member

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

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket