BS ISO IEC 20944-1-2013 Information technology Metadata Registries Interoperability and Bindings (MDR-IB) Framework common vocabulary and common provisions for conformance.pdf

1、raising standards worldwide NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW BSI Standards Publication BS ISO/IEC 20944-1:2013 Information technology Metadata Registries Interoperability and Bindings (MDR-IB) Part 1: Framework, common vocabulary, and common provisions for confo

2、rmanceBS ISO/IEC 20944-1:2013 BRITISH STANDARD National foreword This British Standard is the UK implementation of ISO/IEC 20944-1:2013. The UK participation in its preparation was entrusted to T e c h n i c a l C o m m i t t e e I S T / 4 0 , D a t a m a n a g e m e n t a n d i n t e r c h a n g e

3、. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2013. Published by BSI St

4、andards Limited 2013. ISBN 978 0 580 53640 3 ICS 35.040 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 January 2013. Amendments issued since publication Dat

5、e T e x t a f f e c t e dBS ISO/IEC 20944-1:2013Reference number ISO/IEC 20944-1:2013(E) ISO/IEC 2013INTERNATIONAL STANDARD ISO/IEC 20944-1 First edition 2013-01-15 Information technology Metadata Registries Interoperability and Bindings (MDR-IB) Part 1: Framework, common vocabulary, and common prov

6、isions for conformance Technologies de linformation Interoprabilit et liaisons des registres de mtadonnes (MDR-IB) Partie 1: Cadre dapplications, vocabulaire commun et dispositions communes de conformit BS ISO/IEC 20944-1:2013 ISO/IEC 20944-1:2013(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2013 All rig

7、hts reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the country of th

8、e requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2013 All rights reservedBS ISO/IEC 20944-1:2013 ISO/IEC 20944-1:2013(E) ISO/IEC 2013 All rights reserved iiiCon

9、tents Page Foreword iv Introduction . v 1 Scope 1 1.1 General . 1 1.2 Overview of concepts . 2 2 Normative references 3 3 Terms and definitions . 4 3.1 Terms and definitions from ISO/IEC Guide 2 . 4 3.2 Terms and definitions from ISO/IEC Directives, Part 2 . 8 3.3 Terms and definitions from ISO/IEC

10、JTC 1 Directives . 9 3.4 Terms and definitions from ISO 704 9 3.5 Terms and definitions from ISO 1087-1 . 9 3.6 Terms and definitions from ISO/IEC 2382-1, fundamental terms . 10 3.7 Terms and definitions from ISO/IEC 2382-4, organization of data . 15 3.8 Terms and definitions from ISO/IEC 2382-5, re

11、presentation of data . 21 3.9 Terms and definitions from ISO/IEC 2382-6, preparation and handling of data . 21 3.10 Terms and definitions from ISO/IEC 2382-7, computer programming . 24 3.11 Terms and definitions from ISO/IEC 2382-8, security 26 3.12 Terms and definitions from ISO/IEC 2382-9, data co

12、mmunications 33 3.13 Terms and definitions from ISO/IEC 2382-15, programming languages . 37 3.14 Terms and definitions from ISO/IEC 2382-17, databases 38 3.15 Terms and definitions from ISO/IEC 2382-18, distributed data processing 44 3.16 Terms and definitions from ISO/IEC TR 10000-1 44 3.17 Terms a

13、nd definitions from ISO/IEC 11404 . 45 3.18 Terms and definitions from ISO/IEC 11179 . 46 3.19 Terms and definitions from ISO/IEC 13886 . 47 3.20 Terms and definitions from ISO/IEC 19501 . 49 3.21 Terms and definitions particular to this document . 49 3.22 Acronyms, initialisms, and abbreviations 71

14、 4 Conformance . 72 4.1 Conformance level 73 4.2 Profiles, derived standards, subset standards, superset standards, and extensions 73 4.3 Strictly conforming implementations 73 4.4 Conforming implementations 73 4.5 Conformance labels 74 5 Derived normative documents, profiles, extensions . 74 5.1 De

15、rived normative document (derived standard) 74 5.2 General principles of a profile 74 5.3 Extensions . 75 Annex A (informative) Using ISO/IEC 20944 as building blocks for metadata and data interchange 77 Annex B (informative) Rationale 80 Annex C (normative) Conformance labels . 84 Index of definiti

16、ons . 85 BS ISO/IEC 20944-1:2013 ISO/IEC 20944-1:2013(E) iv ISO/IEC 2013 All rights reservedForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are me

17、mbers of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international o

18、rganizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO

19、/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 7

20、5 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 20944-1 was prepared by Joint Technical Co

21、mmittee ISO/IEC JTC 1, Information technology, Subcommittee SC 32, Data management and interchange. ISO/IEC 20944 consists of the following parts, under the general title Information technology Metadata Registries Interoperability and Bindings (MDR-IB): Part 1: Framework, common vocabulary, and comm

22、on provisions for conformance Part 2: Coding bindings Part 3: API bindings Part 4: Protocol bindings Part 5: Profiles BS ISO/IEC 20944-1:2013 ISO/IEC 20944-1:2013(E) ISO/IEC 2013 All rights reserved vIntroduction ISO/IEC 20944 provides the bindings and their interoperability for metadata registries,

23、 such as those specified in ISO/IEC 11179. This part of ISO/IEC 20944 contains an overview, framework, common vocabulary, and common provisions for conformance for ISO/IEC 20944. In the context of increasing metadata and data interoperability harmonization, four methodologies have been employed to s

24、implify the tasks and to reduce risk. The first methodology employed is the treating of data (and metadata) interoperability as a series of layered technical specifications (e.g., standards), from application-independent layers to application-specific layer(s). The second methodology employed is the

25、 simplification of interoperability specializations, also known as bindings. Rather than independently developing each separate method of representation and access codings, application programming interfaces (APIs), protocols, a common, harmonized approach is taken where each binding is derived in a

26、 consistent two-step process: Step #1 is choosing from the categories of coding, API, protocol (or combination), which themselves are derived from a common data model and navigation method. Step #2 is to derive the specific binding from its general binding, e.g., the XML coding binding (ISO/IEC 2094

27、4-2:2012, Clause 12) and other (specific) coding bindings are derived from the generic coding binding (ISO/IEC 20944-2:2012, Clauses 1-10); the C API binding (ISO/IEC 20944-3:2012, Clause 11), the Java API binding (ISO/IEC 20944-3:2012, Clause 12), and the other API bindings are derived from the gen

28、eric API binding (ISO/IEC 20944-3:2012, Clauses 1-10). Because these bindings have a well-defined derivation, the bindings are harmonized, i.e., there is commonality in meaning and interpretation across the bindings. Thus, the complexity of adding and harmonizing a new (coding, API, protocol) bindin

29、g is greatly simplified. The third methodology employed is the use of rule-based bindings to simplify the normative wording of the standards. A rule-based binding is a binding that is specified by a general set of rules (in contrast to application-specific normative wording). For example, the XML co

30、ding binding is based upon a set of transformation rules (in contrast to specifying a specific DTD or XML schema). The fourth methodology involves the harmonization of bindings within a category. For example, the XML coding binding is intended to be harmonized with the ASN.1 coding binding; the C AP

31、I binding is intended to be harmonized with the Java API binding, etc. BS ISO/IEC 20944-1:2013BS ISO/IEC 20944-1:2013 INTERNATIONAL STANDARD ISO/IEC 20944-1:2013(E) ISO/IEC 2013 All rights reserved 1Information technology Metadata Registries Interoperability and Bindings (MDR-IB) Part 1: Framework,

32、common vocabulary, and common provisions for conformance 1 Scope 1.1 General ISO/IEC 20944 is a series of International Standards that describe codings, APIs, and protocols for interacting with an ISO/IEC 11179 metadata registry (MDR). This part of ISO/IEC 20944 provides the overview, framework, com

33、mon vocabulary, and common provisions for conformance for ISO/IEC 20944. It addresses the following data interoperability features 1 : a common framework for variety control: harmonized concepts for conforming implementations and strictly conforming implementations; harmonized provisions, such as ma

34、ndatory requirements 2and optional requirements 3 , and their consistent application across all bindings of ISO/IEC 20944; harmonized and consistent treatment of data elements with varying data obligation attributes (e.g., mandatory, conditional, optional, extended) and varying data longevity attrib

35、utes (e.g., in-use, obsolete, reserved, etc.). This part of ISO/IEC 20944 also includes a rationale that guided its development. The rationale also discusses the harmonized use of profiles (e.g., subsets, supersets, changes, etc.) of the data structure and data elements. 1The concept of data interop

36、erability applies to metadata when metadata is treated as data, e.g., metadata item attributes (as specified by ISO/IEC 11179-3) that are transferred or exchanged. The concept of data interoperability is different from metadata interoperability (agreement upon the meaning of descriptive data), which

37、 is outside the scope of ISO/IEC 20944. 2In the context of this part of ISO/IEC 20944, the term mandatory requirement is defined as in ISO/IEC Guide 2:2004, subclause 7.5.1: a requirement of a normative document that must necessarily be fulfilled in order to comply with that document. There is no im

38、plication that the aforementioned requirement is compulsory by law or regulation. This kind of mandatory requirement is also known as an exclusive requirement. 3ISO/IEC Guide 2:2004, subclause 7.5.2 defines the term optional requirement, which includes the following note: An optional requirement may

39、 be either: a) one of two or more alternative requirements; or b) an additional requirement that must be fulfilled only if applicable and that may otherwise be disregarded. BS ISO/IEC 20944-1:2013 ISO/IEC 20944-1:2013(E) 2 ISO/IEC 2013 All rights reserved1.2 Overview of concepts 1.2.1 Metadata vs. d

40、ata Metadata is descriptive data about objects 4 . The essential characteristics of metadata include: it is descriptive data, and that it is descriptive about something. For example, if P is data and P Q represents the descriptive relationship such that P describes Q, then P is metadata about Q. If

41、there is no relationship from P to Q, then P is no longer metadata (i.e., P is merely data) because metadata is always relative to the object of description. Or stated differently, P only becomes metadata once its descriptive relationship to Q is established. Thus, it is impossible to determine, ind

42、ependent of context and relationships, that any piece of data is actually also metadata. The implications are: (1) because metadata is data, it can be exchanged like other data, but (2) to remain metadata, the exchange must include the associated context and relationships. ISO/IEC 20944 simply treat

43、s everything as data whether it is used as metadata is outside the scope of ISO/IEC 20944. Although metadata is just data, ISO/IEC 20944 also provides reification 5and navigation of these contexts and relationships that are particular to metadata (and atypical for common data sets). NOTE ISO/IEC 209

44、44-5 provides a mapping and a profile such that ISO/IEC 20944 bindings may be used to interchange metadata contained in ISO/IEC 11179 metadata registries, e.g., an application may connect to, access, read, and use metadata from an ISO/IEC 11179 metadata registry. 1.2.2 Metadata and data interoperabi

45、lity The successful interchange of data is dependent upon mutual agreement of interchange participants. Some key requirements for successful data interchange include (from lower implementation details to higher level abstractions): The syntax determines how data is coded (structured) and encoded (re

46、presented). Codings include specifications for organizing data structures (e.g., How are records represented? Is tagging embedded or implied?). Encodings include specifications for representation of datatypes (e.g., are numbers represented as a string of characters or a string of bits?). EXAMPLE 1 I

47、n XML, “the temperature is 17“ might be coded as a tagged element “17“ that is encoded as 15 UTF-8 characters, the encoding would be the ordering of the bits within the octet, e.g., little endian vs. big endian. EXAMPLE 2 In the programming language C, “the temperature is 17“ might be coded as a sin

48、gle binary octet uint8_t temp = 17; , and encoded as a twos complement big-endian 16-bit integer. The semantics define the meaning of the data. Several kinds of descriptive techniques are possible, such as using ISO/IEC 11179-3 for describing data. Additional technical specifications, such as standa

49、rds, may be used in conjunction with the ISO/IEC 11179-3 description of data. EXAMPLE 3 The statement “the temperature is 17“ might not be descriptive enough because (1) it does not convey units of measure, e.g., Celsius or Fahrenheit; and (2) it does not convey what is being measured, e.g., temperature sensor #289. Both these features are part of the semantic description that comprises an ISO/IEC 11179-3 Data Element. Application-specific behavior is determined by the context of the data. EXAMPLE 4