BS ISO IEC 20944-5-2013 Information technology Metadata Registries Interoperability and Bindings (MDR-IB) Profiles《信息技术 元数据登记系统互用性和绑定(MDR-IB) 配置文件》.pdf

《BS ISO IEC 20944-5-2013 Information technology Metadata Registries Interoperability and Bindings (MDR-IB) Profiles《信息技术 元数据登记系统互用性和绑定(MDR-IB) 配置文件》.pdf》由会员分享，可在线阅读，更多相关《BS ISO IEC 20944-5-2013 Information technology Metadata Registries Interoperability and Bindings (MDR-IB) Profiles《信息技术 元数据登记系统互用性和绑定(MDR-IB) 配置文件》.pdf（28页珍藏版）》请在麦多课文档分享上搜索。

1、raising standards worldwide NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW BSI Standards Publication BS ISO/IEC 20944-5:2013 Information technology Metadata Registries Interoperability and Bindings (MDR-IB) Part 5: ProfilesBS ISO/IEC 20944-5:2013 BRITISH STANDARD National for

2、eword This British Standard is the UK implementation of ISO/IEC 20944-5: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 . A list of organizations represented on this committee can

3、 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 Standards Limited 2013. ISBN 978 0 580 56089 7 ICS 35.040 Com

4、pliance 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 Date T e x t a f f e c t e dBS ISO/IEC 20944-5:2013Reference n

5、umber ISO/IEC 20944-5:2013(E) ISO/IEC 2013INTERNATIONAL STANDARD ISO/IEC 20944-5 First edition 2013-01-15 Information technology Metadata Registries Interoperability and Bindings (MDR-IB) Part 5: Profiles Technologies de linformation Interoprabilit et liaisons des registres de mtadonnes (MDR-IB) Par

6、tie 5: Profils BS ISO/IEC 20944-5:2013 ISO/IEC 20944-5:2013(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2013 All rights 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 microf

7、ilm, without permission in writing from either ISO at the address below or ISOs member body in the country of the 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

8、 2013 All rights reservedBS ISO/IEC 20944-5:2013 ISO/IEC 20944-5:2013(E) ISO/IEC 2013 All rights reserved iiiContents Page Foreword iv Introduction . v 1 Scope 1 2 Normative references 1 3 Terms and definitions . 1 4 Attribute mapping for ISO/IEC 11179-3 MDR metamodel 2 4.1 General . 2 4.2 Value spa

9、ce of labels 2 4.3 Available labels 2 4.4 Label formation 2 4.5 Resolving conflicts 4 4.6 Additional provisions 4 4.7 Identifier mappings . 5 4.8 Conformance label 13 5 Profile for ISO/IEC 11179-3 MDR metamodel 13 5.1 General . 13 5.2 Profile . 14 5.3 Conformance label 14 Annex A (informative) Devel

10、oping and using profiles 15 Bibliography 17 BS ISO/IEC 20944-5:2013 ISO/IEC 20944-5: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 standardi

11、zation. National bodies that are members 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 mut

12、ual interest. Other international organizations, 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 accorda

13、nce with the rules given in the ISO/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 Stand

14、ard requires approval by at least 75 % 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-5

15、 was prepared by Joint Technical Committee 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: Fra

16、mework, common vocabulary, and common provisions for conformance Part 2: Coding bindings Part 3: API bindings Part 4: Protocol bindings Part 5: Profiles BS ISO/IEC 20944-5:2013 ISO/IEC 20944-5:2013(E) ISO/IEC 2013 All rights reserved vIntroduction This part of ISO/IEC 20944 contains provisions that

17、are common to the profiles, and the profiles themselves. It is intended that this part of ISO/IEC 20944 will be extended, via amendments or revisions, as additional profiles are established. BS ISO/IEC 20944-5:2013BS ISO/IEC 20944-5:2013 INTERNATIONAL STANDARD ISO/IEC 20944-5:2013(E) ISO/IEC 2013 Al

18、l rights reserved 1Information technology Metadata Registries Interoperability and Bindings (MDR-IB) Part 5: Profiles 1 Scope The ISO/IEC 20944 series of International Standards describe codings, application programming interfaces (APIs), and protocols for interacting with an ISO/IEC 11179 metadata

19、registry (MDR). This part of ISO/IEC 20944 specifies the common provisions for profiles using the ISO/IEC 20944 series. This part of ISO/IEC 20944 specifies mapping of metamodel attributes, as specified in ISO/IEC 11179-3, to identifiers for the purpose of navigating metadata registries. 2 Normative

20、 references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC Guide 2, Standardization and

21、related activities General vocabulary ISO/IEC TR 10000-1, Information technology Framework and taxonomy of International Standardized Profiles Part 1: General principles and documentation framework ISO/IEC 11179-3:2003, Information technology Metadata registries (MDR) Part 3: Registry metamodel and

22、basic attributes ISO/IEC 20944-1:2013, Information technology Metadata Registries Interoperability and Bindings (MDR- IB) Framework, common vocabulary, and common provisions for conformance 3 Terms and definitions For the purposes of this document, the terms and definitions given in ISO/IEC 20944-1

23、apply. 11Users and implementers of this part of ISO/IEC 20944 may find it useful to reference the terms and definitions from ISO/IEC 20944-1. BS ISO/IEC 20944-5:2013 ISO/IEC 20944-5:2013(E) 2 ISO/IEC 2013 All rights reserved4 Attribute mapping for ISO/IEC 11179-3 MDR metamodel 4.1 General The identi

24、fiers in this clause provide a common mapping to the attributes of the ISO/IEC 11179-3 metamodel. Although the identifiers describe a hierarchical path, there is no requirement that the metamodel be organized or implemented in a hierarchical structure. 4.2 Value space of labels The value space of po

25、ssible labels (i.e., navigable identifiers) is the value space defined by the ISO/IEC 11404 datatype: type character_based_multiple_identifier = array (0*) of ( characterstring(iso-10646) ) NOTE The characterstring datatype is used for representing labels, such as metamodel attribute identifiers (e.

26、g., “units_of_measure“), and used for representing array indexes (e.g., the string “0“ represents the index of the first element of an array). 4.3 Available labels The value space is the set of characterstrings. 24.4 Label formation The ISO/IEC 11179-3 registry metamodel describes a data model (for

27、metadata) in UML notation. The following conventions apply with respect to mapping ISO/IEC 11179-3 metamodel attributes to navigable identifiers that may be used to access the data of the metamodel attribute (i.e., metadata). 4.4.1 Semantic provisions The ISO/IEC 11179-3 metamodel uses a limited set

28、 of UML metaobjects (UML features) from the UML notation. The ISO/IEC 11179-3 metamodel employs the following constraints or assumptions: A limited set of UML metaobjects are used: classes, attributes, containment, relations, objectified relations, specialization. Classes only have attributes and re

29、lations; classes do not have methods. All attributes are public. Specialized classes only use single inheritance. These UML notational features are transformed as follows: UML class notation: UML classes are comprised of UML attributes and UML relations. From the class, this part of ISO/IEC 20944 de

30、scribes navigation to the attributes and, if navigable, navigation to the relationship. 2The distinction between possible and available is: the “possible“ concerns the value space from which the labels are chosen, while the “available“ concerns those ones that are valid. For example, in North Americ

31、a, phone numbers come from a possible list of 10-digit numbers “nnn-nnn-nnnn“, but not all possible numbers are available, e.g., numbers whose first digits are 0 or 1 are not available (e.g., “022-222-2222“ is not available). BS ISO/IEC 20944-5:2013 ISO/IEC 20944-5:2013(E) ISO/IEC 2013 All rights re

32、served 3 UML attributes: An attribute is navigated according to the access operations supported by its datatype. For example, an array is accessed by its index; a record is accessed by the labels of its components. UML relations: A relation may be navigated from its roles (sides) that support naviga

33、tion. Objectified relations may be navigated from the relations roles that support navigation. UML containment relations: A containment relation may be navigated from its parent. UML relations roles multiplicity: A cardinality of 01 or 11 may be navigated directly by the relation role. A cardinality

34、 of 0* or 1* may be navigated as an array of relations for the particular role. Other constraints and provisions of the ISO/IEC 11179-3 metamodel are contained in the normative wording of ISO/IEC 11179-3. Inheritance is simulated by copying all the attributes and relationships of the base type to th

35、e subtype, e.g. if “Y“ is derived from the base type “X“, and “X“ has attributes “A“ and “B“, and relation “C“, and “Y“ has attributes “D“ and “E“, then an instance of “Y“ has the navigable identifiers “a“, “b“, “c_relation“, “d“, and “e“. A conforming implementation shall map the labels defined in

36、this Clause to a conforming ISO/IEC 11179-3 metadata registry 4.4.2 Syntactic provisions The following are syntax requirements All identifiers that refer to classes have the suffix “_class“ added to the identifier, e.g., the “Representation Class“ class, becomes “representation_class_class“. All ide

37、ntifiers that refer to navigable relations have the suffix “_relation“ added to the identifier (e.g., “classifying_relation“, “classified_by_relation“). Containment relationships are represented by the component name (and not “Containing“), e.g., the “Classification Scheme“ class contains a “Classif

38、ication Scheme Item“ class which is represented by “classification_scheme_membership“; in other words, if “X“ represents an instance of the “Classification Scheme“ class, then “X/classification_scheme_membership“ represents an instance(s) of the “Classification Scheme Item“ (see below for more infor

39、mation on indexing notation for this particular class). Attributes of objectified relationships are accessed via the “_relation“ access token, e.g., if “X“ is an instance of an “administered_item_class“, then “X/having_relation/P/_relation/terminological_entry“ represents a component of the “termino

40、logical_entry“ objectified relation class. Attributes and relationships with cardinality “11“ are represented without indexing. Attributes and relationships with cardinality “01“ are represented without indexing. Note: In the case of zero instances, it is assumed that the implementation will have so

41、me technique for determining whether or not the optional feature is present. Attributes and relationships with other cardinalities (e.g., “0*“, “1*“) are accessed via an indexing mechanism, e.g., if “X“ is an instance of the “language_section_class“, then “X/name_entry/0“, “X/name_entry/1“, “X/name_

42、entry/2“, etc., may represent the identifiers associated with each of the “name_entry“s. The slash character “/“ is used to separate components of a navigation identifier. Note that individual bindings may use different component separators and other syntax conventions. BS ISO/IEC 20944-5:2013 ISO/I

43、EC 20944-5:2013(E) 4 ISO/IEC 2013 All rights reserved4.4.3 Lexical provisions The following are lexical provisions All identifier are transformed to lower case, spaces are transformed to underscores, and other punctuation is removed, e.g., “Context (for administered item)“ becomes “context_for_admin

44、istered_item“. All identifiers that refer to classes have the suffix “_class“ added to the identifier, e.g., the “Representation Class“ class, becomes “representation_class_class“. Containment relationships are represented by the component name (and not “Containing“), e.g., the “Classification Schem

45、e“ class contains a “Classification Scheme Item“ class which is represented by “classification_scheme_membership“; in other words, if “X“ represents an instance of the “Classification Scheme“ class, then “X/classification_scheme_membership“ represents an instance(s) of the “Classification Scheme Ite

46、m“ (see below for more information on indexing notation for this particular class). Navigable relationships are represented by their relationship names (e.g., “Classifying“, “Classified By“) and not their relationship type (e.g., “administered_item_classification“). All identifiers that refer to nav

47、igable relations have the suffix “_relation“ added to the identifier (e.g., “classifying_relation“, “classified_by_relation“). 4.4.4 Lifecycle Not applicable. 4.4.5 Re-use Not applicable. 4.5 Resolving conflicts Not applicable. 4.6 Additional provisions 4.6.1 Mandatory top level identifiers The foll

48、owing identifiers shall be accessible at the top level navigation of an administered item within a registry; these identifiers represent starting points for navigating the registry metamodel. administered_item_class classification_scheme_class conceptual_domain_class enumerated_conceptual_domain_cla

49、ss non_enumerated_conceptual_domain_class context_for_administered_item_class data_element_class derivation_rule_class data_element_concept_class object_class_class property_class representation_class_class value_domain_class enumerated_value_domain_class non_enumerated_value_domain_class registration_authority_class organization_class BS ISO/IEC 20944-5:2013 ISO/IEC 20944-5:2013(E) ISO/IEC 2013 All rights reserved 5Example If “X“ represents the navig