ISO 8000-2-2017 Data quality - Part 2 Vocabulary《数据质量 第2部分 词汇表》.pdf

1、 ISO 2017 Data quality Part 2: Vocabulary Qualit des donnes Partie 2: Vocabulaire INTERNATIONAL STANDARD ISO 8000-2 Second edition 2017-08 Reference number ISO 8000-2:2017(E) ISO 8000-2:2017(E)ii ISO 2017 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO 2017, Published in Switzerland All rights

2、reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from eithe

3、r ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Ch. de Blandonnet 8 CP 401 CH-1214 Vernier, Geneva, Switzerland Tel. +41 22 749 01 11 Fax +41 22 749 09 47 copyrightiso.org www.iso.org ISO 8000-2:2017(E)Foreword iv Introduction v 1 Scope . 1 2 Norm

4、ative references 1 3 T erms and definitions . 1 3.1 Terms relating to applications . 1 3.2 Terms relating to data and information 2 3.3 Terms relating to quality 3 3.4 Terms relating to data quality 3 3.5 Terms relating to syntax and semantics 5 3.6 Terms related to characteristic data . 5 3.7 Terms

5、 relating to data dictionaries . 6 3.8 Terms relating to transaction data . 6 3.9 Terms relating to measurement data 6 3.10 Terms relating to master data 7 3.11 Terms relating to product data . 7 3.12 Terms relating to items of production and items of supply . 8 3.13 Terms relating to roles . 9 3.14

6、 Terms relating to process assessment .10 Annex A (normative) Document identification 13 Bibliography .14 ISO 2017 All rights reserved iii Contents Page ISO 8000-2:2017(E) Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO me

7、mber bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governme

8、ntal and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. The procedures used to develop this document and those intended for its further maintenanc

9、e are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/ directives). Attent

10、ion is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction

11、and/or on the ISO list of patent declarations received (see www .iso .org/ patents). Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement. For an explanation on the voluntary nature of standards, the meaning of ISO specific ter

12、ms and expressions related to conformity assessment, as well as information about ISOs adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see the following URL: w w w . i s o .org/ iso/ foreword .html. This document was prepared by Technical Committee

13、 ISO/TC 184, Automation systems and integration, Subcommittee SC 4, Industrial data. This second edition cancels and replaces the first edition (ISO 8000-2:2012), which has been technically revised, with the addition and modification of some terms and definitions. ISO 8000 is organized as a series o

14、f parts, each published separately. The structure of ISO 8000 is described in ISO/TS 8000-1. Each part of ISO 8000 is a member of one of the following series: general data quality, master data quality and product data quality. This document is a member of the general data quality series but applicab

15、le to all of the three data quality series. A list of all parts in the ISO 8000 series can be found on the ISO website.iv ISO 2017 All rights reserved ISO 8000-2:2017(E) Introduction The ability to create, collect, store, maintain, transfer, process and present data to support business processes in

16、a timely and cost effective manner requires both an understanding of the characteristics of the data that determine its quality, and an ability to measure, manage and report on data quality. ISO 8000 defines characteristics that can be tested by any organization in the data supply chain to objective

17、ly determine conformance of the data to ISO 8000. ISO 8000 provides frameworks for improving data quality for specific kinds of data. The frameworks can be used independently or in conjunction with quality management systems. ISO 8000 covers industrial data quality characteristics throughout the pro

18、duct life cycle from conception to disposal. ISO 8000 addresses specific kinds of data including, but not limited to, master data, transaction data and product data. This document establishes the vocabulary for the ISO 8000 series of parts. Annex A contains an identifier that unambiguously identifie

19、s this document in an open information system. ISO 2017 All rights reserved v Data quality Part 2: Vocabulary 1 Scope This document defines terms relating to data quality used in the ISO 8000 series of parts. 2 Normative references There are no normative references in this document. 3 T erms a nd de

20、finiti ons ISO and IEC maintain terminological databases for use in standardization at the following addresses: ISO Online browsing platform: available at h t t p :/ www .iso .org/ obp IEC Electropedia: available at h t t p :/ www .electropedia .org/ 3.1 Terms relating to applications 3.1.1 applicat

21、ion group of one or more processes (3.3.3) creating or using product data (3.11.5) SOURCE: ISO 10303-1:1994, 3.2.2 3.1.2 application protocol AP part of ISO 10303 that specifies an application interpreted model satisfying the scope and information (3.2.7) requirements (3.3.4) for a specific applicat

22、ion (3.1.1) Note 1 to entry: This definition differs from the definition used in open system interconnection (OSI) standards. However, since this document is not intended to be used directly with OSI communications, no confusion should arise. SOURCE: ISO 10303-1:1994, 3.2.7, modified The words “this

23、 International Standard” have been replaced by “this document” in the Note to entry. 3.1.3 application reference model ARM information (3.2.7) model that describes the information requirements (3.3.4) and constraints of a specific application (3.1.1) context SOURCE: ISO 10303-1:1994, 3.2.8 INTERNATI

24、ONAL ST ANDARD ISO 8000-2:2017(E) ISO 2017 All rights reserved 1 ISO 8000-2:2017(E) 3.2 Terms relating to data and information 3.2.1 data reinterpretable representation of information (3.2.7) in a formalized manner suitable for communication, interpretation, or processing SOURCE: ISO/IEC 2382:2015,

25、2121272, modified Notes to entry have been removed. 3.2.2 data exchange storing, accessing, transferring and archiving of data (3.2.1) SOURCE: ISO 10303-1:1994, 3.2.15 3.2.3 data message message used to exchange data (3.2.1) between organizations EXAMPLE 1 Web Services call: data to be exchanged con

26、sisting of Extensible Markup Language (XML) elements in a Simple Object Access Protocol (SOAP) envelope. EXAMPLE 2 E-mail message: data to be exchanged consisting of an XML file attached to the e-mail. EXAMPLE 3 Java remote method invocation call: data to be exchanged consisting of Java objects seri

27、alized according to the Java Remote Method Invocation (RMI) specification. EXAMPLE 4 Open Database Connectivity (ODBC) call: data to be exchanged consisting of an update statement encoded according to the ODBC specification. EXAMPLE 5 File or data to be exchanged contained on a compact diskette deli

28、vered to an organization by a person: data to be exchanged consisting of a spreadsheet. 3.2.4 data set logically meaningful grouping of data (3.2.1) EXAMPLE 1 Computer-aided design (CAD) files. EXAMPLE 2 Electronic data interchange (EDI) transactions. 3.2.5 d at a s p e c i f ic at ion rules for des

29、cribing items belonging to a particular class using entries from a data dictionary (3.7.1) SOURCE: ISO 22745-2:2010, B.2.18, modified Examples have been removed. 3.2.6 entity concrete or abstract thing in the domain under consideration SOURCE: ISO 19439:2006, 3.29, modified The word “any” has been r

30、emoved at the start of the definition. 3.2.7 information knowledge concerning objects, such as facts, events, things, processes (3.3.3), or ideas, including concepts, that within a certain context has a particular meaning SOURCE: ISO/IEC 2382:2015, 2121271, modified Field of application and notes to

31、 entry have been removed.2 ISO 2017 All rights reserved ISO 8000-2:2017(E) 3.2.8 metadata data (3.2.1) defining and describing other data SOURCE: ISO/IEC 11179-1:2015, 3.2.16, modified The words “that defines and describes” have been replaced by “defining and describing”. 3.2.9 or g a n i z at ion i

32、de nt i f ie r reference that can be resolved unambiguously to the legal name, location and the administrator of the organization 3.3 Terms relating to quality 3.3.1 quality degree to which a set of inherent characteristics of an object fulfils requirements (3.3.4) Note 1 to entry: The term “quality

33、 can be used with adjectives such as poor, good or excellent. Note 2 to entry: “Inherent”, as opposed to “assigned”, means existing in the object. SOURCE: ISO 9000:2015, 3.6.2 3.3.2 quality management system part of a management system with regard to quality (3.3.1) SOURCE: ISO 9000:2015, 3.5.4 3.3

34、3 process set of interrelated or interacting activities that use inputs to deliver an intended result SOURCE: ISO 9000:2015, 3.4.1, modified Notes to entry have been removed. 3.3.4 requirement need or expectation that is stated, generally implied or obligatory SOURCE: ISO 9000:2015, 3.6.4, modified

35、 Notes to entry have been removed. 3.4 Terms relating to data quality 3.4.1 accepted reference value value that serves as an agreed-upon reference for comparison Note 1 to entry: The accepted reference value is derived as: a) a theoretical or established value, based on scientific principles; b) an

36、assigned or certified value, based on experimental work of some national or international organization; c) a consensus or certified value, based on collaborative experimental work under the auspices of a scientific or technical group; d) the expectation, i.e. the mean of a specified set of measureme

37、nts (3.9.2), when a), b) and c) are not available. SOURCE: ISO 3534-2:2006, 3.2.7 ISO 2017 All rights reserved 3 ISO 8000-2:2017(E) 3.4.2 authoritative data source owner of a process (3.3.3) that creates data (3.2.1) EXAMPLE The Department of Transportation of the Commonwealth of Pennsylvania, USA,

38、is the authoritative data source for Pennsylvania motor vehicle registration records. 3.4.3 data accuracy closeness of agreement between a property value (3.6.2) and the true value (3.4.11) Note 1 to entry: In practice, the accepted reference value (3.4.1) is substituted for the true value. 3.4.4 da

39、ta accuracy record record of the information (3.2.7) provided about the accuracy (3.11.1) of a piece of data (3.2.1) Note 1 to entry: A data accuracy record can include representations and warranties of the datas accuracy. 3.4.5 data completeness quality (3.3.1) of having all data (3.2.1) that exist

40、ed in the possession of the sender at time the data message (3.2.3) was created 3.4.6 data completeness record record of the information (3.2.7) provided about the completeness of a piece of data (3.2.1) Note 1 to entry: A data completeness record can include representations and warranties of the da

41、tas completeness. 3.4.7 data error non-fulfilment of a data (3.2.1) requirement (3.3.4) Note 1 to entry: In this term, “error” is synonymous with nonconformity (3.14.8). 3.4.8 data quality degree to which a set of inherent characteristics of data (3.2.1) fulfils requirements (3.3.4) Note 1 to entry:

42、 See also quality (3.3.1). 3.4.9 data quality management coordinated activities to direct and control an organization with regard to data quality (3.4.8) 3.4.10 data provenance record record of the ultimate derivation and passage of a piece of data (3.2.1) through its various owners or custodians No

43、te 1 to entry: A data provenance record can include information (3.2.7) about creation, update, transcription, abstraction, validation (3.4.12), and transferring ownership of data. 3.4.11 true value value that characterizes a characteristic perfectly defined in the conditions that exist when the cha

44、racteristic is considered Note 1 to entry: The true value is a theoretical concept and, in general, cannot be known exactly. SOURCE: ISO 3534-2:2006, 3.2.5, modified.4 ISO 2017 All rights reserved ISO 8000-2:2017(E) 3.4.12 validation confirmation, through the provision of objective evidence (3.14.9)

45、 that the requirements (3.3.4) for a specific intended use or application (3.1.1) have been fulfilled SOURCE: ISO 9000:2015, 3.8.13, modified Notes to entry have been removed. 3.4.13 ve r i f ic at ion confirmation, through the provision of objective evidence (3.14.9), that specified requirements (

46、3.3.4) have been fulfilled SOURCE: ISO 9000:2015, 3.8.12, modified Notes to entry have been removed. 3.5 Terms relating to syntax and semantics 3.5.1 formal syntax specification of the valid sentences of a formal language using a formal grammar EXAMPLE 1 An XML document type definition (DTD) is a fo

47、rmal syntax. EXAMPLE 2 ISO 10303-21 contains a formal syntax in Wirth Syntax Notation (WSN) for ISO 10303 physical files. Note 1 to entry: A formal language is computer-interpretable. Note 2 to entry: Formal grammars are usually Chomsky context-free grammars. Note 3 to entry: Variants of Backus-Naur

48、 Form (BNF) such as Augmented Backus-Naur Form (ABNF) and Wirth Syntax Notation (WSN) are often used to specify the syntax of computer programming languages and data (3.2.1) languages. 3.5.2 semantic encoding technique of replacing natural language terms in a message with identifiers that reference

49、data dictionary entries (3.7.2) 3.5.3 s e m a n t i c a l l y c o d e d d a t a s p e c i f i c a t i o n data requirements statement data specification (3.2.5) that uses entries from a data dictionary (3.7.1) EXAMPLE 1 An ISO/TS 22745-30 compliant identification guide. EXAMPLE 2 ISO 13584-501. Note 1 to entry: A semantically coded data specification can be used to specify rules for describing items belonging to a particular class using semantic encoding (3.5.2). 3.6 Terms related to cha