ISO/IECJISO/IECJTC11/SC3232N
Date:2012-12-252012-07-10
Sneak Peek ISO/IECCD19763-6ISO/IECCD219763-6
ISO/IECJISO/IECJTC11/SC3232/WG22
Secretariat:ANSIANSI
Information Technology— Metamodel framework for interoperability— Part6: Registry SummaryInformation Technology— Metamodel framework for interoperability— Part6: Registry Summary
Technology de ľinformation— Cadre du métamodèle pour ľinteropérabilité (MFI)— Partie6: Résumé RegistryTechnology de ľinformation— Cadre du métamodèle pour ľinteropérabilité (MFI)— Partie6: Résumé Registry
Warning
This document is not an ISO International Standard. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an International Standard.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.
Warning
This document is not an ISO International Standard. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an International Standard.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.
Warning
This document is not an ISO International Standard. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an International Standard.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.
Sneak Peek ISO/IECCD319763-6ISO/IECCD219763-6
Copyright notice
This ISO document is a working draft or committee draft and is copyright-protected by ISO. While the reproduction of working drafts or committee drafts in any form for use by participants in the ISO standards development process is permitted without prior permission from ISO, neither this document nor any extract from it may be reproduced, stored or transmitted in any form for any other purpose without prior written permission from ISO.
Requests for permission to reproduce this document for the purpose of selling it should be addressed as shown below or to ISO's member body in the country of the requester:
Reproduction for sales purposes may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
ContentsPage
Foreword......
Introduction......
1Scope......
......
2Normative references......
3Terms and definitions......
4Symbols (and abbreviated terms)......
5Conformance......
5.1Degree of conformance
5.1.1Strictly conforming
5.1.2Conforming implementation
5.2Implementation Conformance Statement (ICS)
6Background and purpose
6.1Role of the Registry Summary
7Registry Summary......
7.1Overview of Registry Summary......
7.2Classes in the RegistrySummary package
AnnexA (informative) Examples of Registry Summary......
A.1Introduction......
A.2Types of target registry for Registry Summary......
A.2.1Independent Registry......
A.2.2Replication Registry......
A.2.3Federated Registry......
AnnexB (informative) Example of Registry Summary......
B.1Introduction......
B.2Adaptation method of model of other standard......
B.2.1Example of using ISO/IEC 11179 Part 3 claases......
B.2.2Example of using UN/CEFACT Core Component Library classes......
AnnexC (informative) Example of Registry Summary XML Schema......
C.1Introduction
C.2XML Schema definition
C.2.1Introduction
C.2.2ComplexType definition
C.2.3Sample element definition
AnnexD (informative) Example of indicator of Registry Summary
D.1Introduction
D.2Location of Registry summary in META tag
1Scope...... 1
2Normative references...... 1
3Terms and definitions...... 1
3.1General...... 1
4Symbols (and abbreviated terms)...... 2
5Conformance...... 3
5.1Degree of conformance...... 3
5.1.1Strictly conforming...... 3
5.1.2Conforming implementation...... 3
5.2Implementation Conformance Statement (ICS)...... 3
6Background and purpose...... 4
6.1Role of the Registry Summary...... 4
7Registry Summary...... 4
7.1Classes in the Registry_Summary package...... 5
7.1.1Assembly class...... 5
AnnexA (informative) Example of Registry Summary...... 14
A.1Introduction...... 14
A.2Adaption method of model of other standard...... 14
A.2.1Exapmle of useing ISO/IEC 11179 Part 3 claases...... 14
A.2.2Example of using UN/CEFACT Core Component Library classes...... 15
AnnexB (informative) Example of Registry Summary XML Schema...... 17
B.1Introduction...... 17
B.1XML Schema definition...... 17
B.1.1Introduction...... 17
B.1.2ComplexType definition...... 17
B.1.3Sample element definition...... 20
AnnexC (informative) Example of indicator of Registry Summary...... 21
C.1Introduction...... 21
C.2Location of Registry summary in META tag...... 21
ContentsPage
Foreword...... iv
Introduction...... v
1Scope...... 1
1.1General...... 1
2Normative references...... 1
3Terms and definitions...... 1
3.1General...... 1
4Symbols (and abbreviated terms)...... 3
5Conformance...... 3
5.1General...... 3
5.2Degree of conformance...... 3
5.2.1General...... 3
5.2.2Strictly conforming...... 3
5.2.3Conforming implementation...... 3
5.3Implementation Conformance Statement (ICS)...... 4
6Requirements...... 4
6.1Background and purpose...... 4
6.2Structure of MFI Registry...... 4
7Registry Summary...... 5
7.1Overview of Registry Summary...... 5
7.1.1Classes in the Registry_Summary package...... 6
AnnexA (informative) Example of Registry Summary...... 12
A.1Introduction...... 12
A.2Adaption method of model of other standard...... 12
A.2.1Exapmle of useing ISO/IEC 11179 Part 3 claases...... 12
A.2.2Example of using UN/CEFACT Core Component Library classes...... 13
AnnexB (informative) Example of Registry Summary XML Schema...... 15
B.1Introduction...... 15
B.1XML Schema definition...... 15
B.1.1Introduction...... 15
B.1.2ComplexType definition...... 15
B.1.3Sample element definition...... 18
AnnexC (informative) Example of indicator of Registry Summary...... 19
C.1Introduction...... 19
C.2Location of Registry summary in META tag...... 19
Foreword
ISO/IEC1976361Information technology32Data Management and Interchage
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 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 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/IECJTC1.
International Standards are drafted in accordance with the rules given in the ISO/IECDirectives, Part2.
The main task of the joint 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.
ISO/IEC197636 was prepared by Joint Technical Committee ISO/IECJTC1, Information technologyInformation technology, Subcommittee SC32, Data Management and InterchageData Management and Interchage.
ISO/IEC19763 consists of the following parts, under the general title Information Technology— Metamodel framework for interoperabilityInformation Technology— Metamodel framework for interoperability:
Part6: Registry SummaryISO/IEC19763Information Technology— Metamodel framework for interoperabilityPart6: Registry SummaryISO/IEC1976361Information technology32Data Management and InterchageISO/IEC19763Information Technology— Metamodel framework for interoperabilityPart6: Registry SummaryISO/IEC1976361Information technology32Data Management and InterchageISO/IEC19763Information Technology— Metamodel framework for interoperabilityPart6: Registry SummaryISO (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 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 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/IECJTC1.
International Standards are drafted in accordance with the rules given in the ISO/IECDirectives, Part2.
The main task of the joint 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.
ISO/IEC197636 was prepared by Joint Technical Committee ISO/IECJTC1, Information technology, Subcommittee SC32, Data Management and Interchage.
ISO/IEC19763 consists of the following parts, under the general title Information Technology— Metamodel framework for interoperability:
Part1:Reference model
Part3:Metamodel for ontology registration
Part 5:Metamodel for process model registration
Part6: Registry Summary (this document)
Part7:Metamodel for service registration
Part8:Metamodel for role and goal registration
Part 9:On Demand Model Selection[Technical Report]
Part 10:Core model and basic mapping
Part 11:Structured model registering[Technical Report]
Part 12:Metamodel for information model registration
Introduction
Today, in E-business (EB) or E-commerce (EC) through the Internet, the effective interchange of business transactions or other related information across countries and cultures is an important concern for people in both the IT industry and non-IT industries.
To follow the current trends of EB or EC, industrial consortia have engaged in the standardization of dDomain[TA1]-specific business objects, including business process models and software components using common modeling toolsfacilities and interchange facilities such as UML and XML. They are very active in standardizing domain-specific business process models and standard modeling constructs such as data elements, entity profiles and value domains.
The ISO/IEC 19763 family of standards defines normative metamodels for the registration of models (including information models and process models), ontologiesy, process models, services and roles & goals[TA2]. Items or objects specified by those metamodels have been registered into particular registry systems. In order to perform effective exchange of pertinent information smoothly, individuala particular registry systems needs to interoperate with other registry sysytems[TA3].[ADACHI4]
This part of ISO/IEC 19763 defines a metamodelin the case thatfor the use case in which registry systems of different kinds must share information[TA5].
©ISO/IEC2012– All rights reserved©ISO/IEC2012– All rights reserved / 1Sneak Peek ISO/IECCD319763-6ISO/IECCD219763-6
Information Technology— Metamodel framework for interoperability— Part6: Registry Summary
1Scope
1.1General[TA6]
The ISO/IEC 19763 family of standards defines normative metamodels for the registrationeringof models (including information models and process models), ontologiesy, process models, services and roles & goals[TA7]. Currently many a lot of metadata registries or model registries have been establishedwere constructed and put in the useutilizedd in a variety ofmany differentdiffernt business domains, such as e-business, healthcare, automobile, electronics devices and civil construction.
One of the key issues for the cross domain data or services integration, must be enabling the easy discoveringy of metadata that are stored in the differentdifferent registries that were scateredscattered over different domains. One of the key issues in the cross-domain supply chain business, or service discovery across domains is finding and mapping between data elements that have been registered in different registries. Therefore, it is necessary requirednecessary to provide specific metadata that describes the registy itself.about a specific registry itself in order to enable the interoperation among different registries. Registries that were built using following different standards.may require special treatment.
This part of the ISO/IEC 19763 family of standardsdefines specifies an the information artchifact which we called the Registry Summary. And they provide administrative information.The Registry Summary consists of information that describes administrative aspects, theartifacts that communicate the registry management, registrysummary of contents and the technical registry access method of the registry.[TA8]
This part of the ISO/IEC 19763 family specifies a normative metamodel that specifies describes the Rregistry Ssummary information.
A collection of multiple Registry Summary information is called a “Registry of Registries” or RoRThe collection of Registry Summmary become a specific database called ROR (Registry of registries), however, this standard does not mandate a particular implementationhowever, this standard would not specify any implementaiton manners. Also, any specific protocol between Rregistry Ssummaries and RoOR, such as creation of RoOR and synchronization of RoOR , would not be specified in this standard. Those are to be specified by other standards.
The Registry Summary and RoOR concept should be applied to all MFI registries, but its use may be applied to any kind of registriesit does not restrict to apply those to any kinds of resistry.
2Normative 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 19763-1:2007[ADACHI9], Information technology — Metamodel framework for interoperability (MFI) — Part 1:
Reference model
ISO/IEC 11179-6:2005[ADACHI10], Information technology — Metadata registries (MDR) — Part 6: Registration
3Terms and definitions[ADACHI11]
Genera[TA12]l
For the purposes of this document, the items and definitions given in ISO/IEC 19763-1, ISO/IEC 11179-6 and the following apply.
3.1
attribute
'metamodel' characteristic of an object or set of objects
[ISO/IECFDIS 11179-3:2012, 3.21.34]
3.2
class
'metamodel' description of a set of objects that share the same attributes, operations, methods, relationships, and semantics
[ISO/IEC FDIS 11179-3:2012, 3.21.45]
3.3
metadata
data that defines and describes other data
[ISO/IEC 11179-1:2004, 3.2.16]
3.4
metadata register
information store or database maintained by a metadata registry
[ISO/IEC 11179-6:2005, 3.12]
[TA13]3.45
metadata registry
MDR
registry sysytem[TA14]
information system for registering metadata,
NOTEAdopted from ISO/IEC 11179-1:2004, 3.2.19.
NOTE 1The associated information store or database is known as a metadata register.
[ISO/IEC FDIS 11179-3:2012, 3.2.75]
NOTE 2registry system has been added as a new synonym,[ADACHI15]
3.56
metamodel
model which describes other models
[ISO/IEC 19763-1:2007, 4.1.4]
[TA16]3.67
referencing registry[TA17]
registry of registries
registry that stores Registry Summary data showing an individual registry system
3.8
referenced registry
registry that stores metadata by metamodels which are defined other parts of ISO/IEC 19763 defined. The referenced registry is described by the Registry Summary
[TA18]3.79
registry summary
registry summary is metadata which refers to an individual particular registry system or an aggregate of registry systems[TA19]
3.10
repository system
repository
system to store and manage items or objects indicated by the registry system
4Symbols (and abbreviated terms)
MDR / Metadata RegistryMFI / Metamodel Framework for Interoperability (i.e. ISO/IEC 19763-1)
RoR / Registry of Registries
RS / Registry Summary
SLA / Service Level Agreement
UML / Unified Modeling Language
URL / Uniform Resource Locator
XML / Extensible Markup Language
WSDL / Web Service Description Language
5Conformance
General
An implementation claiming conformance with this part of ISO/IEC 19763 shall support the metamodel specified in clause7, depending on a degree of conformance as described below.
5.1Degree of conformance
General
The distinction between "strictly conforming" and "conforming" implementations is necessary to address the simultaneous needs for interoperability and extensions. This part of ISO/IEC 19763 describes specifications that promote interoperability. Extensions are motivated by needs of users, vendors, institutions and industries, but are not specified by this part of ISO/IEC 19763.
A strictly conforming implementation may be limited in usefulness but is maximally interoperable with respect to this part of ISO/IEC 19763. A conforming implementation may be more useful, but may be less interoperable with respect to this part of ISO/IEC 19763.
5.1.1Strictly conforming
A strictly conforming implementation
a)shall support the metamodel specified in clause 7;
b)shall not support any extensions to the metamodel specified in clause7.
5.1.2Conforming implementation
A conforming implementation
a)shall support the metamodel specified in clause7;
b)may support extensions to the metamodel specified in[TA20]by clause 7 that are consistent with the metamodel specified in clause7.[TA21]
5.2Implementation Conformance Statement (ICS)
An implementation claiming conformance with this part of ISO/IEC 19763 shall include an Implementation
Conformance Statement stating.
a)whether it is a strictly conforming implementation or a conforming implementation (5.15.2)
b)what extensions are supported if it is a conforming implementation.implementation.implementation?
6Background and purpose
The major pRequirements
Background and purpose
Theurpose of the ISO/IEC 19763 (MFI) family of standards is to enable the interoperability among registries. Currently, many metadata registries have been developedso many metadata registries or model registries were already developed and enforced in various types of business domains. Most of them were developed conforming to international standards, such as e-business, healthcare, or library domains. However, those standards themselfthemselves were incompatible each other, and they were developed primarily according to requirements that came from their particular domainsthey were developed by the mostly requirements came from their own domains. IThist means that a single company or user who belongs to a particular domain has difficulties on thein accessing registries that were built according to requirements from other domainswere enforced in other different domains.
Sharing registry information across different domains can be important for system interoperabilityFor the sake of the system interoperability, it could be an argent issue to share metadata registry across different domains. The ISO/IEC 19763-6 standard (MFI-6) addresses registry interoperation with regard to the problems mentioned aboveThen, the ISO/IEC 19763-6 standard (MFI-6) is intending to materialize the registry interoperation addressing to the problems mentioned above.
This standard specifies a set of small XML artifacts called the Registry Summary to be attached to each domain-specific registryThis standard specifies a set of small XML artifacts called the Registry Summary to be attached to each registry in the domains. These artifacts arewere represented by a metamodel using UML.
6.1 Role of the Registry Summary
defines normative metamodels for the registration of models, ontology, process models, services and roles & goals. Items or objects specified by those metamodels have been registered into particular registry systems. Therefore the registry user has to know with which registry the needed item or object is registered. This part defines location metamodel for the summary data about the registry where the information the user needs resides.
5.3Structure of MFI Registry
This part of ISO/IEC 19763 defines two types of roles for a registry: referencing registry and referenced registry, and assumes that the registries charged with the respective roles cooperate with external communications from other registries. Referenced registry where stores metamodels which other part of ISO/IEC 19763 defined. Referencing registry is Registry of Registries (RoR) which collects and accommodates Registry Summary data which each registry generates.The The Registry Summary is a small set of metadata for the Registry that is attached in the registry system.registry summary is a small set of metadata to be attached in the target registry as a header information of the registry. If every registry would attach this registry summary, it would be possible to capture information on the nature of the another registry as well as technical information for accessing the registryit could be possible to caputure and know the nature of the registry and technical information for accessing the registry.
Figure 1 illustrates a typical use case of for RS(Registry Summary) and ROR(Registry of registries). Each registry prepairedprepared in a particular domain might be able to disclose RS at its access point as entry informationcould be abe to discloses RS at thier header as entry information. Different domains, such as Manufacturing or Retailing, would be able to prepare their own dedicated registry that is a collection of RSThen, every user in different domains, such as Manufacturing or Retailing become able to prepair their oun dedicated registry that is a collection of RS. It should be called the Registry of Registries (ROR).