ISO/IEC 11179-7:2019 情報技術—メタデータレジストリ（MDR）—パート7：データセット登録のメタモデル | ページ 3

Introduction

Many data sets are now generally available. These may be part of a government-led open data initiative, or may be data sets that are used within and across organizations for commercial, scientific or academic purposes.

There is a requirement for metadata about these data sets to be readily available to enable the consistent and appropriate use of data and information, and to prevent duplication of work. Having an enhanced Metadata Registry where metadata that describes data sets is registered will facilitate the discovery of appropriate data sets.

In ISO/IEC 11179-3:2013, Clauses 5 to 11 the structure of a Metadata Registry is specified in the form of a conceptual data model. The Metadata Registry is used to keep information about data elements and associated concepts, such as “data element concepts”, “conceptual domains” and “value domains”. Generically, these are all referred to as “metadata items”. Such metadata are necessary to clearly describe, record, analyse, classify and administer data. This document provides a specification of the extensions to the registry metamodel specified in ISO/IEC 11179-3:2013, Clauses 5 to 11 to enable the registration of metadata about datasets.

When considering data and metadata, it is important to distinguish between types of data/metadata, and instances of these types. ISO/IEC 11179-3:2013, Clauses 5 to 11 specifies the types of metadata objects that form the structure of a basic Metadata Registry. Clause 5 specifies the types of metadata objects that form an extension to that structure so that the whole structure provides facilities to keep information about data sets. A Metadata Registry will be populated with instances of these metadata objects (metadata items), which in turn define, for example, types of data in an application database, or, in the case of this document, data sets that are held elsewhere. Such data sets could, for example, be made available over the internet or be included as a table within a word processing document.

The facilities described in this document, together with those described in ISO/IEC 11179-3:2013, Clauses 5 to 11 provides the ability to record the following data set metadata:

• one or more unique identifiers for the data set;
• the designation or title of the data set;
• a definition or description of the data set that provides sufficient detail to enable a user to quickly understand whether this data set is of interest;
• the date the data set was issued and, if appropriate, the date that subsequent versions of the data set were, or will be, issued;
• the access level and rights associated with the data set;
• the provenance of the data set, i.e., information about the place and time of the origin of the data set, its ownership and the method of the generation of the set;
• a set of keywords or tags that help to explain the data set;
• the language or languages used to describe the data set;
• the temporal and spatial coverages of the data set;
• the accrual periodicity of the data set, i.e., the frequency at which new, revised or updated versions of the data set are made available;
• the details of the distributions of the data set, including the identifier, the title, a description, the media type or file format, the size, the issue date, languages, access level and rights and access and download URLs;
• annotations drawn from a concept system, such as an ontology, to describe the theme or category of the data set or the collection of data sets;
• the details of any contexts, such as a programme, project or business area that use the data set;
• the details of any quality assessments made in respect of the data set;
• any additional descriptions of the data set, including:
  • any data elements that are already registered that are included in the data set;
  • any information models that describe the structure of the information in the data set;
  • any documents which describe aspects of the data set, such as technical information about the data set and/or developer documentation such as a graphical representation of the data model of the data set;

• the details of any superset/subset hierarchies containing the data set;

• the details of any replacement data set if this data set is superseded;

• the details of any collection of data sets of which this data set is a part, including the identifiers, the designation or title, a definition or description, issue dates, languages, access level, rights, the spatial coverage, the provenance and any quality assessments of the collection.