information technology -metadata registries (mdr) - part 5...

Error! Reference source not found.

Document type: Error! Reference source not found. Document subtype: Error! Reference source not found. Document stage: Error! Reference source not found. Document language: Error! Reference source not found. C:\DOCUME~1\Newton\LOCALS~1\Temp\ISO-IEC_11179-5_(E)2013_DIS.docx Error! Reference source not found.

ISO/IEC JTC1 SC32 N 1

Date: 2013-12-18 2

ISO/IEC DIS 11179-5 3

4

ISO/IEC JTC1/SC32/WG2 5

6

Secretariat: ANSI 7

Information technology - Metadata registries (MDR) - Part 5: Naming 8 principles 9

Technologies de l'information — Registries de metadonnees (RM) — Partie 5: Principes de 10 denomination 11

Warning 12

This document is not an ISO International Standard. It is distributed for review and comment. It is subject to 13 change without notice and may not be referred to as an International Standard. 14

Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of 15 which they are aware and to provide supporting documentation. 16

17


ii Error! Reference source not found.

Copyright notice 18

This ISO document is a working draft or committee draft and is copyright-protected by ISO. While the 19 reproduction of working drafts or committee drafts in any form for use by participants in the ISO standards 20 development process is permitted without prior permission from ISO, neither this document nor any extract 21 from it may be reproduced, stored or transmitted in any form for any other purpose without prior written 22 permission from ISO. 23

Requests for permission to reproduce this document for the purpose of selling it should be addressed as 24 shown below or to ISO's member body in the country of the requester: 25

[Indicate the full address, telephone number, fax number, telex number, and electronic mail address, as 26 appropriate, of the Copyright Manger of the ISO member body responsible for the secretariat of the TC or 27 SC within the framework of which the working document has been prepared.] 28

Reproduction for sales purposes may be subject to royalty payments or a licensing agreement. 29

Violators may be prosecuted. 30


Error! Reference source not found. iii

Contents 1

Foreword ............................................................................................................................................................ iv 32

Introduction ......................................................................................................................................................... v 33

1 Scope ...................................................................................................................................................... 1 34

2 Normative references ............................................................................................................................ 1 35

3 Terms and definitions ........................................................................................................................... 2 36

4 Conformance ......................................................................................................................................... 5 37 4.1 Rules for a conforming registry ........................................................................................................... 5 38 4.2 Rules for a strictly conforming registry .............................................................................................. 5 39 4.3 Rules for a conforming system ............................................................................................................ 6 40 4.4 Rules for a strictly conforming system ............................................................................................... 6 41

5 The relationship of names and identifiers within a registry ............................................................. 6 42

6 Names ..................................................................................................................................................... 7 43

7 Naming conventions ............................................................................................................................. 7 44

8 Classes in the metamodel .................................................................................................................... 7 45 8.1 Namespace class ................................................................................................................................... 7 46 8.1.1 Relationship of scoped identifiers and names ................................................................................... 7 47 8.1.2 Uniqueness ............................................................................................................................................ 8 48 8.2 Naming convention class ..................................................................................................................... 8 49

9 Development of naming conventions ................................................................................................. 8 50 9.1 Introduction ............................................................................................................................................ 8 51 9.2 Scope principle ...................................................................................................................................... 9 52 9.3 Authority principle ................................................................................................................................. 9 53 9.4 Semantic principle ................................................................................................................................. 9 54 9.5 Syntactic principle ................................................................................................................................. 9 55 9.6 Lexical principle .................................................................................................................................. 10 56 9.7 Uniqueness principle .......................................................................................................................... 10 57

10 Concept system relationship to names ............................................................................................ 10 58 10.1 Concepts as higher-level classes ...................................................................................................... 10 59 10.2 Concepts as classification system .................................................................................................... 10 60

Annex A (informative) Example naming conventions for names within an MDR registry ...................... 12 61

Annex B (informative) Example naming conventions for Asian languages ............................................... 22 62

Annex C (informative) Concordance table for item names ............................................................................... 26 63 64


iv Error! Reference source not found.

Foreword 65

ISO (the International Organization for Standardization) and IEC (the International Electrotechnical 66 Commission) form the specialized system for worldwide standardization. National bodies that are members of 67 ISO or IEC participate in the development of International Standards through technical committees 68 established by the respective organization to deal with particular fields of technical activity. ISO and IEC 69 technical committees collaborate in fields of mutual interest. Other international organizations, governmental 70 and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information 71 technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. 72

International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. 73

The main task of the joint technical committee is to prepare International Standards. Draft International 74 Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as 75 an International Standard requires approval by at least 75 % of the national bodies casting a vote. 76

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent 77 rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. 78

ISO/IEC 11179-5 was prepared by Joint Technical Committee ISO/IEC JTC 1, JTC 1, Subcommittee SC 32, 79 Data Management and Interchange. 80

This third edition cancels and replaces the second edition. 81

ISO/IEC 11179 consists of the following parts, under the general title Information Technology — Metadata 82 registries (MDR): 83

Part 1: Framework 84

Part 2: Classification 85

Part 3: Registry metamodel and basic attributes 86

Part 4: Formulation of data definitions 87

Part 5: Naming principles 88

Part 6: Registration 89

90


Error! Reference source not found. v

Introduction 91

This part of ISO/IEC 11179 contains both principles and rules. Principles establish the premises on which the 92 rules are based. Registry users may enforce rules as an application of this standard. 93

A naming convention is a convention (a set of rules) about names. Many naming conventions have much in 94 common, whether it is defining a method of specifying names for common usage across application systems, 95 or developing an organization's internal policy on the choice of XML tags for data interchange. A naming 96 convention may be based on principles. In addition, it may contain formal and informal inputs, such as 97 guidelines, recommendations, company policies, programming conventions, specifications, procedures, and 98 so on. The purpose of this Part of this International Standard is to describe and specify these common 99 features of naming conventions. This part of this International Standard is intended to have broad applicability, 100 including areas outside

The goal of any naming convention is to allow development of names for items that have maximum clarity and 102 transparency of meaning, combined with concision, demanding minimal effort of interpretation by the end user, 103 subject to the constraints of the system under which the items are processed. A naming convention can be 104 used to form names by which information about the data is expressed, in a simplified but still understandable 105 grammar compared to natural language rules. Ideally, the names resemble summaries of the formal definition 106 of the information being named. 107

of Metadata Registries. 101

In a metadata registry, one name may be designated as the "registry name," derived by describing the content 108 of a metadata item in a structured way, using a set of rules, i.e., by application of a formalized naming 109 convention. Other names for the same metadata entity may occur in any context. For example, these may 110 be: 111

• Software system names 112

• Programming language names 113

• Report header names 114

• Data interchange (e.g., XML) names 115

• Names in other natural languages 116

Names may have varying levels of rigor applied to their formation and usage. The collection and display of all 117 names used by any single metadata item can be a major benefit of a metadata registry. The process of 118 deriving names from concept systems and arranging semantic components with a naming convention forms a 119 set of consistent, meaningful registry names. Names from other contexts, which may or may not have been 120 formed with naming conventions, and therefore may have little or no semantic content, are collected and 121 related to the registry name, thus contributing in a valuable way to enterprise data management. 122

Edition 3 of ISO/IEC 11179-3 uses the term designation in reference to most metamodel items except for the 123 classes Namespace and Naming Convention. The designations for these classes were adopted in deference 124 to commonly accepted usage. This Part will continue to use the term name for constructs that, for purposes of 125 this Part, are interchangeable with designation. 126

Note: Items from the metamodel described in Edition 3 of ISO/IEC 11179-3 are italicized in this document. 127 Most multi-word designations also contain underscores between words in ISO/IEC 11179-3; the underscores 128 have been omitted in this document for readability. 129

130


Error! Reference source not found. 1


1 Scope 132

This part of ISO/IEC 11179 provides instruction for naming of the following items, as defined in Part 3 of this 133 International Standard: concept, data element concept, conceptual domain, data element, and value domain. 134 This part describes naming in an MDR; includes principles and rules by which naming conventions can be 135 developed; and provides examples of naming conventions. 136

The naming principles and rules described herein apply primarily to names of concepts, data element 137 concepts, conceptual domains, data elements, and value domains, but can be extended to any registry 138 content. Differing naming conventions may be applied to different sets of designatable items. This part of 139 ISO/IEC 11179 should be used in conjunction with those which establish rules and procedures for attributing, 140 classifying, defining, and registering items1

This part may be used for applications that are unrelated to Part 3, i.e., this International Standard has broad 142 applicability for use in describing naming conventions for almost any need or purpose. The same principles 143 apply. 144

) . 141

In annex A, all of the examples are given with English terminologies. However, there is an intention that those 145 rules be effective in other natural languages, even in those languages that use ideographs such as Japanese, 146 Chinese, or Korean, when the terminologies used in the name are controlled properly. Annex B contains a 147 version of the rules for Asian languages. 148

It is out of scope of the naming rules to establish semantic equivalence of names among different languages. 149 Naming must be supplemented by other methods such as ontologies or controlled vocabularies in establishing 150 semantic equivalence. 151

This Part may be applied to Part 3 of this International Standard, i.e., describing naming conventions 152 associated with designations of designatable items and other features of the metamodel. The following are 153 examples of designations in the metamodel: the designation of a data element (class name: Designation; 154 attribute: sign); the designation of classification scheme name; etc. Annex C contains a Concordance Table 155 relating items in this part to items in Part 3. 156

This Part does not make requirements on any specific set of conventions, e.g., specific semantic, syntactic, or 157 lexical requirements for names. 158

2 Normative references 159

The following referenced documents are indispensable for the application of this document. For dated 160 references, only the edition cited applies. For undated references, the latest edition of the referenced 161 document (including any amendments) applies. 162

163

ISO/IEC 11179 (all parts), Information technology – Metadata registries (MDR) 164

1) Refer to 11179-6 Ed. 3 for a discussion of identification.


2 Error! Reference source not found.

3 Terms and definitions 165

For the purposes of this document, the following terms and definitions apply. 166

3.1 167 administered item 168 registered item (3.22) for which administrative information is recorded [ISO/IEC 11179-3:2013] 169 170 3.2 171 characteristic 172 abstraction of a property (3.19) of an object (3.15) or of a set of objects 173

NOTE Characteristics are used for describing concepts (3.3). [ISO 1087-1:2000] 174

3.3 175 concept 176 unit of knowledge created by a unique combination of characteristics (3.2) 177

NOTE: Concepts are not necessarily bound to particular languages. They are, however, influenced by the 178 social or cultural background which often leads to different categorizations. [ISO 1087-1:2000] 179

3.4 180 context 181 setting in which a designation (3.6) or definition is used [ISO/IEC 11179-3:2013] 182

3.5 183 designatable item 184 identified item which can have designations (3.5) and/or definitions [ISO/IEC 11179-3:2013] 185

3.6 186 designation 187 representation of a concept (3.3) by a sign (3.29) which denotes it [ISO/IEC 11179-3:2013] 188

3.7 189 general concept 190 concept (3.3) which corresponds to two or more objects (3.15) which form a group by reason of common 191 properties 192

NOTE Examples of general concepts are 'planet', 'tower'. [ISO 1087-1:2000] 193

3.8 194 lexical 195 pertaining to words or the vocabulary of a language as distinguished from its grammar and construction 196

3.9 197 metadata item 198 instance of a metadata object [ISO/IEC 11179-3:2013] 199

3.10 200 metadata registry 201 information system for registering metadata [ISO/IEC 11179-3:2013] 202

3.11 203 name 204 designation (3.6) of an object (3.15) by a linguistic expression [ISO/IEC 11179-3:2013] 205



3.12 206 name part 207 part of name 208 discrete term that is used as part of a name (3.11) of a designatable item (3.5) 209

3.13 210 namespace 211 set of designations (3.6) and/or scoped identifiers (3.26) for a particular business need 212

NOTE The term namespace is used in this International Standard because it is in common use, even 213 though the concept is being applied to identifiers as well as names. [ISO/IEC 11179-3:2013] 214

3.14 215 naming convention 216 specification of how signs (3.29) of designations (3.6) and/or scoped identifiers (3.26) are formulated 217

NOTE A naming convention can apply to scoped identifiers when they are included in the associated 218 namespace. [ISO/IEC 11179-3:2013] 219

3.15 220 object 221 anything perceivable or conceivable 222

NOTE 1 Objects may be material (e.g. an engine, a sheet of paper, a diamond), immaterial (e.g. conversion 223 ratio, a project plan) or imagined (e.g. a unicorn). 224

NOTE 2 Adapted from ISO1087-1:2000, 3.1.1 [ ISO/IEC 11179-3:2013 ]. 225

3.16 226 object class 227 set of ideas, abstractions or things in the real world that are identified with explicit boundaries and meaning 228 and whose properties (3.19) and behavior follow the same rules [ISO/IEC 11179-3:2013]. 229

3.17 230 object class term 231 part of the name (3.11) of a designatable item (3.5) which represents the object class (3.16) to which it 232 belongs, for those designatable items containing object classes 233

3.18 234 principle 235 fundamental, primary assertion which constitutes a source of action determining particular objectives or 236 results 237

NOTE: A principle is usually supported through one or more rules. 238

3.19 239 property 240 quality common to all members of an object class (3.16) [ ISO/IEC 11179-3:2013] 241

3.20 242 property term 243 part of the name of a designatable item (3.5) that expresses a property (3.19) of an object class (3.16), for 244 those designatable items containing property classes 245

3.21 246 qualifier term 247 word or words that help define and differentiate a concept (3.3) 248



3.22 249 registered item 250 metadata item (3.9) that is recorded and managed in a metadata registry (3.10) [ISO/IEC 11179-3:2013] 251

3.23 252 representation class 253 classification of a type of representation [ISO/IEC TR 20943-1:2003] 254

NOTE: Examples of representation include name, identifier, code, and quantity. 255

3.24 256 representation term 257 designation (3.3.6) of an instance of a representation class (3.23) 258

3.25 259 rule 260 statement governing conduct, procedure, conditions and/or relations 261

3.26 262 scoped identifier 263 identifier of an identified item within a specified namespace (3.13) 264

NOTE A namespace provides the scope within which the scoped identifier uniquely identifies the identified 265 item [ISO/IEC 11179-3:2013]. 266

3.27 267 semantics 268 branch of linguistic science that deals with the meanings of words 269

3.28 270 separator 271 symbol or space enclosing or separating a part within a name (3.11); a delimiter 272

3.29 273 sign (noun) 274 textual string or symbol that can be used to denote a concept (3.3)[ISO/IEC 11179-3:2013] 275

3.30 276 subject field 277 domain 278 field of special knowledge 279 280 NOTE The borderlines of a subject field are defined from a purpose-related point of view. [ISO 1087-1:2000] 281 282

3.31 283 structure set 284 concepts (3.3) in an area of discourse, with their relationships to other concepts 285

NOTE: Examples include data models, information models, taxonomies, and ontologies. 286

3.32 287 syntax 288 relationships among characters or groups of characters, independent of their meanings or the manner of their 289 interpretation and use 290

NOTE: More specifically, the structure of expressions in a language, and the rules governing the structure of a 291 language 292



3.33 293 term 294 verbal designation (3.6) of a general concept (3.7) in a specific subject field 295

NOTE: A term may contain symbols and can have variants, e.g., different forms of spelling. [ISO 1087-1:2000] 296

297

4 Conformance 298

4.1 Rules for a conforming registry 299

A registry containing a namespace associated with a set of designatable items which conform to naming 300 conventions so that: 301

• each item shall be named in accordance with a naming convention, 302

• each naming convention shall have its scope documented, 303

• each naming convention shall have its authority documented, 304

• each naming convention should have its semantic rules documented, 305

• each naming convention should have its syntactic rules documented, 306

• each naming convention should have its lexical rules documented, and 307

• each naming convention should have its uniqueness rules documented, 308

then that namespace is in conformance with this part of 11179. 309

A registry in which every namespace conforms to this part of 11179 is a conforming registry. 310

4.2 Rules for a strictly conforming registry 311

A registry containing a namespace associated with a set of designatable items which conform to naming 312 conventions so that: 313




• each naming convention shall have its semantic rules documented, 317

• each naming convention shall have its syntactic rules documented, 318

• each naming convention shall have its lexical rules documented, and 319

• each naming convention shall have its uniqueness rules documented, 320

then that namespace is in strict conformance with this part of 11179. 321

A registry in which every namespace strictly conforms to this part of 11179 is a strictly conforming registry. 322



4.3 Rules for a conforming system 323

A system containing a namespace associated with a set of objects which conform to naming conventions so 324 that: 325




• each naming convention should have its semantic rules documented, 329

• each naming convention should have its syntactic rules documented, 330

• each naming convention should have its lexical rules documented, and 331

• each naming convention should have its uniqueness rules documented, 332

then that namespace is in conformance with this part of 11179. 333

A system in which every namespace conforms to this part of 11179 shall be a conforming system. 334

4.4 Rules for a strictly conforming system 335

A system containing a namespace associated with a set of objects which conform to naming conventions so 336 that: 337




• each naming convention shall have its semantic rules documented, 341

• each naming convention shall have its syntactic rules documented, 342

• each naming convention shall have its lexical rules documented, and 343

• each naming convention shall have its uniqueness rules documented, 344

then that namespace is in strict conformance with this part of 11179. 345

A system in which every namespace strictly conforms to this part of 11179 shall be a strictly conforming 346 system. 347

5 The relationship of names and identifiers within a registry 348

349 Any metadata item in a registry may be one or more of the following types [ISO/IEC 11179-3:2013]: 350 351

- identified item: an item that is to be retrieved directly, and therefore needs to be referenced 352 353 - designatable item: an identified item that is to be designated (named) and/or defined 354 355



- classifiable item: an item that is to be classified in a classification scheme 356 357 At least one identifier is assigned for each identified item in the registry. Concurrently, or thereafter, the item 358 may be specified, classified, named, and registered according to the relevant part of ISO/IEC 11179. 359

360 361

6 Names 362

In Edition 3 of ISO/IEC 11179-3, sign has replaced name as the attribute of the class Designation that is used 363 to designate an object or concept. A sign may be a string denoting a word or phrase in a natural language, a 364 string denoting a term in a special language, or an icon or other symbol. A name is considered to be 365 language-dependent; that is, a linguistic expression. The output of a naming convention is a set of names and 366 (possibly) symbols, such as dollar signs. 367

As this Part of ISO/IEC 11179 discusses the classes Namespace and Naming Convention in Edition 3 of 368 ISO/IEC 11179-3, this Part will refer to the product of a naming convention as a name. 369

7 Naming conventions 370

A naming convention describes what is known about how names are formulated. A naming convention may 371 be simply descriptive; e.g., where the Registration Authority has no control over the formulation of names for a 372 specific context and merely registers names that already exist. Alternatively, a naming convention may be 373 prescriptive, specifying how names shall be formulated, with the Registration Authority (or an equivalent 374 authority) expected to enforce compliance with the naming convention. The objectives of a prescriptive 375 naming convention may include name consistency, name appearance, and name semantics. An effective 376 naming convention can also enforce the exclusion of irrelevant facts about the designatable item from the 377 name. Though there are no facts that are irrelevant in every case, the input source of a data element or its 378 field position in a file might be if names are designed to convey meaning. 379 380 A naming convention may be specified in a reference document. A naming convention shall cover all relevant 381 documentation aspects. This includes, as applicable, 382 383

- the scope of the naming convention, e.g. established industry name; 384 385 - authority information, including the authority that establishes names, namespace membership, sources 386 such as term list or glossary; 387 388 -semantic rules governing the source and content of the terms used in a name, e.g. terms derived from 389 data models, terms commonly used in the discipline, etc.; 390 391 - syntactic rules covering required term order; 392 393 - lexical rules covering controlled term lists, name length, character set, language; 394 395 - a rule establishing whether or not names must be unique. 396

8 Classes in the metamodel 397

8.1 Namespace class 398

8.1.1 Relationship of scoped identifiers and names 399

In addition to the identifier assigned to identified items (clause 5), the scoped identifier specified in Edition 3 of 400 ISO/IEC 11179-3 is assigned to items within the scope of a Namespace class. It serves to unambiguously 401



identify items within that namespace. This scoped identifier may have a shorthand prefix, which can be 402 attached to a name to identify a namespace. Examples of this usage are provided in clause A.4. 403

8.1.2 Uniqueness 404

There are two aspects to uniqueness that may be expressed using the metamodel constructs - the two 405 attributes in Namespace class: one name per item indicator and one item per name indicator. 406

The one name per item indicator denotes whether more than one Designation and/or Scoped Identifier within 407 the Namespace may be associated with any single item (Designatable Item and/or Identified Item). If the 408 indicator is true, then at most one Designation and/or Scoped Identifier within the Namespace may be 409 associated with any single item [ISO/IEC 11179-3:2013]. This effectively disallows the use of synonyms. 410

The one item per name indicator denotes whether the Namespace may contain more than one Designation 411 and/or Scoped Identifier having the same sign and/or identifier. If the indicator is true, then at most one 412 Designation and/or Scoped Identifier having the same sign and/or identifier is permitted within the Namespace 413 [ISO/IEC 11179-3:2013]. This effectively disallows the use of homonyms. 414

8.2 Naming convention class 415

The Naming Convention class in Edition 3 of ISO/IEC 11179-3 provides a location in the metamodel for 416 recording most of the rules for any particular naming convention. The rules contained in the Naming 417 Convention class are: 418

- scope rule 419

- authority rule 420

- semantic rule 421

- syntactic rule 422

- lexical rule 423

These are all of the type Text and are meant to allow as much complexity in description as needed to describe 424 each rule. See clause 9.7 for a discussion of the uniqueness principle and a discussion of the rules that might 425 follow. 426

427

9 Development of naming conventions 428

9.1 Introduction 429

This clause lists principles used to develop a naming convention. Rules are derived from the principles; these 430 rules form a naming convention. Syntactic, semantic and lexical rules vary by organizations such as 431 corporations or standards-setting bodies for business sectors; each can establish rules for name formation 432 within its context(s). Annexes A and B contain examples of rules for naming conventions that are consistent 433 with the principles presented in this clause. 434 435 Descriptive

440

naming conventions may be applied to designatable items that are not under the control of the 436 Registration Authority for the registry, or other authority previous to entry in the registry. At a minimum, the 437 rules for scope and authority shall be documented. As appropriate, the semantic, syntactic, lexical, and 438 uniqueness rules should be recorded. 439



Attached items, which are items that are administered in the registry as part of a group of items, may not have 441 enough information to describe using all naming rules. These items may have been imported from another 442 source. Descriptive naming conventions apply to them. 443 444 In addition to the scope and authority rules needed to document descriptive naming conventions, prescriptive

447

445 conventions shall be documented by semantic, syntactic, lexical, and uniqueness rules. 446

− Semantic rules enable meaning to be conveyed. 448 449 − Syntactic rules relate items in a consistent, specified order. 450 451 − Lexical (word form and vocabulary) rules reduce redundancy and increase precision. 452 453 − A uniqueness rule documents how to prevent homonyms occurring within the scope of the naming 454 convention. 455 456 The examples in annexes A and B show how the names of each of the designatable items can be formed 457 from a set of items selected from sets of available terms for the naming convention. (The names of other 458 designatable items may be formed by rules based on those described in this part of ISO/IEC 11179.) The 459 names of these items can be developed from the names of the items from which they are composed, each 460 assigned meaning (semantics) and relative or absolute position (syntax) within a name. They may, but need 461 not, be delimited by a separator symbol. The names may be subject to lexical rules. An authority, e.g., a data 462 manager within a corporation or an approving committee for an international business sector naming 463 standard, should control the set or range of values of each item. 464 465 9.2 Scope principle 466

The scope of a naming convention specifies the range within which it is in effect. In terms of the MDR, the 467 scope of a naming convention may be as broad or narrow as the Registration Authority, or other authority, 468 determines is appropriate. The scope should document whether the naming convention is descriptive or 469 prescriptive. 470 471 The scope of each naming convention represented in the MDR shall be documented. 472 473 9.3 Authority principle 474

Identification of the authority that assigns names or enforces the naming convention is necessary for full 475 documentation of the naming convention. This may include the ownership of the namespace, reference to 476 terminology information such as an external glossary or thesaurus, or other source. 477 478 The Authority of each naming convention represented in the MDR shall be documented. 479 480 9.4 Semantic principle 481

Semantics concerns the meanings of name parts and possibly separators that delimit them. The set of 482 semantic rules documents whether or not names convey meaning, and if so, how. Name parts may be 483 derived from structure sets that identify relationships among (classify) members. See annexes A and B for 484 examples of semantic rule sets. 485 486 The semantic rules of each naming convention represented in the MDR should be documented. 487 488 9.5 Syntactic principle 489

Syntax specifies the arrangement of parts within a name. The arrangement may be specified as relative or 490 absolute, or some combination of the two. Relative arrangement specifies parts in terms of other parts, e.g., a 491 rule within a convention might require that a qualifier term must always appear before the part being qualified 492 appears. Absolute arrangement specifies a fixed occurrence of the part, e.g., a rule might require that the 493 property term is always the last part of a name. 494



495 The syntactic rules of each naming convention represented in the MDR should be documented. 496 497 See annexes A and B for examples of syntactic rule sets. 498 499 9.6 Lexical principle 500

Lexical issues concern the appearance of names: preferred and non-preferred terms, synonyms, 501 abbreviations, part length, spelling, permissible character set, case sensitivity, etc. The result of applying 502 lexical rules should be that all names governed by a specific naming convention have a consistent 503 appearance. 504 505 The lexical rules of each naming convention represented in the MDR should be documented. 506 507 See annexes A and B for examples of lexical rule sets. 508 509 9.7 Uniqueness principle 510

There may or may not be requirements for names to be unique within their scope. The uniqueness rules for 511 names represented in the MDR should be documented. 512 513 Uniqueness rules for names within naming conventions should be documented as well as rules for 514 uniqueness within namespaces. If two names emerge as identical as a result of the application of the other 515 rules, a rule for the differentiation of those names should be included. Examples include affixing prefixes or 516 suffixes, differing abbreviation conventions, etc. 517 518

10 Concept system relationship to names 519

10.1 Concepts as higher-level classes 520

In the ISO/IEC 11179-3 registry metamodel, the Concept class is a supertype to many designatable items that 521 can function as components of designated items and as templates for name parts. Annexes A and B describe 522 these relationships more fully. As subtypes of concepts, object class, property, value meaning, and 523 conceptual domain may all be one or more items in a Concept system, which are members of a Concept 524 class. 525

10.2 Concepts as classification system 526

Annex F of ISO/IEC 11179-3 describes the use of a Concept system to implement a classification scheme for 527 Representation Class. This model may be broadened to encompass the derivation of other name parts in a 528 naming convention. 529

A Concept system is registered with the designation appropriate for each individual part of a naming 530 convention. Within the Concept system, individual concepts are registered with designations that correspond 531 to each of the desired name terms. Relationships (associations) among concepts may be used to assist in 532 forming rules for relationships among name parts. Annex E of ISO/IEC 11179-3 describes examples of 533 correspondences among the ISO/IEC 11179-3 metamodel and concepts from other notations. 534

The Classifiable Item class is used to classify the data elements or other registry entities by associating them 535 with the appropriate concept in the Concept system. Naming convention conformance is achieved by 536 associating the designation with the rules residing in the Naming Convention and Namespace classes. 537

538

539



540



Annex A 541 (informative) 542

543 Example naming conventions for names within an MDR registry 544

A.1 General 545 546

The rules are derived from the principles described in clause 9. Examples are included. They show the 547 formation of names within registries, and may be applied to the development of names within contexts at 548 the discretion of the subject area authority. The complete process produces a data element name; other 549 designatable item names are developed during the process. 550

551 These examples are written as American English. Users of other languages may specify different or 552 additional semantic, syntactic and lexical rules as needed to customize naming conventions to their 553 languages. For example, a rule citing an authority for spelling words within terms might be added to the 554 lexical rules. Annex B shows examples in Asian languages. 555

556 557 558 A.2 Semantics of name parts 559

560 Name parts consist of discrete terms. The terms in this annex are derived from designatable items and other 561 items in the MDR metamodel described in ISO/IEC 11179-3. They may be derived from concept system 562 items as described in clause 10. Name parts are designated by names ending with "term" to differentiate 563 them from the entities in Part 3 from which they are derived. These are: object class terms, property 564 terms, and representation terms. These terms are presented as examples of the application of semantic 565 principles to name formation. Qualifier terms are used to further differentiate terms as necessary. 566

567 Object class term 568

569 In the MDR metamodel, an object class is a set of ideas, abstractions or things in the real world that 570 are identified with explicit boundaries and meaning, and whose properties and behaviour follow the same 571 rules. Each object class has a name. The registration of object classes in a registry is optional, but if used, 572 the set of actual and potential object class names provides a taxonomy of object class terms. 573

574 An object class term may be a part of the name of the designatable items concept, conceptual domain, 575 data element concept and data element, and represents an activity or object in a context. Use of a 576 modelling methodology, as for instance a model described using OWL and documented as a Concept 577 System in the MDR, is a way to locate and discretely place designatable items in relation to their higher-578 level model entities. 579

580 Models provide one kind of classification scheme for designatable items. Designatable items that contain 581 object classes may be identified with their related modelling entities by mapping the object class term to the 582 model entity name. 583

584 In the data element names 585 586

Employee Last Name 587 588

Cost Budget Period Total Amount 589 590

Tree Height Measure 591 592

Member Last Name 593 594 the terms Employee, Cost, Tree, and Member 596

are object class terms. 595



597 Object class terms may be used by themselves as concept and conceptual domain names. 598

599 Property term 600

601 In the MDR metamodel, a property is a quality common to all members of an object class. Each property 602 has a name. The registration of properties in a registry is optional, but if used, the set of actual and 603 potential property names provides a taxonomy of property terms. 604

605 A set of property terms may be composed from a set of name parts in a property taxonomy. This set 606 should consist of terms that are discrete (the definition of each does not overlap the definition of any 607 other), and complete

612

(taken together, the set represents all information concepts required for the 608 specification of designatable items which use properties, such as data elements, data element concepts and 609 value domains). These terms may be taken from the same Concept system as the object class terms or 610 may be derived from a separate structure set. 611

In the data element names 613 614

Employee Last Name 615 616

Cost Budget Period Total Amount 617 618

Member Last Name 619 620

Tree Height Measure 621 622

the terms Last Name, Total Amount, and Height 624

are properties. 623

Using terms from two structure sets provides a complementary way of categorization. Both object class 625 and property terms of data element concepts and data elements are utilized to form a name that contains 626 vital information about these designatable items, and also excludes extraneous or irrational elements that 627 may be introduced when no conventions are employed. Data element concept names may be 628 composed by combining object class terms and property terms. 629

630 Representation term 631

632 A representation term may be a part of an designatable item name that describes the form of 633 representation of an designatable item that includes representation: data elements and value domains. 634 Each term may be developed from a controlled word list or taxonomy. In the MDR metamodel, a 635 Representation Class is the classification of types of representation. Each representation class has a 636 name. The registration of representation classes in a registry is optional, but if used, the set of actual and 637 potential representation class names provides a taxonomy of representation class terms. Annex F of 638 ISO/IEC 11179-3 discusses using a Representation Class classification scheme as a concept system. 639

640 Representation terms categorize forms of representation such as 641

642 - Name - Amount 643

644 - Measure - Number … 645

646 - Quantity - Text 647

648 This term describes the form of the set of valid values of an designatable item which includes 649 representation. Often, the representation term may be redundant with part of the property term. When this 650 occurs, one term or part of one term may be eliminated in a structured name. This can be established 651 as a rule in a naming convention. 652

653 Using the above rules, a data element describing a measurement of the height of a tree would have the 654 data element name Tree Height Measure. The word Measure is the data element’s representation term. 655



However, a data element that describes the last name of a person would have the data element name of 656 Person Last Name Name. The second word Name is the data element’s representation term. However, to 657 promote clarity, one occurrence of the redundant word is removed. 658

659 660

Qualifier term 661 662

Qualifier terms may be attached to object class terms, property terms, and representation terms if 663 necessary to distinguish one data element concept, conceptual domain, data element, or data value domain 664 from another. These qualifier terms may be derived from structure sets specific to a context. In the rules for 665 a naming convention, a restriction in the number of qualifier terms is recommended. 666

667 For example, in the data element name 668

669 Cost Budget Period Total Amount 670

671 the term Budget Period

673 is a qualifier term. 672

NOTE 1: Limitations in the form of permitted terms of qualifiers help reduce redundancy and increase incidence of data 674 reuse by eliminating synonyms. This applies also to object class terms, property terms, and representation terms. A 675 mechanism such as a thesaurus of terms facilitates this effort. 676 677 NOTE 2: Because of a change to the cardinality of the relationship between Data Element Concept and Conceptual 678 Domain in 11179 Part 3 Edition 3, the qualifier term construct is now of enhanced importance. 679

680 Semantics of separators 681

682 Various kinds of punctuation connect name parts, including separators such as spaces and hyphens, 683 and grouping symbols such as parentheses. These may have: 684

685 a) No semantic meaning. A naming rule may state that separators will consist of one blank space or 686

exactly one special character (for example a hyphen or underscore) regardless of semantic relationships 687 of parts. Such a rule simplifies name formation. 688

689 b) Semantic meaning. Separators can convey semantic meaning by, for example, assigning a 690

different separator between words in the qualifier term from the separator that separates words in the 691 other part terms. In this way, the separator identifies the qualifier term clearly as different from the rest of 692 the name. 693

694 For example, in the data element name 695

696 Cost_Budget-Period_Total_Amount 697

698 the separator between words in the qualifier term is a hyphen; other name parts are separated 699 by underscores. 700

701 Some languages, such as German and Dutch, commonly join grammatical constructs together in a 702 single word (resulting in one word which in English or French might be a phrase consisting of nouns and 703 adjectives). These languages could use a separator that is not a break between words, such as a 704 hyphen, space or underscore, but instead capitalize the first letter of each name part within a single word 705 (sometimes called CamelCase). This naming convention is also commonly used in programming languages 706 such as C++ and Java. 707

708 Asian languages often form words using two characters which, separately, have different meanings, but 709 when joined together have a third meaning unrelated to its parts. This may pose a problem in the 710 interpretation of a name because ambiguity may be created by the juxtaposition of characters. A possible 711 solution is to use one separator to distinguish when two characters form a single word, and another when 712 they are individual words. 713

714



The following table indicates which name parts are combined to form administrative item names. See A.5 715 for examples of designatable items with related names. 716

717 718 719 720

Table A.1 — Relationship of name parts to designatable item names 721 722 Conceptual

Domains Data Element

Concepts

Data Elements

Value Domains

Object Class Terms X X X

Property Terms X X

Representation Terms

X

X

Qualifier Terms X X X X 723 A.3 Example of complete rule sets for naming conventions 724

725 These rules implement the semantics described above and combine them with other rules based on 726 principles from clause 9. They may be documented in the Naming Convention and Namespace classes of 727 the metamodel. 728

729 Example rule sets for registry names 730

731 Name: MDR Registry Name 732

Context: Registry preferred name 733

Scope: MDR Example Registry 734

Authority: ISO/IEC SC 32/WG 2; XYZ Namespace Abbreviation List 735

Semantic rules: 736 737

a) Object classes represent things of interest in a universe of discourse that may, for instance, be found in 738 a model of that universe. 739

740 EXAMPLE Cost 741

742 b) One and only one object class term shall be present. 743

744 c) Property terms shall be derived from the property system structure set and represent a quality of the 745

object class. 746 747

EXAMPLE Total Amount 748 749

d) One and only one property term shall be present. 750 751

NOTE The combination of object class term and property term forms the names for data element concepts. 752 753

e) Qualifiers may be derived as determined by the subject area authority and will be added as needed 754 to make the name unique within a specified context. The order of the qualifier terms is not significant. 755 Qualifier terms are optional. 756

757 EXAMPLE Budget Period 758

759 f) The representation of the valid value set of a data element or value domain is described by the 760

representation term. 761



762 g) One and only one representation term shall be present. 763

764 EXAMPLE Amount 765

766 NOTE Representation terms, usually with added qualifiers, form value domain names. 767

768 769 770

Syntactic rules: 771 772

a) The object class term shall occupy the first (leftmost) position in the name. 773 774

b) Qualifier terms shall precede the part qualified. The order of qualifiers shall not be used to differentiate 775 names. 776

777 c) The property term shall occupy the next position. 778

779 d) The representation term shall occupy the last position. If any word in the representation term is 780

redundant with any word in the property term, one occurrence will be deleted. 781 782

EXAMPLE Cost Budget Period Total Amount 783 784

Lexical rules: 785 786

a) Nouns are used in singular form only. Verbs (if any) are in the present tense. 787 788

b) Name parts and words in multi-word terms are separated by spaces. No special characters are allowed. 789 790

c) All words in the name are in mixed case. The rules of “mixed case” are defined by the RA. These rules 791 may by different for different parts of the designatable item name (object class, property, representation 792 class). 793

794 d) Abbreviations, acronyms, and initialisms are allowed. Use the abbreviations in the XYZ Namespace 795 Abbreviation List. 796

797 EXAMPLE Cost Budget Period Total Amount 798

799 NOTE: These rules may not apply to all languages. See the notes in Annex B for specific exceptions to 800 Chinese. 801 802 Uniqueness rule: 803

804 All names in each language shall be unique within this context. 805

806 807 808 A.4 Example rule sets for data element names within XML tags 809

810 "XML namespaces provide a simple method for qualifying element and attribute names used in Extensible 811 Markup Language documents by associating them with namespaces identified by IRI references." 812 [ Namespaces in XML 1.1, W3C Recommendation 16 August 2006] This is done by assigning a prefix to the 813 element and attribute names. The following example shows how this rule may be applied within a naming 814 convention. 815

816 These rules are derived from the principles described in Clause 9. The first example differs from the 817 rules described above only in the application of XML-specific lexical restrictions. 818

819 Name: XML tag name 820

821 Context: XML schema for reports 822



823 Scope: All element and attribute names in XML DTD's 824

825 Authority: XML data administrator 826

827 828

829 830 831 832

Semantic rules: 833 834

a) Object classes represent things of interest in a universe of discourse that may, for instance, be found in 835 a model of that universe. 836

837 EXAMPLE Cost 838

839 b) One and only one object class term shall be present. 840

841 c) Property terms shall be derived from the property system structure set and represent a quality of the 842

object class. 843 844

EXAMPLE Total Amount 845 846

d) One and only one property term shall be present. 847 848

e) Qualifiers may be derived as determined by the subject area authority and will be added as needed 849 to make the name unique within a specified context. The order of the qualifier terms is not significant. 850 Qualifier terms are optional. 851

852 EXAMPLE Budget Period 853

854 f) The representation of the valid value set of the data element is described by the representation term. 855

g) One and only one representation term shall be present. 856

EXAMPLE Amount 857 858

Syntactic rules: 859 860

a) The object class term shall occupy the first (leftmost) position in the name. 861 862

b) Qualifier terms shall precede the part qualified. The order of qualifiers shall not be used to differentiate 863 data element names. 864

865 c) The property term shall occupy the next position. 866

867 d) The representation term shall occupy the last position. If any word in the representation term is 868

redundant with any word in the property term, one occurrence will be deleted. 869 870

EXAMPLE Cost Budget Period Total Amount 871 872

Lexical rules: 873 874

a) Nouns are used in singular form only, unless the concept itself is plural. Verbs (if any) are in the 875 present tense. 876

877 b) Name parts are separated by capitalizing the first character of the second thru nth word. 878

c) All words in the name are in mixed case. 879



d) Abbreviations, acronyms, and initialisms are allowed only when used normally within business terms. 880

e) Words contain letters and numbers only. 881

EXAMPLE CostBudgetPeriodTotalAmount 882 883 884 885 886

Uniqueness rule: 887 888

All names shall be unique within a DTD. 889 890

Usage Examples 891 892

In this example, a data element name is used in an XML element tag 893 894

< !ELEMENT CostBudgetPeriodTotalAmount (#PCDATA) > 895 896

An additional example can be developed to show the use of prefixes to identify the namespace to which an 897 XML schema element or attribute is assigned. 898 899 An additional semantic rule is defined: 900 901

h) Not more than one namespace indicator shall be present. 902

An additional syntactic rule is defined: 903

e) If a namespace indicator is used, it shall precede all other terms. 904

And an additional lexical rule is defined: 905

f) A namespace indicator is in lowercase and is separated from the other terms by a colon. 906

Example of an XML name using a namespace indicator: 907

< !ELEMENT acct:CostBudgetPeriodTotalAmount > 908 909 The prefix can also serve as a scoped identifier to differentiate items within a DTD, to enforce the uniqueness 910 rule. 911

912 913 914 A.5 Attributed example of a data element 915

916 The table below presents an attributed example of a data element with all designatable item 917 derivations named. Specifically, this data element is derived from: 918

919 data element concept: Country Identifier 920

composed of occurrences of the 921

conceptual domain: Country 922

and its 923 924

value domain: ISO English-Language Country Short Name. 925 926

Three names are provided for this data element example: 927 928



(a) Country Mailing Address Name, the registry name: 929 930 (b) Country.Mailing_Address.Name, a name that appears in an application system, the convention for 931 which requires separators with semantic meaning, 932 933 (c) addr:CountryMailingAddressName, an XML Schema name, which employs a prefix identifying the 934 namespace in which the name is included. 935

936 Semantic, syntactic and lexical rules are documented using the Naming Convention class of the metamodel. 937

938

939

Metadata Attribute Name Attribute Value 1 Data Element Definition a Data Element (DE)

Definition Context Registry

DE Definition The name of the country where a mail piece is delivered.

b DE Definition Context Facility Data System DE Definition The name of a country where the addressee is located. c DE Definition Context XML Address Schema DE Definition The name of the country in an address. 2 Permissible Values and Value Domain Permitted Values (each

PV) All English-language short country names from ISO 3166, matched with value meanings. (recorded as: Afghanistan, Albania,....., Zimbabwe)

PV Begin Date (each PV) 19970110 PV End Date (each PV) (Not applicable) Value Domain (VD)

Context Registry

VD Entry Name ISO English-Language Country Short Name VD Definition All short, ISO-recognized English-language names of all countries. VD Description (Not applicable) VD Entry Identifier {RAI} 5678:1 Datatype CHARACTER VARYING Datatype Scheme

Reference ANSI ISO SQL

Maximum Characters 44 Format (Not applicable) Unit of Measure (Not applicable) Precision (Not applicable) VD Origin ISO 3166-1:2006 VD Explanatory Comment The value domain includes only the subset of names that designate countries; it

does not include names of territories. 3 Representation Class (RC) Classification System Attributes RC Classification System

Name ISO/IEC 11179-3 Annex F Specification

Representation Class Term

Name



Metadata Attribute Name Attribute Value Representation Class

Qualifier Short

4 Data Element Name (Designation) and Identifier a DE Name Country Mailing Address Name DE Name Context Registry Naming Convention (NC)

Name Registry Preferred Naming Convention

NC Rules <Rule set, excluding uniqueness rules> Namespace (NS)

Authority Registry Administrator

NS Uniqueness (one name per item)

One name per item is true

NS Uniqueness (one item per name)

One item per name is true

NS NC Obligation All names in this NS must conform to this NC. b DE Name Country.Mailing_Address.Name DE Name Context Facility Data System NC Name Facility Data System Naming Convention NC Rules <Rule set, excluding uniqueness rules> Namespace (NS)

Authority Facility Data System Administrator





NS NC Obligation All names in this NS must conform to this NC. c DE Name addr:CountryAddressMailingName DE Name Context XML Address Schema NC Name XML Schema Naming Convention NC Rules <Rule set, excluding uniqueness rules> Namespace (NS)

Authority System XYZ Administrator





NS NC Obligation All names in this NS must conform to this NC. NS Prefix addr: NS Scheme Reference http://www.w3.org/TR/1999/REC-xml-names-19990114/ DE Entry Identifier {RAI} 5394:1 5 Other Data Element Attributes DE Example Denmark DE Origin Application system DE Comment This data element is required for delivery of mail outside the country of origin. Submitting organization Office of Enforcement and Compliance Assurance

http://www.w3.org/TR/1999/REC-xml-names-19990114/�



Metadata Attribute Name Attribute Value Stewardship Contact Facility Data Systems Administrator 6 Data Element Concept and Conceptual Domain Data Element Concept

(DEC) Context Registry

DEC Name Country Identifier DEC Definition An identifier for a primary geopolitical entity of the world. Object Class Country Property Identifier DEC Entry Identifier {RAI}12468:1 Conceptual Domain (CD)

Context Registry

CD Name Country CD Definition The primary geopolitical entities of the world. CD Entry Identifier {RAI} 2468:1 CD Origin ISO 3166:1 Value Meaning (for each

VM) The primary geopolitical entity known as <China>

VM Begin Date (for each VM)

19970110

VM End Date (for each VM)

(Not applicable)

VM Identifier (for each VM)

<Assigned by system as 1001…1230: one to each VM>

7 Concept Scheme Examples

Classification Values for Concept Type

Keyword Country, Address, Mailing Group Mailing Address Object Address, Country Concept Scheme

Membership Level Specialization

8 Registration and Administrative Status DE Registration Status Recorded DE Administrative Status In Quality Review VD Registration Status Standard VD Administrative Status Final DEC Registration Status Recorded DEC Administrative

Status In Quality Review

CD Registration Status Standard CD Administrative Status Final 940

941



Annex B 942 (informative) 943

944 Example naming conventions for Asian languages 945

These rules are derived from the principles in clause 9. Examples described here are the same as in annex A. 946

Asian language often form words using two characters which, separately, have different meanings, but when 947 joined together have a third meaning unrelated to its parts. This may pose a problem in the interpretation of a 948 name because ambiguity may be created by the juxtaposition of characters. 949

These examples are written as American English, Japanese, Korean and Chinese. 950

951

Semantic rules: 952

a. Object classes represent things of interest in a universe of discourse that may, for instance, be found in a 953 model of that universe. 954

Example: 955

-English: Cost 956

-Chinese: 成本 957

-Japanese: 経費 958

-Korean: 비용 959

960

b. One and only one object class term shall be present. 961

c. Property terms shall be derived from the property system structure set and represent the category of the 962 data. 963

Example: 964

-English: Total Amount 965

-Chinese:总金额 966

-Japanese: 合計金額 967

-Korean: 총합계 968

969

d. One and only one property term shall be present. 970

Note: The combination of object class term and property term forms the names for data element concepts. 971



e. Qualifiers may be derived as determined by the subject area authority and will be added as needed to 972 make the name unique within a specified context. The order of the qualifier terms is not significant. 973 Qualifier terms are optional. 974

Example: 975

-English: Budget Period 976

-Chinese: 预算期间 977

-Japanese: 予算期間 978

-Korean: 예산기간 979

980

f. The representation of the valid value set of a data element or value domain is described by the 981 representation term. 982

g. One and only one representation term shall be present. 983

Example: 984

-English: Amount 985

-Chinese:金额 986

-Japanese: 金額 987

-Korean: 합계 988

989

Note: Representation terms, usually with added qualifiers, form value domain names. 990

991

Syntactic rules: 992

a. The object class term shall occupy the first (leftmost) position in the name. 993

b. Qualifier terms shall precede the part qualified. The order of qualifiers shall not be used to differentiate 994 name. 995

c. The property term shall occupy the next position. 996

d. The representation term shall occupy the last position. If any word in the representation term is redundant 997 with any word in the property term, one occurrence will be deleted. 998

Example: 999

-English: Cost Budget Period Total Amount 1000

-Chinese:成本预算期间总金额 1001

-Japanese: 経費予算期間金額合計 or 経費・予算期間・金額合計 1002

-Korean: 예산기간비용합계 1003



1004

Lexical rules: 1005

a. Nouns are used in singular form only. Verbs (if any) are in the present tense. 1006

Note: In Chinese and Japanese, this rule shall not be applied because of no plural form of nouns and no 1007 distinction of verb tense. 1008

b. Name items and words in multi-word terms are separated by spaces. No special characters are allowed. 1009

Note: In Chinese and Japanese, as multi-word terms are naturally expressed without spaces, any characters 1010 shall not be allowed or a dot character may be used for separating those terms. 1011

c. All words in the name are in mixed case. 1012

Note: In Chinese, this rule shall not be applied as there is no mixed case. In Japanese, all words in the name 1013 are in mixed case of Zen-kaku and Han-kaku. 1014

d. Abbreviations, acronyms, and initialisms are allowed. 1015

Example: 1016

-English: Cost Budget Period Total Amount 1017

-Chinese: 成本预算期间总金额 1018

-Japanese: 経費予算期間金額合計 or 経費・予算期間・金額合計 1019

-Korean: 예산기간비용합계 1020

Note: This rule shall not be applied as there are no abbreviations, acronyms, or initialisms. 1021

1022

Uniqueness rule: 1023

All names in each language shall be unique within this context. 1024

1025

1026



1027



Annex C 1028 (informative) 1029

1030 Concordance table for item names 1031

PART 5 ITEM PART 5 CLAUSE PART 3 ITEM PART 3 CLAUSE

concept 1,10 Concept class 9

data element 1

Data_Element class 11.5

data element concept 1 Data_Element_Concept class 11.2

conceptual domain 1 Conceptual_Domain class 11.3

value domain 1 Value_Domain class 11.3

designatable item 1,4,5,7,8,9,10,A Designatable_Item class 7.3

designation of designatable item

1,6.8.10,A attribute of Designation class: sign 7.3

name 1,6,7,8,9,10,A,B attribute of Designation class: sign 7.3

naming convention 1,4,6,7,8,9,10,A,B Naming_Convention class 7.3

scope rule 4,8,9,A,B attribute of Naming_Convention class: scope_rule

7.3

authority rule 4,8,9,A,B attribute of Naming_Convention class: authority_rule

7.3

semantic rule 4,8,9,A,B attribute of Naming_Convention class: semantic_rule

7.3

syntactic rule 4,8,9,A,B attribute of Naming_Convention class: syntactic_rule

7.3

lexical rule 4,8,9,A,B attribute of Naming_Convention class: lexical_rule

7.3

uniqueness rule 4,8,9,A,B attributes of Namespace class: one_name_per_item_indicator; one_item_per_name_indicator

7.3



identifier 5 attribute of Scoped_Identifier class: identifier

7.2

attached item 9 Attached_Item class 8.1

Concept class 10 Concept class 9

Concept system 10 Concept_System class 9

object class 10,A,B Object_Class class 11.2

property 10,A,B Property class 11.2

value meaning 10,A,B Value_Meaning class 11.3

conceptual domain 10,A,B Conceptual_Domain class 11.3

Representation Class 10 Implementation of Concept_System and Classifiable_Item classes

Annex F

Classifiable Item class 10 Classifiable_Item class 9.2

1032

Items in the table are listed in the order of their appearance in Part 5. 1033



Bibliography 1034

[1] ISO 1087-1:2000, Terminology work-Vocabulary-Part 1: Theory and application 1035

information technology -metadata registries (mdr) - part 5...

Documents