throbber
Case 5:18-md-02834-BLF Document 406-12 Filed 04/12/19 Page 1 of 5
`Case 5:18—md-02834-BLF Document 406-12 Filed 04/12/19 Page 1 of 5
`
`
`
`
`
`
`
`EXHIBIT 9
`EXHIBIT 9
`
`

`

`Case 5:18-md-02834-BLF Document 406-12 Filed 04/12/19 Page 2 of 5
`_
`E...LEI
`DDL
`LG.NE
`Q:L
`(Uml
`
`7GB USHEiLiIJEI H581
`
`71.1....3....
`
`MEREWM“
`WE.EE
`
`3.5.11.3
`
`MMMV
`
`....
`
`31%MMMMM
`
`Provided by IHS under license with IEEE
`
`
`
`
`
`MMMM..,MM..MMMMM.MMM.MMM.MAM...MM-.-M..M.M.MMM..MMMMMMMMMMMMMMMMMMMMMWMMMMMMMMM
`
`
`
`
`
`
`
`
`
`
`
`
`.§.>..§...r1w1w..fl.r3.3.1........i.......HL131.111.111.99.4.(133.41........1.1....5w....-.1.L1fi323=3§ELB1JPk§F.Wa:..1.fi...1§k11a1§§vq¥rp§fl>£h1113143.1Ew2154yxiiEJi$5..........nmfiakafifixn
`
`
`
`
`
`
`
`
`v1:......Ekrarez..............1...L4L...1.....M..1.!...51.1§4..i.11ur.iu..l1¢<r...1.1..x......rwe.\v1k.un..m.k$.l~..mm.s¥§fifl§i1im1:uh.zr’lva....iurgfl....ftln.!n€21.....E.«.4.14.15.in:..t.\.r.n§~...\w..EarthlrklhtlePwm:1..
`
`
`
`
`
`
`
`cw.....v...3.1.M1vtfial11uqJdeflfiuét.“1.11.3.....111.....,..1........S.Jh1)¢..4..z:...2......s?»§.&§§2?§k§?§.army-1x!.....“.....M5...:.1....>1.H.H1.5......1J&\..5.34.13.1nb5111...uv.35.
`
`
`
`
`
`
`..I.........1.15523...{11.1.3..f....;...a.13...a.....~..11t.fl....€nr3.11:3..6...n}agé§a...skgu{kiiwfi5A....flr.........1.51.33:"1.311.“;
`
`
`
`
`M.....MMM_.M.MMMMMM.MM,..MM.MMMM...MMMMMM1M.MMMMM..MM.M._.......”....MMMMMMMMMMMMZMMM.
`
`
`
`MM
`
`Copyright The Institute of Electrical and Electronics Engineers, Inc.
`No reproduction or networking permitted without license from IHS
`
`Sold to:SUSMAN GODFREY LLP, 01695146
`Not for Resale.2008l4/21 15:0:28 GMT
`
`

`

`Case 5:18-md-02834-BLF Document 406-12 Filed 04/12/19 Page 3 of 5
`Case 5:18—md-02834-BLF Document 406-12 Filed 04/12/19 Page30f5
`STD-IEEE lUU-ENGL Last. I nansma nsuauga am I
`
`IEEE Std 100-1996
`
`The IEEE Standard Dictionary of
`Electrical and Electronics Terms
`
`Sixth Edition
`
`Standards Coordinating Committee 10, Terms and Definitions
`Jane Radatz, Chair
`
`This standard is one of a number of information technology dictionaries being developed by standards
`organizations accredited by the American National Standards Institute. This dictionary was developed
`under the sponsorship of voluntary standards organizations, using a consensus-based process.
`
`ISBN 1-55937-533-5
`
`CopyrightTheInstituteofElectricalandElectronicsEngineers,Inc.
`
`Provided by IHS under license with IEEE
`No reproduction or networking permitted without license from IHS
`
`“‘ll
`
`9 7 81 5 5 9 378338
`
`“
`
`i|”
`
`Sold to:SUSMAN GODFREY LLP, 01695146
`Not for Resale,2008l4/21 15:0:28 GMT
`
`

`

`Case 5:18-md-02834-BLF Document 406-12 Filed 04/12/19 Page 4 of 5
`Case 5:18—md-02834-BLF Document 406-12 Filed 04/12/19 Page4of5
`
`STD-IEEE LUD-ENGL 11‘1“": - HEDS'MIE DSH‘l'HIJ DUI: -
`
`Introduction
`
`Since the first edition in 1941 of the American Standard Definitions of Electrical Terms, the work now
`known as IEEE Std 100, The IEEE Standard Dictionary of Electrical and Electronics Terms, has evolved
`into the unique compendium of terms that it is today.
`
`The current edition includes all terms defined in approved IEEE standards through December 1996. Terms
`are categorized by their technical subject area. They are also associated with the standards or publications
`in which they currently appear. In some cases, terms from withdrawn standards are included when no
`current source can be found. Earlier editions of IEEE Std 100 included terms from sources other than
`
`IEEE standards, such as technical journals, books, or conference proceedings. These terms have been
`maintained for the sake of consistency and their sources are listed with the standards in the back of the
`book.
`
`The practice of defining terms varies from standard to standard. Many working groups that write standards
`prefer to work with existing definitions, while others choose to write their own. Thus terms may have
`several similar, although not identical, definitions. Definitions have been combined wherever it has been
`possible to do so by making only minor editorial changes. Otherwise, they have been left as written in
`the original standard.
`
`Users of IEEE Std 100 occasionally comment on the surprising omission of a particular term commonly
`used in an electrical or electronics field. This occurs because the terms in IEEE Std 100 represent only
`those defined in the existing or past body of IEEE standards. To respond to this, some working groups
`obtain authorization to create a glossary of terms used in their field. All existing, approved standard
`glossaries have been incorporated into this edition of IEEE Std 100, including the most current glossaries
`of terms for computers and power engineering.
`
`IEEE working groups are encouraged to refer to IEEE Std 100 when developing new or revised standards
`to avoid redundancy. They are also encouraged to investigate deficiencies in standard terms and create
`Standard glossaries to alleviate them.
`
`The sponsoring body for this document was Standards Coordinating Committee 10 on Definitions
`(SCClO), which consisted of the following members:
`
`John W. Balde
`Arthur Ballato
`Bruce Barrow
`William Carey
`Frank A. Denbrock
`Jay Forster
`
`Jane Radatz, Chair
`
`Chris Heegard
`John Horch
`J. L. Koepfinger
`Allen H. Meitzler
`Frank D. Myers
`David E. Roberts
`
`F. A. Saal
`Ralph M. Showers
`Edward N. Skomal
`Kenneth L. Swinth
`Raymond S. Turgel
`Edward F. Vance
`
`Copyright The Institute of Electrical and Electronics Engineers, Inc.
`Provided by IHS under license with IEEE
`No reproduction or networking permitted without license from IHS
`
`Sold to:SUSMAN GODFREY LLP, 01695146
`Not for Resale.2008l4/21 15:0:28 GMT
`
`

`

`Case 5:18-md-02834-BLF Document 406-12 Filed 04/12/19 Page 5 of 5
`Case 5:18—md-02834-BLF Document 406-12 Filed 04/12/19 Page 5 of 5
`
`STD-IEEE lDU-ENGL L‘l‘ll: - l-lr'!il35?[lE USH‘i'r‘Eb 7H]. -
`
`data abstraction
`
`251
`
`data bit
`
`logical data; null data; numeric data;
`See also: data type;
`pointer data. (B) (data management) (software) Anything
`observed in the documentation or operation of software that
`deviates from expectations based on previously verified soft-
`ware products or reference documents. Synonym: documen-
`tation.
`(C) 610.12-1990, 6105-1990
`data abstraction (A) (software) The process of extracting
`the essential characteristics of data by defining data types
`and their associated functional characteristics and disregard-
`ing representation details. See also: encapsulation; informa-
`tion hiding. (B) (software) The result of the process in defini-
`tion (A).
`(C) 610.12-1990
`data-access operation A processor-initiated load, store, or lock
`that involves a data-format copy and (for lock operations) a
`data-update action (such as swap or add).
`(C/MM) 15965-1993
`data access register A register that is used for arithmetic as-
`sociated with random-access of data.
`(C) 610.10-1994
`data acquisition (station control and data acquisition) (su-
`pervisory control, data acquisition, and automatic con-
`trol) The collection of data.
`(PE/SWG/SUB) 999-1992, C37.l-1994, C37.100-1992
`data acquisition system (1) (station control and data acqui-
`sition) (supervisory control, data acquisition, and auto-
`matic control) A system that receives data from one or
`more locations. See also: telemetering.
`(PE/SUB) C37.l-1994
`(2) A cenu'alized system that receives data from one or more
`remote points—a telemetering system. Data may be trans-
`ported by either analog or digital telemetering.
`(PE/SWG) C37.lOO-1992
`data administrator An individual who is responsible for the
`definition, organization, supervision, and protection of data
`within some organization. See also: database administrator.
`(C) 6105-1990
`data aggregate A collection of two or more data items that are
`treated as a unit. Synonyms: aggregate; group item. See also:
`composite data element.
`(C) 6105—1990
`data attribute A characteristic of a unit of data.
`(C) 6105-1990
`data bank (A) A collection of data libraries. Note: A record
`contains one or more items, a file contains one or more re-
`cords, a library contains one or more files, and a data bank
`contains one or more libraries. (B) A collection of data relat-
`ing to a particular subject area. Note: The data may or may
`not be machine-readable.
`(C) 6105-1990
`database (1) (A) (data management) (software) A collection
`of logically related data stored together in one or more com-
`puterized files. Note: Each data item is identified by one or
`more keys. See also: database management system. (B) (data
`management) (software) In CODASYL, the collection of all
`the record occurrences, set occurrences, and areas controlled
`by a specific schema.
`(C) 6105—1990
`(2) A collection of data fundamental to a system.
`(C/SE) 1074-1995
`(3) A collection of related data stored in one or more com-
`puterized files in a manner that can be accessed by users or
`computer programs via a database management system.
`(C/ SE)
`J—STD-016—199S
`database access method A technique for organizing and storing
`a physical database in computer storage.
`(C) 6105-1990
`database administration (DBA) The responsibility for the def-
`inition, operation, protection, performance, and recovery of a
`database.
`(C) 6105-1990
`database administrator (DBA) An individual who is respon-
`sible for the definition, operation, protection, performance,
`and recovery of a database. See also: data administrator.
`(C) 6105-1990
`database command language (DBCL) A procedural data ma-
`nipulation language used to access a database through a da-
`tabase management system. See also: database manipulation
`Copyright The Institute of Electrical and Electronics Engineers, Inc.
`(C) 6105-199.)
`Provided by IHS under license with IEEE
`No reproduction or networking permitted without license from IHS
`
`database creation The process of naming, allocating space, for-
`matting, and defining a database. See also: database defini-
`tion; database design.
`(C) 6105—1990
`database definition (A) The process of translating a conceptual
`schema for a database into a data storage schema. See also:
`database creation; database design; redefinition. (B) The re-
`sult of such a translation.
`(C) 6105-1990
`database description language See: data definition language.
`database design (A) The process of developing a conceptual
`schema for a database that will meet a user’s requirements.
`Synonym:
`implementation design. See also: database cre-
`ation; database definition. (B) The result of the process in
`definition (A).
`(C) 610.5-1990
`database engine A software engine that is specially designed
`for database applications; performs low—level database oper-
`ations such as record creation, editing, and deletion. See also:
`relational engine.
`(C) 610.10—1994
`database extract A file, each record of which contains data
`items selected from a database based on a particular criterion.
`(C) 6105-1990
`database integrity The degree to which the data in a database
`are current, consistent and accurate. See also: data integrity;
`database security; integrity.
`(C) 610.5-1990
`database key A field in a database that identifies a record in
`that database.
`(C) 610.5-1990
`database management system (DBMS) (1) A computer system
`involving hardware, software, or both that provides a system-
`atic approach to creating, storing, retrieving and processing
`information stored in a database. A DBMS acts as an interface
`between computers’ programs and data files as well as be-
`tween users and the database. It may include backup/recov—
`ery, checkpoint processing, and ad—hoc query capability.
`(C) 6105-1990
`(2) An integrated set of computer programs that provide the
`capabilities needed to establish, modify, make available, and
`maintain the integrity of a database.
`J-STD-016-1995
`(C/ SE)
`database manipulation language See: data manipulation lan-
`guage.
`database organization The manner in which a database is
`structured; for example, a hierarchical organization, a rela-
`tional organization. See also: reorganization.
`(C) 6105-1990
`database record (A) A collection of data elements that are
`stored in a database. See also: record. (B) A collection of
`hierarchically dependent segments (one root and all its de-
`scendants) within a hierarchical database. See also: record.
`(C) 610.5-1990
`
`database reorganization See: reorganization.
`database security The degree to which a database is protected
`from exposure to accidental or malicious alteration or destruc-
`tion. See also: data security; database integrity.
`(C) 6105—1990
`
`database segment See: segment.
`database server On a network, a server that provides access to
`a database at the record level; that is, the server sends and
`locks only the records affected by a particular requester. See
`also: disk server; file server; mail server; network server; print
`server; terminal server.
`(C) 610.7-1995
`database sublanguage See: data sublanguage.
`database system A software system that supports multiple
`applications using a common database.
`(C) 6105-1990
`Database Task Group (DBTG) A task group of the CODA-
`SYL Programming Language Committee that established a
`set of standards for specification and design of network da-
`tabase structures. See aIso: CODASYL database.
`_
`,,
`(C) 6105-1990
`data bit (1') A single entity of information that is transmitted
`acrosg r aerial cianallino marlin A hit assumes one of [WO
`Sold tOESUSMAN GODFREY LLP, 01695146
`Not for Resale.2008l4/21 15:0:28 GMT
`
`

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