GB/T 18391.1-2026Information technology - Metadata registries (MDR) - Part 1: Framework (English PDF)

Foreword

This document complies with the provisions of GB/T 1.1-2020 "Standardization Work Guidelines Part 1: Structure and Drafting Rules of Standardization Documents".

Drafting.

This document is Part 1 of GB/T 18391 "Metadata Registry System for Information Technology (MDR)", which has been published.

The following section.

---Part 1: Framework;

---Part 2: Classification;

---Part 3: Metamodel of Public Facilities in the Registration System;

---Part 4: Formation of Data Definitions;

---Part 5: Naming and Identification Principles;

---Part 6: Registration.

This document replaces GB/T 18391.1-2009 "Information Technology Metadata Registry System (MDR) Part 1: Framework", and is consistent with...

Compared with GB/T 18391.1-2009, apart from structural adjustments and editorial changes, the main technical changes are as follows.

---Chapter 7 provides an overview of ISO/IEC 11179, including the original six parts, and adds sections on Parts 30 and 31.

Introduction to Parts 32, 33, 34, and 35;

---A new Chapter 8 has been added, which expands the relationship between this document and relevant standards, mainly including.

- 8.1 Interoperability Metamodel;

- 8.2 Metadata Registration System Module;

- 8.3 Achieve consistency of metadata registration system content;

- 8.4 Metadata interoperability and binding;

- 8.5 Metadata Concepts and Applications;

- 8.6 Format of data element values;

- 8.7 Gender Code;

- 8.8 General Data Types;

- 8.9 General Logic;

- 8.10 Top-level ontology.

This document is equivalent to ISO/IEC 11179-1:2023 "Information technology metadata registry system (MDR) Part 1: Framework".

The following minimal editorial changes have been made to this document.

---Added notes (see 5.3, 7.7, 8.1.2, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.2, 8.3.2, 8.3.3, 8.6, 8.8, 8.9).

Please note that some content in this document may involve patents. The issuing organization of this document assumes no responsibility for identifying patents.

This document was proposed and is under the jurisdiction of the National Information Technology Standardization Technical Committee (SAC/TC28).

Introduction

GB/T 18391 describes the semantics of data, the representation of data, and the registration of data descriptions. Through these descriptions, semantics can be found...

Accurate understanding and useful description of data.

The purpose of GB/T 18391 is to promote.

---Standard description of data;

---A consistent understanding of data within and between organizations;

---Reuse and standardization of data across time, space, and application;

---Data collaboration and standardization within and between organizations;

---Management of data components;

---Reuse of data components.

Each part of GB/T 18391 is designed to address one aspect of the above-mentioned requirements, see Chapter 7.

GB/T 18391 is proposed to consist of twelve parts.

---Part 1: Framework. This section presents the overall framework of this series of standards, including data elements, value ranges, data element concepts, conceptual domains, and concepts and generalizations.

It introduces fundamental concepts such as the concept system, providing context that connects the various parts.

---Part 2: Classification. This section elaborates on the meaning and significance of classification, and explains how to apply a classification scheme to other aspects of the registration system.

Classification standards.

---Part 3: Metamodel of the Registration System's Public Facilities. The Metadata Registry (MDR) is defined using the Unified Modeling Language (UML).

The core metamodel.

---Part 30: Basic Metadata Attributes. Describes the basic attributes of data elements and related metadata in order to avoid issues that may arise from a lack of complete metadata.

Used according to the registration system.

---Part 31: Data Specification Registration Metamodel. Provides extensions to the Metadata Registry (MDR) system for registering descriptive data elements.

Metadata for related concepts.

---Part 32: Conceptual System Registration Metamodel. Provides extensions to the Metadata Registry (MDR) system for registering descriptive conceptual entities.

Metadata of the system.

---Part 33: Dataset Registration Metamodel. Provides extensions to the Metadata Registry (MDR) system for registering descriptive datasets, Metadata of a dataset.

---Part 34: Computable Data Registry Metamodel. Provides extensions to the Metadata Registry (MDR) system for registering computable data descriptions.

Metadata of the computational data.

---Part 35: Model Registration Metamodel. Provides extensions to the Metadata Registry (MDR) system for registering descriptive models and related metadata.

Metadata of the metamodel.

---Part 4: Forming Data Definitions. Provides guidance on how to develop clear data definitions.

---Part 5: Naming and Identification Principles. These guidelines provide direction on how to assign names to managed items.

---Part 6: Registration. Provides information on assigning a unique identifier to each data component and how registration applicants can register with the registration authority.

(RA) Operation Guide for Registering Data Components.

Descriptive data is typically referred to as metadata. Metadata can describe books, telephone numbers, data, etc. GB/T 18391 focuses on metadata.

It is defined as descriptive data.

A metadata registry (MDR) is a system used to maintain a metadata database. Registration is one of the implementable functions of this system. Note the registration process serves three main purposes. identification, provenance, and quality control. Identification involves assigning a unique identifier to each registered object (within the registration system).

Symbols are used to implement this; the source indicates the origin of the metadata and the object it describes; quality control ensures that the metadata fulfills its assigned task.

MDR can be used to manage the semantics of data. Understanding data is fundamental to designing, harmonizing, standardizing, applying, reusing, and exchanging data.

The foundation. The basic model for MDR is designed to capture all the fundamental components of data semantics, regardless of the application or professional domain.

Typically, MDRs are organized so that application designers can determine if suitable alternatives exist within existing MDRs.

If a new object is confirmed to be needed, it is encouraged to derive it by appropriately modifying the existing description to avoid unnecessary differences caused by similar descriptions.

The registration process can also identify whether two or more management items describe the same object. More importantly, it can reveal discrepancies in one or more aspects.

Whether management items with significant differences use similar or identical names.

In MDR, the meaning of an object is given through its name, definition, data type, and related objects. Because...

Names and definitions convey only limited information about an object; therefore, the scope of their meaning is limited. In a registration system, the object and its semantics...

The relationships between related objects will provide additional information, and this additional information is related to the number of semantically related objects.

A metadata registry system conforming to GB/T 18391 can describe a wide variety of data. In fact, the attributes described in GB/T 18391...

These are data elements, which can be registered in the GB/T 18391 metadata registration system. Furthermore, any set of descriptors or metadata attributes can be decrypted.

It is interpreted as a data element and registered in the metadata registration system.

This will produce two main results.

---A metadata registry can describe itself;

---GB/T 18391 does not define the hierarchy or level of metadata.

Therefore, GB/T 18391 is a universal descriptive framework applicable to data of any type, organization, and purpose.

GB/T 18391 does not address other data management needs, such as data models, application specifications, program code, project planning, business planning, and business processes.

These needs should be addressed elsewhere, such as service policies.

The growth of data processing and electronic data interchange applications largely depends on the accuracy, reliability, controllability, and usability of data in databases.

Verification. One of the prerequisites for the correct and appropriate use and interpretation of data is that the users and owners of the data understand its meaning and description.

There should be a consistent understanding of features (such as representations). To reach a consensus, several basic attributes should be defined.

The basic attributes specified here are suitable for defining and standardizing the content of the data dictionary, and are also applicable to the exchange between various sets of management items.

Reference. The term "basic" in "basic attributes" means that these attributes are commonly required for the complete specification of managed items, to ensure they are appropriate.

Used for various functions, such as.

---Design of information processing systems;

---Data retrieval from the database;

---EDI message design for data exchange;

---Maintenance of the metadata registration system;

---Data Management;

---Dictionary design;

---Dictionary management;

---Application of information processing systems.

The term "basic" also implies that they are independent of any of the following.

---Application Environment;

---The function of the object described by the management item;

---Abstract layer;

---Grouping of managed items;

---Methods for designing information processing systems or data exchange messages;

---MDR.

"Basic" does not mean that the attributes specified in GB/T 18391 are required in all cases. These basic attributes are divided into.

There are several types. required, conditionally required, and optional.

Information Technology Metadata Registry (MDR) Part 1: Framework

1 Scope

This document provides a method for understanding and relating the various parts of ISO/IEC 11179, and provides a conceptual understanding of metadata and metadata registration.

The system's foundation. This document also describes other standards, technical specifications, and technical reports from ISO/IEC 11179 and JTC1/SC32.

relation.

In all parts of ISO/IEC 11179, metadata specifically refers to the description of data and does not include general processing of metadata.

Note. JTC1/SC32 is the first Joint Technical Committee (JTC1) under the International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) for Data Management and...

Technical Committee on Exchange (SC32).

2 Normative references

The contents of the following documents, through normative references within the text, constitute essential provisions of this document. Dated citations are not included.

For references to documents, only the version corresponding to that date applies to this document; for undated references, the latest version (including all amendments) applies.

This document.

Note. GB/T 10112-2019 Terminology Working Principles and Methods (ISO 704:2009, IDT) Note. GB/T 15237-2025 Terminology work and scientific terminology (ISO 1087:2019, IDT)

3 Terms, Definitions and Abbreviations

The terms and definitions defined in ISO 704 and ISO 1087, as well as the following terms and definitions, apply to this document.