Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 1 of 39
`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 1 of 39
`
`
`
`
`EXHIBIT B
`EXHIBIT B
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 2 of 39
`
`’355 Patent
`
`‘355 Patent - Term 1
`
`Claim Term
`
`series of numerical
`values having tags
`indicating
`characteristics of the
`numerical values
`
`
`Claims
`
`e-Numerate
`Construction
`1, 27, 28 and 54 A set of one or more
`numerical values
`having markup
`language tags wherein
`the markup language
`tags for the one or
`more numerical values
`have more than one
`attribute that explains
`the meaning of the
`numerical values
`
`
`
`
`‘355 Patent - Term 2
`
`Defendant
`Construction
`Plain and ordinary
`meaning
`(incorporating
`Defendant’s
`construction of
`“tag/tags”).
`Defendant maintains
`that the term “tag”
`should be construed
`as “markup language
`tag” and “tags” as
`“markup language
`tags.” Alternatively,
`to the extent the term
`is construed as a
`whole, Defendant
`proposes
`“A set of one or more
`numerical values
`having markup
`language tags wherein
`the markup language
`tags for the one or
`more numerical
`values have one or
`more attributes that
`describe the meaning
`of the one or more
`numerical values.”
`
`Claim Term
`
`Claims
`
`tag/tags
`
`1, 13, 14, 15, 27,
`28, 40, 41, 42, 54
`
`e-Numerate
`Construction
` “Tag” should not be
`construed as a stand-
`alone term because e-
`
`Defendant
`Construction
`“Tag” should be
`construed as “markup
`language tag” and
`
`
`
`1
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 3 of 39
`
`Numerate has
`identified a phrase for
`construction. In
`addition, the claim
`language uses the term
`“tags” in the plural. To
`the extent “tags” is
`construed, e-Numerate
`contends that the term
`“tags” should be
`construed as “markup
`language tags”.
`
`“tags” as “markup
`language tags.”
`Further, a markup
`language is “a language
`that uses tags to define
`elements within a
`document. Examples
`of markup languages
`include HTML, XML
`and XBRL.”
`
`e-Numerate
`Construction
`Interpreted code that
`performs one or more
`well-defined, generally
`limited tasks
`
`Defendant
`Construction
`Short program which
`performs well-defined,
`limited tasks
`
`Defendant
`Construction
`Plain and ordinary
`meaning
`
`e-Numerate
`Construction
`Converting the series
`of one or more
`numerical values and
`one or more of the
`attributes for the
`numerical values into a
`new series of one or
`more numerical values
`and one or more
`attributes that reflects
`the operation
`
`2
`
`
`
`‘355 Patent - Term 3
`
`Claim Term
`
`Claims
`
`macro
`
`
`
`1, 2, 3, 4, 6, 25,
`26, 27, 28, 29, 30,
`31, 33, 52, 53, 54,
`55
`
`‘355 Patent -Term 4
`
`Claim Term
`
`Claims
`
`1, 27, 28 and 54
`
`transform the series
`of numerical values
`into a new
`representation of the
`series of numerical
`values
`
`
`
`
`
`
`
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 4 of 39
`
`‘355 Patent - Term 5
`
`Claim Term
`
`generating at least
`one second title
`corresponding to
`results of the
`operation
`
`
`
`‘355 Patent - Term 6
`
`Claims
`
`1, 28
`
`e-Numerate
`Construction
`Plain and ordinary
`meaning
`
`Defendant
`Construction
`Generating at least one
`second title based on
`the results of the
`operation and the tags
`
`Claim Term
`
`Claims
`
`the step of receiving
`
`15 and 42
`
`
`
`‘355 Patent -Term 7
`
`Claim Term
`
`report
`
`Claims
`
`21
`
`
`
`
`
`Defendant
`Construction
`Indefinite
`
`e-Numerate
`Construction
`Not indefinite. 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.
`
`e-Numerate
`Construction
`Plain and ordinary
`meaning
`
`Defendant
`Construction
`Document generated
`by combining an
`XML-compliant
`document with a
`template.
`
`3
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 5 of 39
`
`‘816 Patent
`
`‘816 Patent -Term 1
`
`Claim Term
`
`Claims
`
`tags reflecting
`characteristics of the
`numerical values
`
`1, 10, 17, 26, 27
`
`e-Numerate
`Construction
`Markup language
`tags wherein the
`markup language tags
`for the one or more
`numerical values
`have more than one
`attribute that explains
`the meaning of the
`numerical values
`
`
`
`
`
`
`
`
`
`
`4
`
`Defendant
`Construction
`Plain and ordinary
`meaning
`(incorporating
`Defendant’s
`construction of
`“tag/tags”) Defendant
`maintains that “tag”
`should be construed
`as “markup language
`tag” and “tags” as
`“markup language
`tags.” Further, a
`markup language is
`“a language that uses
`tags to define
`elements within a
`document. Examples
`of markup languages
`include HTML, XML
`and XBRL.” To the
`extent this term is
`construed, Defendant
`proposes: “Markup
`language tags
`wherein the markup
`language tags for the
`one or more
`numerical values
`have one or more
`attributes that
`describe the meaning
`of the numerical
`values.”
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 6 of 39
`
`e-Numerate
`Construction
`“Tag” should not be
`construed as a stand-
`alone term. e-
`Numerate has
`identified a phrase for
`construction. In
`addition, the claim
`language uses the
`term “tags” in the
`plural. To the extent
`the term “tags” is
`construed, it should
`be construed as
`“markup language
`tags.”
`
`Defendant
`Construction
`“Tag” should be
`construed as “markup
`language tag” and
`“tags” as “markup
`language tags.”
`Further, a markup
`language is a
`“language that uses
`tags to define
`elements within a
`document. Examples
`of markup languages
`include HTML, XML
`and XBRL.”
`
`Defendant
`Construction
`Plain and ordinary
`meaning
`
`e-Numerate
`Construction
`One or more
`attributes for the
`numerical values in
`the first markup
`document are
`different from one or
`more attributes for
`the numerical values
`in the second markup
`document
`
`‘816 Patent – Term 2
`
`Claim Term
`
`Claims
`
`tag/tags
`
`1, 3 – 8, 10, 17 and
`19 – 27
`
`
`
`
`‘816 Patent – Term 3
`
`Claim Term
`
`Claims
`
`1, 10, 17, 26, 27
`
`wherein the
`characteristics
`indicate that the
`numerical values of
`the first markup
`document differ in
`format from the
`numerical values of
`the second markup
`document
`
`
`
`
`
`
`
`
`
`
`5
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 7 of 39
`
`Defendant
`Construction
`Plain and ordinary
`meaning.
`
`‘816 Patent – Term 4
`
`Claim Term
`
`automatically
`transforming/transforms
`the numerical values of
`at least one of the first
`markup document and
`the second markup
`document, so that the
`numerical values of the
`first markup document
`and the second markup
`document have a
`common format
`
`
`Claims
`
`e-Numerate
`Construction
`1, 10, 17, 26 and 27 Automatically
`converting/converts
`at least a portion of
`the first or second
`numerical values and
`one or more
`attributes for the
`numerical values in
`the first or second
`markup document to
`create new numerical
`values and common
`attributes for the
`numerical values
`
`
`
`‘816 Patent – Term 5
`
`Claim Term
`
`Claims
`
`the markup language
`
`12
`
`Claims
`
`26
`
`
`
`‘816 Patent – Term 6
`
`Claim Term
`
`means for receiving a
`first markup
`document and a
`second
`markup document,
`both the first markup
`document and
`
`
`
`Defendant
`Construction
`Indefinite
`
`e-Numerate
`Construction
`Not indefinite.
`Antecedent basis is
`implied, inter alia, by
`the use of the term
`“markup document”
`in claim 10.
`
`e-Numerate
`Construction
`To be construed
`under § 112 par. 6.
`
`Function: receiving a
`first markup
`document and a
`
`Defendant
`Construction
`To be construed
`under § 112 ¶ 6
`
`Function: Receiving a
`first markup
`document and a
`second markup
`
`6
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 8 of 39
`
`the second markup
`document containing
`numerical values
`and tags reflecting
`characteristics of the
`numerical
`values wherein the
`characteristics
`indicate that the
`numerical values of
`the first markup
`document differ in
`format from the
`numerical values of
`the second markup
`document
`
`
`
`
`‘816 Patent – Term 7
`
`Claim Term
`
`means for
`automatically
`transforming the
`numerical values
`of at least one of the
`first markup
`document and the
`second markup
`document, so that the
`numerical values
`of the first markup
`document and the
`second markup
`document have a
`common format
`
`
`
`Claims
`
`26
`
`second markup
`document.
`
`Structure: Reader
`See, e.g., Fig. 7A
`box 704, Fig. 8, step
`802, col. 8, line 4;
`col. 19, lines 30 – 48;
`col. 29, lines 35 – 65;
`col. 30, lines 37 – 45.
`
`document, both the
`first markup
`document and the
`second markup
`document containing
`numerical values and
`tags reflecting
`characteristics of the
`numerical values,
`wherein the
`characteristics
`indicate that the
`numerical values of
`the first markup
`document differ in
`format from the
`numerical values of
`the second markup
`document
`
`Structure:
`Undisclosed
`
`Term is indefinite
`
`e-Numerate
`Construction
`To be construed
`under § 112 par. 6.
`
`Function:
`automatically
`transforming the
`numerical values
`of at least one of the
`first markup
`document and the
`second markup
`document.
`
`Structure: X-value
`transformer
`
`Defendant
`Construction
`To be construed
`under § 112 ¶ 6
`
`Function:
`Automatically
`transforming the
`numerical values of
`at least one of the
`first markup
`document and the
`second markup
`document, so that the
`numerical values of
`the first markup
`document and the
`
`7
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 9 of 39
`
`
`
`
`
`Claims
`
`26
`
`‘816 Patent – Term 8
`
`Claim Term
`
`means for combining
`the first markup
`document and the
`second markup
`document into a
`single data
`
`
`
`
`
`
`
`
`second markup
`document have a
`common format.
`
`Structure:
`Undisclosed
`
`Term is indefinite
`
`Defendant
`Construction
`To be construed
`under § 112 ¶ 6
`
`Function: Indefinite
`
`Structure:
`Undisclosed
`
`Term is indefinite
`
`employing
`conversion factors.
`Fig. 7A block 710;
`Figure 8 block 808;
`Figure 10, blocks
`1012 and 1014;
`Figure 11; col. 19,
`line 49 – col. 20, line
`3; col. 23, lines 47 –
`59; col. 30, line 46 -
`col. 33, line 33; col.
`25, line 45 – col. 27,
`line 45.
`
`
`
`e-Numerate
`Construction
`To be construed
`under § 112 par. 6.
`
`Function: combining
`the first markup
`document and the
`second markup
`document.
`
`Structure: primary
`data store; Fig. 7,
`Box 712; Figure 8,
`line 810; Fig; 11;
`Figure 13; col. 19,
`line 66 – col. 20, line
`3; col. 31, lines 4 –
`30; col. 33, lines 9 –
`59; col. 35, line 50 –
`col. 36, line 40.
`
`8
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 10 of 39
`
`‘816 Patent – Term 9
`
`Claim Term
`
`Claims
`
`means for displaying
`the single data set
`
`26
`
`
`
`‘816 Patent – Term 10
`
`Claim Term
`
`Claims
`
`characteristic of the
`numerical value
`
`27
`
`
`
`‘383 Patent
`
`‘383 Patent – Term 1
`
`Claim Term
`
`first tags reflecting
`characteristics of the
`first numerical values
`
`Claims
`
`1, 17, 18
`
`
`
`Defendant
`Construction
`To be construed
`under § 112 ¶ 6
`
`Function: Displaying
`the single data set
`
`Structure:
`Undisclosed
`
`Term is indefinite
`
`e-Numerate
`Construction
`To be construed
`under § 112 par. 6.
`
`Function: displaying
`the single data set
`
`Structure: graphical
`user interface.
`Fig. 7A block 734;
`Figures 15 A, B & C;
`Fig. 19 B; col. 35,
`line 50 – 63; col. 36,
`line 66 – col. 37, line
`45; col. 48, lines 41 –
`49; col. 53, lines 44 –
`53.
`
`
`e-Numerate
`Construction
`An attribute that
`explains the meaning
`of the numerical
`value
`
`Defendant
`Construction
`Plain and ordinary
`meaning
`
`e-Numerate
`Construction
`Markup language
`tags wherein the
`markup language tags
`for the one or more
`
`Defendant
`Construction
`Plain and ordinary
`(incorporating
`Defendant’s
`construction of
`
`9
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 11 of 39
`
`
`
`
`
`numerical values
`have more than one
`attribute that explains
`the meaning of the
`numerical values
`
`“tag”/”tags”).
`Defendant maintains
`that ”tag” should be
`construed as “markup
`language tag” and
`“tags” should be
`construed as “markup
`language tags.”
`Further, a markup
`language is “a
`language that uses
`tags to define
`elements within a
`document. Examples
`of markup languages
`include HTML, XML
`and XBRL.” To the
`extent the Court
`construes the entire
`term, Defendant
`proposes “Markup
`language tags
`wherein the markup
`language tags for the
`one or more
`numerical values
`have one or more
`attributes that
`describe the meaning
`of the numerical
`values.”
`
`‘383 Patent – Term 2
`
`Claim Term
`
`second tags reflecting
`characteristics of the
`second numerical
`values
`
`
`Claims
`
`1, 17, 18
`
`e-Numerate
`Construction
`Markup language
`tags wherein the
`markup language tags
`for the one or more
`numerical values
`have more than one
`attribute that explains
`
`Defendant
`Construction
`Plain and ordinary
`(incorporating
`Defendant’s
`construction of “tag”
`and “tags”)
`Defendant maintains
`that “tag” should be
`construed as “markup
`
`
`
`10
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 12 of 39
`
`the meaning of the
`numerical values
`
`language tag” and
`“tags” as “markup
`language tags.”
`Further, a markup
`language is “a
`language that uses
`tags to define
`elements within a
`document. Examples
`of markup languages
`include HTML, XML
`and XBRL.” To the
`extent the Court
`construes the entire
`term, Defendant
`proposes “Markup
`language tags
`wherein the markup
`language tags for the
`one or more
`numerical values
`have one or more
`attributes that
`describe the meaning
`of the numerical
`values.”
`
`e-Numerate
`Construction
`“Tag” should not be
`construed as a stand-
`alone term because e-
`Numerate has
`identified a phrase for
`construction. In
`addition, the claim
`language uses the
`term “tags” in the
`plural. To the extent
`“tags” is construed, e-
`Numerate contends
`the term “tags”
`
`Defendant
`Construction
`“Tag” should be
`construed as “markup
`language tag and
`“tags” as “markup
`language tags.”
`Further, a markup
`language is “a
`language that uses
`tags to define
`elements within a
`document. Examples
`of markup languages
`
`
`
`‘383 Patent – Term 3
`
`Claim Term
`
`tag/tags
`
`Claims
`
`1, 4, 17
`
`
`
`11
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 13 of 39
`
`should be construed
`as “Markup language
`tags”.
`
`include HTML, XML
`and XBRL.”
`
`e-Numerate
`Construction
`Markup language
`tags wherein the
`markup language tags
`for the one or more
`numerical values
`have more than one
`attribute that explains
`the meaning of the
`numerical values
`
`Defendant
`Construction
`Plain and ordinary
`(incorporating
`Defendant’s
`constructions of
`“tag/tags” and
`“semantic
`tag/semantic tags”)
`Defendant maintains
`that “tag[s]” and
`“semantic tag[s]”
`should be construed.
`To the extent the
`Court construes the
`term as a whole,
`Defendant proposes
`“Markup language
`tags wherein the
`markup language tags
`for the one or more
`numerical values
`have one or more
`attributes that
`describe the meaning
`of the numerical
`values.”
`
`
`
`Claims
`
`1, 17, 18
`
`
`
`‘383 Patent – Term 4
`
`Claim Term
`
`wherein the first tags
`and the second tags
`each include
`computer-readable
`semantic tags that
`describe a semantic
`meaning of a
`corresponding one of
`at least one of the
`first numerical values
`or the second
`numerical values
`
`
`
`‘383 Patent – Term 5
`
`Claim Term
`
`Claims
`
`semantic
`tag/semantic tags
`
`1, 6-8, 11, 12, 15, 17
`and 18.
`
`e-Numerate
`Construction
`“Semantic tag”
`should not be
`
`Defendant
`Construction
`A “semantic tag”
`should be construed
`
`
`
`12
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 14 of 39
`
`as “markup language
`tag with one or more
`attributes that
`describe the meaning
`of the tagged
`value(s).” and
`“semantic tags”
`should be construed
`as “Markup language
`tags with one or more
`attributes that
`describe the meaning
`of the tagged
`value(s).”
`
`Defendant
`Construction
`Plain and ordinary
`(incorporating the
`parties’ agreed
`construction of
`“markup document”
`as “a document that
`contains markup
`language tags.”)
`
`construed as a stand-
`alone term because e-
`Numerate has
`identified a phrase for
`construction. In
`addition, the claim
`language uses the
`term “semantic tags”
`in the plural. To the
`extent “semantic
`tags” is construed, e-
`Numerate contends
`that the term
`“semantic tags”
`should be construed
`as “markup language
`tags wherein the
`markup language tags
`for the one or more
`numerical values
`have more than one
`attribute that explains
`the meaning of the
`numerical values.”
`
`e-Numerate
`Construction
`Automatically
`converting at least a
`portion of the first or
`second numerical
`values and one or
`more attributes for
`the numerical values
`in the first or second
`markup document to
`create new numerical
`values and common
`attributes reflecting a
`unit of measure for
`the numerical values
`
`13
`
`Claims
`
`1, 17
`
`
`
`‘383 Patent -Term 6
`
`Claim Term
`
`automatic
`transformation of at
`least a portion of the
`first or second
`numerical values of
`at least one of the
`first markup
`document or the
`second markup
`document, so that at
`least some of the first
`numerical values of
`the first markup
`document and at least
`some of the second
`
`
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 15 of 39
`
`markup document
`have a common unit
`of measure
`
`
`
`
`383 Patent – Term 7
`
`Claim Term
`
`Claims
`
`8
`
`capable of including
`at least one of:
`multiple hierarchical
`relationships between
`two line items of
`corresponding
`numerical values; or
`computer- readable
`semantic tags that
`each describe a
`semantic meaning of
`one or more of
`corresponding
`numerical values
`
`
`
`‘383 Patent – Claim 8
`
`Claim Term
`
`rule
`
`Claims
`
`9, 10
`
`e-Numerate
`Construction
`Plaintiffs contend that
`“capable of
`including” should be
`construed as “may
`include.” Plaintiffs
`have previously
`provided their
`constructions for the
`other phrases in this
`claim and incorporate
`those by reference.
`
`Defendant
`Construction
`Defendant maintains
`that “capable of
`including” has its
`plain and ordinary
`meaning of “has the
`ability to include.”
`Defendant has
`provided
`constructions for
`other terms including
`“multiple hierarchical
`relationships between
`two line items of
`corresponding
`numerical values”
`and “semantic tags”
`and incorporates
`those herein. The
`remaining terms
`should be construed
`according to their
`plain and ordinary
`meaning.
`
`e-Numerate
`Construction
`Plain and ordinary
`meaning (i.e., not
`limited to being in the
`Document Type
`Definition (DTD))
`
`Defendant
`Construction
`constraint listed in a
`Document Type
`Definition (DTD)
`
`
`
`14
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 16 of 39
`
`‘383 Patent – Claim 9
`
`Claim Term
`
`presentation
`
`Claims
`
`14
`
`
`
`‘383 Patent – Term 10
`
`Claim Term
`
`report
`
`Claims
`
`14
`
`
`
`‘383 Patent – Term 11
`
`Claim Term
`
`Claims
`
`7, 8 and 15
`
`multiple hierarchical
`relationships between
`two line items of
`corresponding
`numerical values
`
`e-Numerate
`Construction
`Plain and ordinary
`meaning
`
`Defendant
`Construction
`A visualization of the
`object that is
`displayed
`
`e-Numerate
`Construction
`Plain and ordinary
`meaning
`
`Defendant
`Construction
`Document generated
`by combining an
`XML-compliant
`document with a
`template
`
`e-Numerate
`Construction
`As used in claims 7
`and 15, Plaintiffs
`contend that the
`phrase should contain
`the word “includes”
`before “multiple” and
`should be construed
`as “includes a line
`item in various types
`of hierarchical
`relationships with
`other line items. By
`way of example,
`parent-child, siblings,
`grandparent -
`grandchild, etc.”
`Claim 8 uses the term
`“capable of”. e-
`Numerate has
`
`Defendant
`Construction
`“at least two
`relationships between
`two line items of
`corresponding
`numerical values
`where one
`relationship is
`expressed as a parent-
`child relationship
`between the two line
`items and the other is
`based on a common
`ancestor between the
`two line items”
`
`(incorporating above
`construction of “line
`items” )
`
`
`
`15
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 17 of 39
`
`
`
`‘383 Patent – Claim 12
`
`Claim Term
`
`capable of including
`computer- readable
`semantic tags that
`each describe a
`semantic meaning of
`one or more of the
`corresponding values
`
`Claims
`
`15
`
`Claims
`
`18
`
`
`
`‘383 Patent – Term 13
`
`Claim Term
`
`means for identifying
`a first markup
`document including
`first numerical values
`and first tags
`reflecting first
`characteristics
`of the first numerical
`values associated
`with a
`
`
`
`previously provided a
`construction for the
`phrase including
`“capable of.”
`
`e-Numerate
`Construction
`Plaintiffs contend that
`“capable of
`including” should be
`construed as “may
`include.” e-
`Numerate has
`previously provided
`its constructions for
`the other phrases in
`this claim.
`
`Defendant
`Construction
`Defendant maintains
`that “capable of
`including” should
`have its plain and
`ordinary meaning of
`“has the ability to
`include.” Defendant
`previously identified
`a construction for
`“semantic tags” and
`that term should be
`construed. The
`remaining verbiage in
`this term should be
`construed according
`to its plain and
`ordinary meaning.
`
`e-Numerate
`Construction
`To be construed
`under § 112 par. 6.
`
`Function: identifying
`a first markup
`document including
`first numerical values
`and first tags
`reflecting first
`characteristics of the
`first numerical values
`
`Defendant
`Construction
`To be construed
`under § 112 ¶ 6
`
`Function: Identifying
`a first markup
`document including
`first numerical values
`and first tags
`reflecting first
`characteristics of the
`first numerical values
`
`16
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 18 of 39
`
`first unit of measure,
`and a second markup
`document
`including second
`numerical values and
`second tags
`reflecting second
`characteristics of the
`second numerical
`values associated
`with a second unit of
`measure,
`wherein the first tags
`and the second tags
`each include
`computer-readable
`semantic tags that
`describe a semantic
`meaning of a
`corresponding one of
`at least one of the
`first numerical values
`or the second
`numerical values
`via a computer-
`readable tagging
`association
`therebetween, where
`the first
`characteristics of the
`first numerical
`values associated
`with the first unit of
`measure are
`different from the
`second characteristics
`of the second
`numerical values
`associated with the
`second unit of
`measure
`
`
`
`
`
`
`
`
`associated with a first
`unit of measure, and
`a second markup
`document including
`second numerical
`values and second
`tags reflecting second
`characteristics of the
`second numerical
`values associated
`with a second unit of
`measure
`
`Structure: Reader
`See, e.g., Fig. 7A
`box 704, Fig. 8, step
`802; col. 17, line 27 –
`col. 18, line 7; col.
`28, lines 1 – 31; col.
`29, lines 3 – 11.
`
`associated with a first
`unit of measure, and
`a second markup
`document including
`second numerical
`values and second
`tags reflecting second
`characteristics of the
`second numerical
`values associated
`with a second unit of
`measure, wherein the
`first tags and the
`second tags each
`include computer-
`readable semantic
`tags that describe a
`semantic meaning of
`a corresponding one
`of at least one of the
`first numerical values
`or the second
`numerical values, via
`a computer- readable
`tagging association
`therebetween, where
`the first
`characteristics of the
`first numerical values
`associated with the
`first unit of measure
`are different from the
`second characteristics
`of the second
`numerical values
`associated with the
`second unit of
`measure
`
`Structure:
`Undisclosed
`
`Term is indefinite
`
`17
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 19 of 39
`
`Claims
`
`18
`
`‘383 Patent – Term 14
`
`Claim Term
`
`means for
`automatically
`transforming at least
`a portion of
`the first or second
`numerical values of
`at least one of the
`first markup
`document or the
`second markup
`document,
`so that at least some
`of the first numerical
`values of the
`first markup
`document and at least
`some of the second
`numerical values of
`the second markup
`document have a
`common unit of
`measure
`
`
`
`
`‘383 Patent – Term 15
`
`Claims
`
`18
`
`Claim Term
`
`means for processing
`at least a part of the
`first markup
`document and at least
`
`
`
`e-Numerate
`Construction
`To be construed
`under § 112 par. 6.
`
`Function:
`automatically
`transforming at least
`a portion of the first
`or second numerical
`values of at least one
`of the first markup
`document or the
`second markup
`document
`
`Structure: X-value
`transformer
`employing
`conversion factors.
`Fig. 7A block 710;
`Figure 8 block 808;
`Figure 10, blocks
`1012 and 1014;
`Figure 11; col. 18,
`lines 8 – 30; col. 22,
`lines 17 – 29; col. 29,
`line 13 – col. 31, line
`29; col. 24, line 9 –
`col. 26, line 10
`
`
`
`Defendant
`Construction
`To be construed
`under § 112 ¶ 6
`
`Function:
`Automatically
`transforming at least
`a portion of the first
`or second numerical
`values of at least one
`of the first markup
`document or the
`second markup
`document, so that at
`least some of the first
`numerical values of
`the first markup
`document and at least
`some of the second
`numerical values of
`the second markup
`document have a
`common unit of
`measure
`
`Structure:
`Undisclosed
`
`Term is indefinite
`
`e-Numerate
`Construction
`To be construed
`under § 112 par. 6.
`
`Function: processing
`at least a part of the
`
`Defendant
`Construction
`To be construed
`under § 112 ¶ 6
`
`Function: Processing
`at least a part of the
`
`18
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 20 of 39
`
`a part of the second
`markup document,
`resulting in a single
`markup document
`
`
`
`
`‘383 Patent – Term 16
`
`Claim Term
`
`means for causing a
`display of at least a
`portion of the
`single markup
`document
`
`Claims
`
`18
`
`
`
`
`
`first markup
`document and at least
`a part of the second
`markup document,
`resulting in a single
`markup document
`
`Structure:
`Undisclosed
`
`Term is indefinite
`
`Defendant
`Construction
`To be construed
`under § 112 ¶ 6
`
`Function: Causing a
`display of at least a
`portion of the single
`markup document
`
`Structure:
`Undisclosed
`
`Term is indefinite
`
`first markup
`document and at least
`a part of the second
`markup document,
`resulting in a single
`markup document
`
`Structure: primary
`data store;
`Fig. 7, Box 712;
`Figure 8, line 810;
`Fig; 11; Figure 13;
`col. 18, lines 25 – 30;
`col. 29, lines 37 – 63;
`col. 31, line 45 – col.
`32, line 25.
`
`e-Numerate
`Construction
`To be construed
`under § 112 par. 6.
`
`Function: causing a
`display of at least a
`portion of the single
`markup document
`
`Structure: graphical
`user interface.
`Fig. 7A block 734;
`Figs. 14 A – D,
`Figures 15 A, B & C;
`Fig. 16, Fig. 17, Fig.
`19 B; col. 34, line 13
`– 26; col. 35, line 23
`– col. 36, line 7; col.
`46, line 65 – col. 47,
`line 6.
`
`
`
`19
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 21 of 39
`
`‘384 Patent
`
`‘384 Patent – Term 1
`
`Claim Term
`
`values
`
`Claims
`
`66
`
`
`
`‘384 Patent – Term 2
`
`Claim Term
`
`data structure
`
`
`
`Claims
`
`66
`
`
`
`‘384 Patent – Term 3
`
`Claim Term
`
`Claims
`
`66
`
`
`identify one or more
`indications
`for one or more of the
`original values for
`tagging, in
`connection with at
`least one computer-
`readable Extensible
`Markup Language
`(XML)-compliant
`data document, using
`a corresponding one
`or more computer
`readable semantic
`tags
`
`e-Numerate
`Construction
`Plain and ordinary
`meaning
`
`Defendant
`Construction
`Plain and ordinary
`(i.e., not limited to
`numerical values)
`
`Defendant
`Construction
`Plain and ordinary
`meaning
`
`e-Numerate
`Construction
`An organizational
`scheme that can be
`applied to data to
`facilitate interpreting
`the data or
`performing
`operations on it
`
`e-Numerate
`Construction
`Plain and ordinary
`meaning that
`incorporates
`Plaintiffs’ definition
`of “one or more
`computer readable
`semantic tags”
`
`Defendant
`Construction
`Plain and ordinary
`meaning
`(incorporating below
`construction of
`“semantic tags” and
`“tag[ging]”)
`
`
`
`
`20
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 22 of 39
`
`‘384 Patent – Term 4
`
`Claim Term
`
`one or more
`computer readable
`semantic tags
`
`Claims
`
`66
`
`
`
`‘384 Patent – Term 5
`
`Claim Term
`
`semantic
`tag/semantic tags
`
`Claims
`
`66
`
`
`
`
`
`
`
`
`
`e-Numerate
`Construction
`One or more markup
`language tags for one
`or more values that
`have more than one
`attribute that explains
`the meaning of the
`values.
`
`Defendant
`Construction
`Plain and ordinary
`(incorporating
`Defendant’s
`construction of
`“semantic tags”)
`
`Defendant
`Construction
`A “semantic tag”
`should be construed
`as “markup language
`tag with one or more
`attributes that
`describe the meaning
`of the tagged
`value(s)” and
`“semantic tags”
`should be construed
`as “markup language
`tags with one or more
`attributes that
`describe the meaning
`of the tagged
`value(s).”
`
`e-Numerate
`Construction
`The term “semantic-
`tag” should not be
`construed as a stand-
`alone term because
`the claim language
`uses “semantic tags”.
`e-Numerate has
`identified a phrase in
`claim 66 that should
`be construed and has
`provided a
`construction
`therefore. To the
`extent “semantic
`tags” is construed as
`markup language tags
`for one or more
`values that have more
`than one attribute that
`explains the meaning
`of the values.
`
`21
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 23 of 39
`
`‘384 Patent – Term 6
`
`Claim Term
`
`presentation
`
`Claims
`
`66
`
`
`
`‘384 Patent – Term 7
`
`Claim Term
`
`report
`
`Claims
`
`66
`
`
`
`‘748 Patent
`
`‘748 Patent – Term 1
`
`Claim Term
`
`Claims
`
`data values/values
`
`1, 11 and 19
`
`
`
`‘748 Patent – Term 2
`
`Claim Term
`
`computer-readable
`semantic tags that
`describe a semantic
`meaning of the data
`values
`
`
`
`
`e-Numerate
`Construction
`Plain and ordinary
`meaning
`
`Defendant
`Construction
`A visualization of the
`object that is
`displayed
`
`e-Numerate
`Construction
`Plain and ordinary
`meaning
`
`Defendant
`Construction
`Document generated
`by combining an
`XML-compliant
`document with a
`template
`
`e-Numerate
`Construction
` Plain and ordinary
`meaning
`
`Defendant
`Construction
`Plain and ordinary
`(i.e., not limited to
`numerical values)
`
`Claims
`
`1, 11, 19
`
`
`
`
`
`
`e-Numerate
`Construction
`Markup language
`tags for one or more
`data values that have
`more than one
`attribute that explains
`
`Defendant
`Construction
`Plain and ordinary
`(incorporating
`Defendant’s
`construction of
`“semantic tags”
`below)
`
`22
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 24 of 39
`
`computer-readable
`semantic tags that
`describe a semantic
`meaning of the data
`values and are each
`computer-readably
`coupled to at least
`one of the data
`values/computer-
`readable semantic
`tags
`
`
`
`
`
`
`‘748 Patent – Term 3
`
`Claim Term
`
`Claims
`
`semantic
`tag/semantic tags
`
`1 – 5, 11, 14 – 16, 19,
`20
`
`the meaning of the
`data values
`
`
`Defendant
`Construction
`A “semantic tag”
`should be construed
`as a “markup
`language tag with one
`or more attributes
`that describe the
`meaning of the
`tagged value(s)” and
`“semantics tags”
`should be construed
`as “markup language
`tags with one or more
`attributes that
`describe the meaning
`of the tagged
`value(s).”
`
`e-Numerate
`Construction
`“Semantic tag”
`should not be
`construed as a stand-
`alone term. The
`claims use the term
`“semantic tags” in the
`plural. e-Numerate
`has proposed a
`construction of
`phrases including this
`term that should be
`construed. To the
`extent that “semantic
`tags” is construed, it
`should be construed
`as “markup language
`tags for one or more
`values that have more
`than one attribute that
`explains the meaning
`of the values.”
`
`
`
`
`
`
`
`
`
`23
`
`

`

`Case 1:19-cv-00859-RTH Document 80-3 Filed 03/14/22 Page 25 of 39
`
`‘748 Patent – Term 4
`
`Claim Term
`
`Claims
`
`1
`
`capable of including
`multiple hierarchical
`relationships between
`two line items
`
`
`
`‘748 Patent – Term 5
`
`Claim Term
`
`Claims
`
`multiple hierarchical
`relationships between
`two line items
`
`1
`
`e-Numerate
`Construction
`May include a line
`