`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 1 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`
`
`EXHIBIT S
`
`
`
`
`
`
`
`
`
`
`Page 1
`
`

`

`
`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 2 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`
`The following claim charts are preliminary in nature. e-Numerate reserves the right to amend and supplement these charts as discovery
`proceeds.
`
`1. An apparatus, comprising:
`
` device; and
`
` a
`
`
`an application including a network browser on the device for accessing a system configured for:
`
`identification of at least one computer-readable Extensible Markup Language (XML)-compliant data document including:
`
` a
`
` a
`
` plurality of line items with a plurality of data values, and
`
` computer-readable datatype rule for validation of a type of data values,
`
` computer-readable calculation rule for validation of a calculation involving data values, and
`
` a
`
` a
`
` a
`
` computer-readable unit rule for validation of a unit of data values;
`
`
`validation of the at least one computer-readable XML-compliant data document by:
`
`identifying at least a subset of the computer-readable rules including at least one of:
`
`the computer-readable datatype rule for validation of the type of data values,
`
`
`
`
`
`
`Page 2
`
` plurality of 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, where the at least one computer-readable XML-compliant data
`document is capable of including multiple hierarchical relationships between two line items;
`
`parsing of the at least one computer-readable XML-compliant data document;
`
`accessing a plurality of computer-readable rules including:
`
`

`

`
`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 3 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`the computer-readable calculation rule for validation of the calculation involving data values, or
`
`the computer-readable unit rule for validation of the unit of data values;
`
`
`processing at least a portion of the data values of at least a portion of the line items of the at least one computer-readable XML-
`compliant data document, utilizing the at least subset of the computer-readable rules and at least a portion of the computer-readable
`sematic tags of the at least one computer-readable XML-compliant data document;
`
`said apparatus configured for:
`
`accessing at least a portion of the at least one computer-readable XML-compliant data document utilizing the application including
`the network browser.
`
`
`
`Page 3
`
`
`
`
`
`
`
`
`
`
`
`

`

`
`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 4 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`Applicability
`Users of an XBRL validator use an apparatus, comprising: a device; and an application including
`a network browser on the device for accessing a system. See excerpt(s) below, for example
`(emphasis added):
`
`Note: Any entity using XBRL on an official basis requires use of an XBRL validator to ensure that
`an XBRL document complies with relevant rules set forth by the XBRL standard.
`
`Upon information and belief, the Federal Energy Regulatory Commission (FERC) and/or
`Department of Energy (DOE) validate XBRL filings made to those organizations and infringe
`at least claim 1 of the ‘748 patent in violation of 35 U.S.C. § 271(a) by using the patented
`invention to, inter alia, process multiple XBRL-compliant filings. See pertinent excerpt(s)
`below illustrating applicability to the FERC/DOE Taxonomy Architecture, for example:
`https://xbrl.us/home/filers/ferc-reporting/tools/.
`
`“The FERC Taxonomy Architecture follows rules defined by XBRL International
`specifications and best practices established by XBRL US domain steering committee.
`Adherence to these recommendations ensures that taxonomies using the Architecture are
`fully XBRL 2.1 compliant.”
`
`“Rendering Templates
`
`Because the data collected by FERC has been historically forms based, the taxonomy
`structure reflects the structure of the Forms. The taxonomy includes html templates for each
`schedule that can be processed with an XBRL instance file and taxonomy entry point to
`render a representation of the form. The templates will render an XHTML version of the
`instance in an inline XBRL format. The rendering templates are defined as labels in the
`taxonomy and are defined as labels of the Schedule abstract element that is at the
`presentation root of every schedule.
`
`Validations
`The taxonomy includes validations to ensure the quality of data submitted. The validations
`are grouped by form and schedule, with sets of validations that are applicable to a given
`
`
`
`Claim 1 Elements
`1. An apparatus, comprising:
`
` a
`
` device; and
`
`
`an application including a
`network browser on the device
`for accessing a system
`configured for:
`
`
`
`
`
`Page 4
`
`

`

`
`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 5 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`form. Validations defined for one schedule will also run on other schedules where the data
`is the same. All validations are expressed using the XULE syntax.”
`
`“3.9 Validations
`
`The taxonomy includes validations represented as rules. A filing should validate against
`these rules to be successfully filed. Each form has a set of validation rules applicable to it.
`In addition, there are validation rules that apply to all forms. These are organized so that
`validation rules do not need to be duplicated by the taxonomy manager.
`
`The validation rules are expressed as XULE rules and are maintained by the taxonomy
`author.”
`
`“5 Form Rendering
`
`5.1 Overview
`
`When an XBRL filing is made to the FERC one of the functions that needs to be performed
`is to create a human readable version of the XBRL instance that looks like a traditional
`form. The following figure shows the process flow of a filing and where form rendering
`occurs:
`
`
`
`
`
`Page 5
`
`

`

`
`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 6 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`
`
`...
`The technology used to render the forms relies on the XULE language to express how data
`from the taxonomy and the instance should be meshed together to create a rendering of
`the form.
`
`The resulting form is rendered in an xhtml format as an inline XBRL document. This makes
`the FERC filing program similar to programs adopted by the US Securities and Exchange
`Commission (SEC) and other global regulators. It also has the advantage that many of the
`FERC filers will be familiar with this approach as they already file in inline XBRL to the SEC.
`
`Because the document is in an xhtml format, formatted text can be included in the filing in
`an xhtml and will be rendered consistently.“
`https://www.ferc.gov/sites/default/files/2020-05/FERC_Taxonomy_Guide.pdf
`
`
`Users of an XBRL validator use an application… configured for: identification of at least one
`computer-readable Extensible Markup Language (XML)-compliant data document including: a
`
`Page 6
`
`identification of at least one
`computer-readable Extensible
`
`
`
`
`

`

`
`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 7 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`plurality of line items with a plurality of data values, and a plurality of 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, where the at least one computer- readable
`XML-compliant data document is capable of including multiple hierarchical relationships between
`two line items. See excerpt(s) below, for example (emphasis added):
`
`Note: As set forth below, XBRL documents are required by the XBRL standard to be XML-
`compliant and include a plurality of line items with a plurality of data values, and a plurality of
`computer-readable semantic tags.
`
`“In XBRL terminology, a concept is a definition of a reporting term. Concepts manifest as XML
`
`Schema [SCHEMA‑1] element definitions. In the taxonomy schema a concept is given a concrete
`
`name and a type. The type defines the kind of data types allowed for facts measured according
`to the concept definition. For example, a “cash” concept would typically have a monetary type.
`This declares that when cash is reported, its value will be monetary. In contrast, a
`“accountingPoliciesNote” concept would typically have a string type so that, when the
`“accountingPoliciesNote” is reported in an XBRL instance, its value would be interpreted as a
`string of characters. Additional constraints on how concepts can be used are documented by
`
`additional XBRL attributes on the XML Schema [SCHEMA‑1] element definitions that correspond
`
`to the concepts…The linkbases in a taxonomy further document the meaning of the concepts by
`expressing relationships between concepts (inter-concept relationships) and by relating concepts
`to their documentation.”
`http://www.xbrl.org/Specification/xbrl-recommendation-2003-12-31+corrected-errata-2012-01-
`25.htm#_Toc202578211
`
`“The core XBRL specifications (see XBRL Essentials) define validation constraints which XBRL
`processors must impose on all XBRL reports. These enforce not only basic syntactical checks, but
`also ensure that the reports comply with the definitions in the taxonomy.”
`http://specifications.xbrl.org/validation.html
`
`Note: As set forth below, XBRL documents are required by the XBRL standard to be XML-
`compliant and be capable of including multiple hierarchical relationships between two line items.
`
`
`Markup Language (XML)-
`compliant data document
`including:
`
` a
`
` plurality of line items with a
`plurality of data values, and
`
` a
`
` plurality of 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,
`where the at least one
`computer- readable XML-
`compliant data document is
`capable of including multiple
`hierarchical relationships
`between two line items;
`
`
`
`
`
`Page 7
`
`

`

`
`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 8 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`
`
`
`
`
`http://www.exkss.com/devel/huHU/tankonyv/attachments/XBRL_For_Dummies.pdf
`
`“From a technical perspective, XBRL implements XML, but also encapsulates other WC3
`standards to enable features important to business reporting—like multiple relationships (both
`hierarchical and non-hierarchical) and extensibility—that are not available in native XML. The
`XBRL specification defines how to create documents containing your data in well-formed XML
`(called instance documents) and how to create files containing relevant business terminology,
`their meanings, their data types, relationships among terms, and the rules/formulas they must
`follow (called taxonomies).”
`http://www.xbrl.org/bpboarddocs/xbrlorcustomizedxml.pdf
`
`Users of an XBRL validator use an application… configured for: parsing of the at least one
`computer-readable XML- compliant data document. See excerpt(s) below, for example (emphasis
`added):
`
`
`parsing of the at least one
`computer-readable XML-
`compliant data document;
`
`
`
`
`
`
`http://www.exkss.com/devel/huHU/tankonyv/attachments/XBRL_For_Dummies.pdf
`
`“XBRL can express multiple hierarchies of explicit relations. Because XBRL separates concept and
`
`Page 8
`
`

`

`
`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 9 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`relation definitions, you can define more than one hierarchy of such relations.”
`http://www.exkss.com/devel/huHU/tankonyv/attachments/XBRL_For_Dummies.pdf
`
`Users of an XBRL validator use an application… configured for: accessing a plurality of computer-
`readable rules including: a computer-readable datatype rule for validation of a type of data
`values, a computer-readable calculation rule for validation of a calculation involving data
`values, and a computer-readable unit rule for validation of a unit of data values. See excerpt(s)
`below, for example (emphasis added):
`
`Note: As set forth below, a computer-readable datatype rule is required for validation of a type
`of data values.
`
`“The core XBRL specifications (see XBRL Essentials) define validation constraints which XBRL
`processors must impose on all XBRL reports. These enforce not only basic syntactical checks, but
`also ensure that the reports comply with the definitions in the taxonomy.”
`https://specifications.xbrl.org/validation.html
`
`“Datatypes
`All XBRL concept definitions are associated with a datatype that enforces basic validation of the
`format of reported values. For example, ensuring that strings are not reported against concepts
`which should take numeric values. At a technical level, XBRL reuses the XML Schema datatype
`system. The standard defines a wide range of base datatypes, but the Data Type Registry 1.0
`allows for the collaborative development, rapid review, publication and on-going use of
`additional specialised data constraints.”
`http://specifications.xbrl.org/validation.html
`
`Note: As set forth below, a computer-readable calculation rule is required for validation of a
`calculation involving data values.
`
`“Calculations
`Taxonomies can capture basic summation relationships between concepts which will be checked
`during the validation process. As the scope of calculations that can be defined in this way is
`limited, many implementations choose to use Formula for all calculation constraints.”
`http://specifications.xbrl.org/validation.html
`
`accessing a plurality of
`computer- readable rules
`including:
`
` a
`
` computer-readable
`datatype rule for validation of
`a type of data values,
`
` a
`
` computer-readable
`calculation rule for validation
`of a calculation involving data
`values, and
`
` a
`
` computer-readable unit
`rule for validation of a unit of
`data values;
`
`
`
`
`
`Page 9
`
`

`

`
`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 10 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`
`Note: As set forth below, a computer-readable unit rule is required for validation of a unit of
`data values.
`
`“Units
`The XBRL 2.1 specification requires that facts for concepts with a monetary datatype use
`particular units based on the ISO 4217 currency code standard. More general constraints
`between datatypes and units can be defined in the Units Registry 1.0.”
`http://specifications.xbrl.org/validation.html
`
`“Validation
`Data quality can be greatly enhanced through multiple layers of validation. The XBRL standard
`provides the ability to design and publish business validation rules in a standardised format.
`Basic validation semantics can be represented in XBRL taxonomies using the core specifications.
`More complex constraints can be modelled using the Formula Specifications. These validation
`rules can be applied at the time of preparation of a report, as well as by all of the recipients of
`that report.”
`http://specifications.xbrl.org/spec-group-index-formula.html
`
`“the monetary type serves as the datatype for those financial concepts in a taxonomy which
`denote units in a currency. Instance items with this type must have a unit of measure from the
`ISO 4217 namespace of currencies.”
`http://www.xbrl.org/Specification/XBRL-2.1/REC-2003-12-31/XBRL-2.1-REC-2003-12-
`31+corrected-errata-2013-02-20.html#unit
`
`
`validation of the at least one
`computer-readable XML-
`
`
`
`
`
`http://www.exkss.com/devel/huHU/tankonyv/attachments/XBRL_For_Dummies.pdf
`Users of an XBRL validator use an application… configured for: validation of the at least one
`computer-readable XML- compliant data document by: identifying at least a subset of the
`
`Page 10
`
`

`

`
`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 11 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`compliant data document by:
`
`identifying at least a subset of
`the computer-readable rules
`including at least one of:
`
`the computer-readable
`datatype rule for validation of
`the type of data values,
`
`the computer-readable
`calculation rule for validation
`of the calculation involving
`data values, or
`
`the computer-readable unit
`rule for validation of the unit
`of data values;
`
`computer-readable rules including at least one of: the computer-readable datatype rule for
`validation of the type of data values, the computer-readable calculation rule for validation of the
`calculation involving data values, or the computer-readable unit rule for validation of the unit of
`data values. See excerpt(s) below, for example (emphasis added):
`
`“The XBRL conformance suite has over 400 tests, each which an XBRL processor must "pass" an
`property interpret XBRL functionality specified in the XBRL specification.”
`http://frux.wikispaces.com/file/view/Chapter-18-Extracting.pdf
`
`“The core XBRL specifications (see XBRL Essentials) define validation constraints which XBRL
`processors must impose on all XBRL reports. These enforce not only basic syntactical checks, but
`also ensure that the reports comply with the definitions in the taxonomy.”
`http://specifications.xbrl.org/validation.html
`
`“Datatypes
`All XBRL concept definitions are associated with a datatype that enforces basic validation of the
`format of reported values. For example, ensuring that strings are not reported against concepts
`which should take numeric values. At a technical level, XBRL reuses the XML Schema datatype
`system. The standard defines a wide range of base datatypes, but the Data Type Registry 1.0
`allows for the collaborative development, rapid review, publication and on-going use of
`additional specialised data constraints.
`…
`Calculations
`Taxonomies can capture basic summation relationships between concepts which will be checked
`during the validation process. As the scope of calculations that can be defined in this way is
`limited, many implementations choose to use Formula for all calculation constraints.
`Units
`The XBRL 2.1 specification requires that facts for concepts with a monetary datatype use
`particular units based on the ISO 4217 currency code standard. More general constraints
`between datatypes and units can be defined in the Units Registry 1.0.”
`http://specifications.xbrl.org/validation.html
`
`
`
`
`
`
`Page 11
`
`

`

`
`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 12 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`
`
`
`
`
`
`Page 12
`
`

`

`
`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 13 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`
`
`
`
`
`
`
`
`Page 13
`
`

`

`
`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 14 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`processing at least a portion
`of the data values of at least
`a portion of the line items of
`the at least one computer-
`readable XML-compliant data
`document, utilizing the at
`least subset of the computer-
`readable rules and at least a
`portion of the computer-
`readable sematic tags of the
`at least one computer-
`readable XML-compliant data
`document;
`
`http://www.exkss.com/devel/huHU/tankonyv/attachments/XBRL_For_Dummies.pdf
`
`Users of an XBRL validator use an application… configured for: processing at least a portion of
`the data values of at least a portion of the line items of the at least one computer-readable XML-
`compliant data document, utilizing the at least subset of the computer-readable rules and at
`least a portion of the computer- readable sematic tags of the at least one computer-readable
`XML-compliant data document. See excerpt(s) below, for example (emphasis added):
`
`“The XBRL conformance suite has over 400 tests, each which an XBRL processor must "pass" an
`property interpret XBRL functionality specified in the XBRL specification.”
`http://frux.wikispaces.com/file/view/Chapter-18-Extracting.pdf
`
`“The core XBRL specifications (see XBRL Essentials) define validation constraints which XBRL
`processors must impose on all XBRL reports. These enforce not only basic syntactical checks, but
`also ensure that the reports comply with the definitions in the taxonomy.”
`http://specifications.xbrl.org/validation.html
`
`“Datatypes
`All XBRL concept definitions are associated with a datatype that enforces basic validation of the
`format of reported values. For example, ensuring that strings are not reported against concepts
`which should take numeric values. At a technical level, XBRL reuses the XML Schema datatype
`system. The standard defines a wide range of base datatypes, but the Data Type Registry 1.0
`allows for the collaborative development, rapid review, publication and on-going use of
`additional specialised data constraints.
`…
`Calculations
`Taxonomies can capture basic summation relationships between concepts which will be checked
`during the validation process. As the scope of calculations that can be defined in this way is
`limited, many implementations choose to use Formula for all calculation constraints.
`Units
`The XBRL 2.1 specification requires that facts for concepts with a monetary datatype use
`particular units based on the ISO 4217 currency code standard. More general constraints
`between datatypes and units can be defined in the Units Registry 1.0.”
`http://specifications.xbrl.org/validation.html
`
`
`
`
`
`Page 14
`
`

`

`
`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 15 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`
`
`
`
`
`
`
`
`Page 15
`
`

`

`
`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 16 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`
`
`
`
`
`
`
`
`Page 16
`
`

`

`
`Case 1:19-cv-00859-RTH Document 53-19 Filed 04/27/21 Page 17 of 17
`
`Claim Charts for U.S. Patent 9,268,748
`
`http://www.exkss.com/devel/huHU/tankonyv/attachments/XBRL_For_Dummies.pdf
`Users of an XBRL validator use an apparatus configured for: accessing at least a portion of the at
`least one computer-readable XML-compliant data document utilizing the application including
`the network browser. See excerpt(s) below, for example (emphasis added):
`
`Note: Any entity using XBRL on an official basis requires use of an XBRL validator to ensure that
`an XBRL document complies with relevant rules set forth by the XBRL standard.
`
`
`
`said apparatus configured for:
`
`accessing at least a portion of
`the at least one computer-
`readable XML-compliant data
`document utilizing the
`application including the
`network browser.
`
`Caveat:
`The notes, cited excerpts, and/or portions thereof utilized herein are set forth for illustrative purposes only and are not meant to be limiting
`in any manner. For example, the notes, cited excerpts, and/or color-coded portions thereof may or may not be supplemented or
`substituted with different excerpt(s) of the relevant reference(s), as appropriate. Further, to the extent any error(s) and/or omission(s) exist
`herein, all rights are reserved to correct the same in connection with any subsequent correlations.
`
`
`
`
`
`
`Page 17
`
`