1、INCITS/ISO/IEC 11179-5-2005 (ISO/IEC 11179-5:2005, IDT) Information technology Metadataregistries (MDR) Part 5: Naming and IdentificationprinciplesINCITS/ISO/IEC 11179-5-2005(ISO/IEC 11179-5:2005, IDT)INCITS/ISO/IEC 11179-5-2005 ii ITIC 2006 All rights reserved PDF disclaimer This PDF file may conta
2、in embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibil
3、ity of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation para
4、meters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. Adopted by INCITS (InterNational Committee f
5、or Information Technology Standards) as an American National Standard. Date of ANSI Approval: 1/30/2006Published by American National Standards Institute, 25 West 43rd Street, New York, New York 10036 Copyright 2006 by Information Technology Industry Council (ITI). All rights reserved. These materia
6、ls are subject to copyright claims of International Standardization Organization (ISO), International Electrotechnical Commission (IEC), American National Standards Institute (ANSI), and Information Technology Industry Council (ITI). Not for resale. No part of this publication may be reproduced in a
7、ny form, including an electronic retrieval system, without the prior written permission of ITI. All requests pertaining to this standard should be submitted to ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of America INCITS/ISO/IEC 11179-5-2005 ITIC 2006 - All rights re
8、served iiiContents Page Foreword iv 1 Scope1 2 Normative references1 3 Terms and definitions .2 4 Data Identifiers within a registry3 5 Identification 3 6 Names.4 6.1 Names in a registry .4 6.2 Naming conventions .4 7 Development of naming conventions .5 7.1 Introduction5 7.2 Scope principle5 7.3 Au
9、thority principle.5 7.4 Semantic principle.5 7.5 Syntactic principle.6 7.6 Lexical principle 6 7.7 Uniqueness principle 6 Annex A (informative) Example naming conventions for names within an MDR registry 7 Annex B (informative) Example naming conventions for Asian languages .16 INCITS/ISO/IEC 11179-
10、5-2005 iv ITIC 2006 - 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 members of ISO or IEC participate in the development
11、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 organizations, governmental and non-governmental, in
12、 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/IEC Directives, Part 2. The main task of the joint
13、 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 75 % of the national bodies casting a vote. Attentio
14、n 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 11179-5 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subc
15、ommittee SC 32, Data management and interchange. This second edition cancels and replaces the first edition (ISO/IEC 11179-5:1995), which has been technically revised. ISO/IEC 11179 consists of the following parts, under the general title Information technology Metadata registries (MDR): Part 1: Fra
16、mework Part 2: Classification Part 3: Registry metamodel and basic attributes Part 4: Formulation of data definitions Part 5: Naming and identification principles Part 6: Registration AMERICAN NATIONAL STANDARD INCITS/ISO/IEC 11179-5-2005 ITIC 2006 - All rights reserved 1Information technology Metad
17、ata registries (MDR) Part 5: Naming and identification principles 1 Scope This part of ISO/IEC 11179 provides instruction for naming and identification of the following administered items: data element concept, conceptual domain, data element, and value domain. It describes the parts and structure o
18、f identification. Identification is narrowly defined to encompass only the means to establish unique identification of these administered items within a register. It describes naming in an MDR; includes principles and rules by which naming conventions can be developed; and describes example naming c
19、onventions. The naming principles and rules described herein apply primarily to names of data element concepts, conceptual domains, data elements, and value domains. When “administered item“ is used in this part of ISO/IEC 11179, it is understood to refer specifically to these four items. This part
20、of ISO/IEC 11179 should be used in conjunction with those that establish rules and procedures for attributing, classifying, defining, and registering administered items. In Annex A, all of the examples are given with English terminologies. However, there is an intention that those rules be effective
21、 in other national languages, even in those languages that use ideographs such as Japanese, Chinese, or Korean, when the terminologies used in the name are controlled properly. Annex B contains a version of the rules for Asian languages. It is out of scope of the naming rules to establish semantic e
22、quivalence of the naming among different languages. Naming must be supplemented by other methods such as ontologies or controlled vocabularies in establishing semantic equivalence. 2 Normative references The following referenced documents are indispensable for the application of this document. For d
23、ated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 11179-1, Information technology Metadata registries (MDR) Part 1: Framework ISO/IEC 11179-2, Information technology Metadata registries (
24、MDR) Part 2: Classification1)ISO/IEC 11179-3, Information technology Metadata registries (MDR) Part 3: Registry metamodel and basic attributes ISO/IEC 11179-6, Information technology Metadata registries (MDR) Part 6: Registration 1) To be published. Revision of ISO/IEC 11179-2:2000 INCITS/ISO/IEC 11
25、179-5-2005 2 ITIC 2006 - All rights reserved3 Terms and definitions For the purposes of this document, the terms and definitions given in ISO/IEC 11179-1, ISO/IEC 11179-2, ISO/IEC 11179-3, ISO/IEC 11179-6, and the following apply. 3.1 administered item registry item for which administrative informat
26、ion is recorded in an Administration Record ISO/IEC 11179-3:2003 3.2 context universe of discourse in which a name or definition is used ISO/IEC 11179-3:2003 3.3 lexical pertaining to words or the vocabulary of a language as distinguished from its grammar and construction 3.4 name designation of an
27、object by a linguistic expression ISO/IEC 11179-3:2003 3.5 name part part of name discrete term that is used as part of a name of an administered item 3.6 naming convention set of rules for creating names and their associations 3.7 object class term part of the name of an administered item which rep
28、resents the object class to which it belongs, for those administered items containing object classes 3.8 principle fundamental, primary assertion which constitutes a source of action determining particular objectives or results NOTE A principle is usually supported through one or more rules. 3.9 pro
29、perty term part of the name of an administered item that expresses a property of an object class, for those administered items containing property classes 3.10 qualifier term word or words that differentiate a concept 3.11 representation term designation of an instance of a representation class INCI
30、TS/ISO/IEC 11179-5-2005 ITIC 2006 - All rights reserved 33.12 rule statement governing conduct, procedure, conditions and/or relations 3.13 semantics branch of linguistic science that deals with the meanings of words 3.14 separator symbol or space enclosing or separating a part within a name; a deli
31、miter 3.15 structure set concepts in an area of discourse, with their relationships to other concepts; examples include data models, taxonomies, and ontologies 3.16 syntax relationships among characters or groups of characters, independent of their meanings or the manner of their interpretation and
32、use; the structure of expressions in a language, and the rules governing the structure of a language 4 Data Identifiers within a registry Each administered item shall have a unique data identifier within the register of a Registration Authority. The combination of registration authority identifier,
33、data identifier, and version identifier shall constitute a unique identification of an administered item. See ISO/IEC 11179-6 for detailed information. A data identifier is assigned for any administered item that is registered. Concurrently, or thereafter, the administered item may be classified acc
34、ording to ISO/IEC 11179-2, specified according to ISO/IEC 11179-3:2003, defined according to ISO/IEC 11179-4, named according to ISO/IEC 11179-5, and registered according to ISO/IEC 11179-6. 5 Identification The registration authority identifier (RAI), data identifier (DI), and version identifier (V
35、I) constitute the international registration data identifier (IRDI). An IRDI is required for an administered item. Data identifiers are assigned by a Registration Authority; data identifiers shall be unique within the domain of a Registration Authority. Requirements for a Registration Authority, and
36、 a discussion of the IRDI, appear in ISO/IEC 11179-6. As each Registration Authority may determine its own DI assignment scheme, there is no guarantee that the DI by itself will uniquely identify an administered item. For example, if two RAs both use sequential 6-digit numbers, there may be two admi
37、nistered items with the same DIs; however, the administered items will almost certainly not be the same. Both the DI and the RAI are necessary for identification of an administered item. INCITS/ISO/IEC 11179-5-2005 4 ITIC 2006 - All rights reservedIf particular attributes of an administered item cha
38、nge, then a new version of the administered item shall be created and registered. The registrar shall determine these attributes. In such a case, a VI is required to complete the unique identification of an administered item. For further guidance, see ISO/IEC 11179-6. An IRDI can serve as a key when
39、 exchanging data among information systems, organizations, or other parties who wish to share a specific administered item, but might not utilize the same names or contexts. ISO/IEC 11179 does not specify the format or content of a unique DI. 6 Names 6.1 Names in a registry An administered item shal
40、l have at least one name within a registry of a Registration Authority. If there are other names by which the administered item is known, preferred names may be identified. Any administered item in the Registry can be subject to naming conventions. The annexes show examples of naming conventions app
41、lied to several administered items. Others can be developed by extension of the Principles. An administered item shall have at least one name within a context. See ISO/IEC 11179-3 for detailed information. 6.2 Naming conventions Each name for an administered item is specified within a context. A nam
42、ing convention describes what is known about how names are formulated. A naming convention may be simply descriptive; e.g., where the Registration Authority has no control over the formulation of names for a specific context and merely registers names that already exist. Alternatively, a naming conv
43、ention may be prescriptive, specifying how names shall be formulated, with the Registration Authority (or an equivalent authority) expected to enforce compliance with the naming convention. The objectives of a prescriptive naming convention may include name consistency, name appearance, and name sem
44、antics. An effective naming convention can also enforce the exclusion of irrelevant facts about the administered item from the name, such as the input source of a data element or its field position in a file. A naming convention may be specified in a reference document. A naming convention shall cov
45、er all relevant documentation aspects. This includes, as applicable, the scope of the naming convention, e.g. established industry name; the authority that establishes names; semantic rules governing the source and content of the terms used in a name, e.g. terms derived from data models, terms commo
46、nly used in the discipline, etc.; syntactic rules covering required term order; lexical rules covering controlled term lists, name length, character set, language; a rule establishing whether or not names must be unique. INCITS/ISO/IEC 11179-5-2005 ITIC 2006 - All rights reserved 57 Development of n
47、aming conventions 7.1 Introduction This clause lists principles used to develop a naming convention. Rules are derived from the principles; these rules form a naming convention. Syntactic, semantic and lexical rules vary by organizations such as corporations or standards-setting bodies for business
48、sectors; each can establish rules for name formation within its context(s). Annexes A and B contain examples of rules for naming conventions that are consistent with the principles presented in this clause. Descriptive naming conventions may be applied to administered items which are not under the c
49、ontrol of the Registration Authority for the registry, or other authority previous to entry in the registry. At a minimum, the rules for scope and authority should be documented. As appropriate, the semantic, syntactic, lexical, and uniqueness rules may be recorded. In addition to the scope and authority rules needed to document descriptive naming conventions, prescriptive conventions should be documented by semantic, syntactic, lexical, and uniqueness rules. Semantic rules enable meaning to be conveyed.
