ISO/IEC 11179-3:2013 - 信息技术元数据注册表（MDR）第3部分：注册元模型和基本属性

需积分: 13 183 浏览量更新于2024-07-15 收藏 4.36MB PDF 举报

"ISO/IEC 11179-3:2013是关于元数据注册表（Metadata Registry, MDR）的标准，它详细定义了元数据注册的第三部分，即注册元模型和基本属性。这个标准提供了一个概念性的数据模型，用于描述MDR的结构，但不依赖于特定的技术实现，如数据库管理系统、系统接口或计算平台。它并不直接应用于实际数据在通信和信息处理系统中的使用。" ISO/IEC 11179系列标准是一个全球广泛采用的框架，旨在规范元数据的定义、分类、管理和存储。元数据是关于数据的数据，可以提供关于信息资产的上下文、质量、来源和结构等关键信息。这个标准的第三部分，即ISO/IEC 11179-3，是整个标准的核心，因为它定义了元数据注册的模型和核心属性。元数据注册表（MDR）是存储和管理元数据的系统，它允许组织对数据进行标准化和规范化，从而提高数据的质量、一致性和可发现性。ISO/IEC 11179-3中的注册元模型涵盖了元数据的生命周期管理，包括创建、审批、发布、更新和退役等阶段。它还定义了元数据的基本属性，这些属性是描述元数据的关键元素，例如元数据的名称、定义、类型、关联关系、版本信息等。标准中的模型图使用统一建模语言（UML）来表达，但重要的是要注意，ISO/IEC 11179-3并不指定任何特定的实现技术。这意味着该标准可以适应各种不同的IT环境，可以根据实际需求和现有基础设施进行灵活的实施。元数据注册的实施可以帮助组织实现以下目标： 1. 数据治理：通过定义和管理元数据，确保数据的一致性和准确性。 2. 数据发现：元数据可以帮助用户快速找到所需的信息，提高工作效率。 3. 数据互操作性：通过标准化元数据，不同系统之间的数据交换变得更加容易。 4. 遵循法规：元数据注册可以帮助组织满足法规遵从性要求，如记录数据来源和处理历史。 ISO/IEC 11179-3的范围包括元数据注册的结构和基础属性，为组织提供了一个全面的框架来建立和维护有效的元数据管理体系。通过遵循这个标准，组织可以提高其数据管理的成熟度，促进信息资产的有效利用，并为业务决策提供更可靠的数据支持。

ISO/IEC 11179-3:2013(E)

h) the provision of services for semantic computing: Semantics Service Oriented Architecture, Semantic

Grids, semantics based workflows, Semantic Web, etc.;

i) support for addressing semantic web considerations such as AAA (anyone can say anything about

anything), non-unique names, and open world assumption;

j) the capture of semantics with more formal techniques (in addition to natural language) -- First Order Logic

(e.g., Common Logic), Description Logics (such as OWL-DL);

k) support of Application Development and Maintenance;

l) support of data migration, data mediation;

m) support of portals, data marts, and data warehouses;

n) support of data grids and online transaction networks;

o) ontological reasoning with metadata;

p) ontology entry point for browsing and searching metadata registries;

q) capture of associations between the published identifiers used in the ontology(s), and the concepts

registered in the registry;

r) support for Ontology-driven Data Translation;

s) support for data integration & data interoperation.

INTERNATIONAL STANDARD ISO/IEC 11179-3:2013(E)

Information technology — Metadata registries (MDR) —

Part 3:

Registry metamodel and basic attributes

1 Scope

1.1 Scope – Structure of a metadata registry

Clauses 5 through 11 specify the structure of a metadata registry in the form of a conceptual data model.

While the model diagrams are presented in UML notation, this part of ISO/IEC 11179 does not assume nor

endorse any specific system environment, database management system, database design paradigm, system

development methodology, data definition language, command language, system interface, user interface,

computing platform, or any technology required for implementation. This part of ISO/IEC 11179 does not

directly apply to the actual use of data in communications and information processing systems.

1.2 Scope – Basic attributes of metadata items

Clause 12 specifies basic attributes which are required to describe metadata items, and which might be used

in situations where a complete metadata registry is not appropriate (e.g. in the specification of other

International Standards).

2 Normative references

The following referenced documents are indispensable for the application of this document. For dated

references, only the edition cited applies. For undated references, the latest edition of the referenced

document (including any amendments) applies.

ISO/IEC 11179-6, Information technology — Metadata registries (MDR) — Part 6: Registration

3 Terms, definitions and abbreviated terms

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

NOTE 1 An alphabetical list of all terms used in this part of ISO/IEC 11179 is included in Annex A.

NOTE 2 Some definitions listed in this clause have one or more notes; some have a reference to another standard

from which the definition is taken; and some have both notes and a reference. Where a definition has both one or more

notes and a reference, notes that precede the reference come from the referenced source; notes that follow the reference

have been added by this part of ISO/IEC 11179.

ISO/IEC 11179-3:2013(E)

3.1 Terms and definitions of metamodel constructs used in this part of ISO/IEC 11179

NOTE This subclause defines the metamodel constructs (3.2.81 - units of notation for modelling) used in specifying

the registry metamodel in Clauses 6 through 11.

3.1.1

abstract class

metamodelclass (3.1.5) that does not provide a complete declaration and typi

cally cannot be instantiated

NOTE 1 An abstract class is intended to be used by other classes as a general class for specialization (3.1.16);

NOTE 2 Adapted from ISO/IEC 19505-1:2012, 9.19.1 Classifier.isAbstract.

NOTE 3 Cf. concrete class (3.1.8)

3.1.2

association

metamodelsemantic relationship (3.1.15) between two classes (3.1.5)

NOTE 1 An association is a type of relationship;

NOTE 2 Adapted from ISO/IEC 19505-2:2012, 7.3.3.

3.1.3

association class

metamodelassociation (3.1.2) that is also a cla

ss (3.1.5)

NOTE 1 An association class not only connects a set of classes, but also defines a set of features that belong to the

association itself;

NOTE 2 Adapted from ISO/IEC 19505-2:2012, 7.3.4.

3.1.4

attribute

metamodelcharacteristic (3.2.14) of an objec

t (3.2.87) or set of objects

3.1.5

class

metamodeldescription of a set of objects (3.2.87) that share the same attribu

tes (3.1.4), operations,

methods, relationships (3.1.15), and semantics

NOTE Adapted from ISO/IEC 19505-2:2012, 7.3.7.

3.1.6

composite attribute

metamodelattribute (3.1.4) whose da

tatype (3.1.8) is non-atomic

EXAMPLE See Registration.registration_state (8.1.5.1.2.1), where registration_state is a composite attibute with

Registration_State (8.1.2.6) as its composite datatype (3.1.7).

3.1.7

composite datatype

metamodeldatatype (3.1.8) that is also a class (3.1.5)

NOTE A composite datatype is used as a datatype for a composite attribute (3.1.6).

EXAMPLE See Registration.registration_state (8.1.5.1.2.1) where Registr

ation_State (8.1.2.6) serves as the

composite datatype for the composite attribute registration_state.

ISO/IEC 11179-3:2013(E)

NOTE 1 In this part of ISO/IEC 11179, a relationship is one of: an association (3.1.2), a generalization (3.1.10) or a

specialization (3.1.16);

NOTE 2 Adapted from ISO/IEC 19505-2:2012, 7.3.47.

3.1.16

specialization

metamodelrelationship (3.1.15) between a more general class (the parent) a

nd a more specific class (the

child) that is fully consistent with the general class and that adds additional information

NOTE 1 A specialization is a type of relationship (3.1.15);

NOTE 2 The more general class is referred to as the superclass (3.1.18);

NOT

E 3 The more specific class is referred to as a subclass (3.1.17);

NOTE 4 A specialization is directed from the superclass to the subclass;

NOTE 5 ‘Fully consistent’ means that the subclass has all of the attributes (3.1.4) and relationships (3.1.15) of the

superclass;

NOTE 6 cf. generalization (3.1.10); specialization is the inverse of generalization;

NOTE 7 Adapted from ISO/IEC 19505-2:2012, 7.3.20.

3.1.17

subclass

class (3.1.5) that is a specializ

ation (3.1.16) of another class, its superclass (3.1.18)

NOTE 1 In UML, subclasses of a superclass are by default incomplete and disjoint (3.2.59). This part of

ISO/IEC 11179 specifies when subclasses are complete and/or overlapping. Further, when the list of subclasses is

intended to be exhaustive, this part of ISO/IEC 11179 shows the superclass as abstract, thus preventing any other

subclass being instantiated. An abstract class (3.1.1) is indicated by showing the class name in italics in any class

diagram that uses it.

NOTE 2 A particular class may be a subclass with respect to one relationship, but a superclass with respect to another

relationship.

3.1.18

superclass

class (3.1.5) that is a generaliz

ation (3.1.10) of one or more other classes, its subclasses (3.1.17)

NOTE 1 In UML, subclasses of a superclass are by default incomplete and disjoint (3.2.59). This part of

ISO/IEC 11179 specifies when subclasses are complete and/or overlapping. Further, when the list of subclasses is

intended to be exhaustive, this part of ISO/IEC 11179 shows the superclass as abstract, thus preventing any other

subclass being instantiated. An abstract class (3.1.1) is indicated by showing the class name in italics in any class

diagram that uses it.

NOTE 2 A particular class may be a superclass with respect to one relationship, but a subclass with respect to another

relationship.

3.2 Terms for concepts used in this part of ISO/IEC 11179

NOTE This subclause provides definitions for terms which are concepts used in the specification of the metadata

model in Clauses 5 through 10. Data definitions are included in those clauses. An alphabetical list of terms with links to the

corresponding definitions is included in Annex A.

3.2.1

acceptability rating

scale of acceptability

NOTE 1 The following values shall be used: preferred, admitted, deprecated, obsolete and superseded

剩余243页未读，继续阅读

bruce_wang

粉丝: 15
资源: 7

ISO/IEC 11179-3:2013 - 信息技术 元数据注册表（MDR） 第3部分：注册元模型和基本属性

ISO IEC 11179-6 2015.pdf

c061932_ISO_IEC_11179-1_2015.pdf

ISO11179 2015

iso_iec_14496-10-avc-2012.pdf

iso iec 11179-2 pdf 中文

iec 61508-0-2010.pdf

iec 61000-1-3 pdf

ic卡标准-iso_iec 7816-3-2006

iec 62282-3-100 pdf

iec 62443-3-3 2013

最新资源

ISO/IEC 11179-3:2013 - 信息技术元数据注册表（MDR）第3部分：注册元模型和基本属性