Editor s Draft. Outcome of Berlin Meeting ISO/IEC JTC 1/SC32 WG2 N1669 ISO/IEC CD :ED2

Transcription

1 ISO/IEC JTC 1/SC32 WG2 N ISO/IEC CD :ED2 ISO/IEC JTC 1/SC 32/WG 2 Secretariat: Information Technology Metamodel framework for interoperability (MFI) Part 1: Reference model, Second Edition Editor s Draft Outcome of Berlin Meeting

2 Copyright notice This ISO document is a Draft International Standard and is copyright-protected by ISO. Except as permitted under the applicable laws of the user's country, neither this ISO draft nor any extract from it may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, photocopying, recording or otherwise, without prior written permission being secured. Requests for permission to reproduce should be addressed to either ISO at the address below or ISO's member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel Fax copyright@iso.ch Web Reproduction may be subject to royalty payments or a licensing agreement. Violators may be prosecuted. 1

3 目次 内容 ISO/IEC JTC 1/SC 32 WG2 NXXXX... 0 DATE: ISO/IEC CD :ED ISO/IEC JTC 1/SC 32/WG COPYRIGHT NOTICE... 1 FOREWORD... 4 INTRODUCTION SCOPE NORMATIVE REFERENCES TERMS, DEFINITIONS AND ABBREVIATED Terms and Definition domain model Interoperability metadata... 7 Metamodel... 7 Model... 7 Information model... 7 model construct... 7 modeling facility... 7 Modeling Language... 7 Model mapping... 8 Ontology... 8 Registration... 8 registry... 8 Repository... 8 Process model... 8 Service Abbreviations...8 BPMN... 8 EDI

4 ebxml... 8 HL7...Error! Bookmark not defined. MDA... 8 MOF... 8 MFI... 8 OWL...Error! Bookmark not defined. SDO... 9 UML... 9 UOD CONCEPT AND ARCHITECTURE OF MFI What is Metamodel Model registry... Error! Bookmark not defined. 4.3 Background of the MFI standards Major target area of MFI standards Typical application of MFI... Error! Bookmark not defined. 4.6 Interoperation among cross industry or domain ODMS (On Demand Model Selection) MFI AND MDR ARCHITECTURE Internal structure of MFI MODEL REGISTRATION CONCEPT Registration example...error! Bookmark not defined. 7 CONFORMANCE BIBLIOGRAPHY

5 Foreword 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. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 3. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. 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. Attention is drawn to the possibility that some of the elements of this part of ISO/IEC may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. International Standard ISO/IEC19763 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 32, Data management services. ISO/IEC consists of the following parts, under the general title Information technology --Metamodel Framework for interoperability: _Part 1: Reference model, 2 nd edition [this document] _Part 3: Metamodel for ontology registration, 2 nd edition _Part 5: Metamodel for process model registration _Part 6: Registry summery _Part 7: Metamodel for service registration _part 8: Metamodel role and goal registration _part 9: On demand model selection (Technical Report) _Part 10: Core model and basic mapping _Part 11: Structured registering (Technical Report) _Part-12: Metamodel for Information model Registration 4

6 Introduction Due to the spread of E-Business and E-Commerce over the Internet, the effective exchange of business transactions and other related information across countries and cultures has become a prime concern for people both inside and outside the IT industry. Adding to those trends, various types of information were exchanged and collected through the Internet or social networks involving peoples who are not expert of IT. Already, huge data were stored in so called the Cloud, it had roused further needs for new paradigms that enable effective use of data and semantically interoperation of those huge data. One of key facilities for the easy sharing and the interoperation of information could be the registry that enables the discovering and sharing of meta-information such as metadata and models Background of the 2 nd edition of MFI part 1 The first edition of the MFI part-1 standard was published At that time, the MFI family of standards was consisted of only four sub parts (part 1, part 2, part 3 and part 4). However, after publishing the first edition of part 1, many new projects were initiated. They are mostly intending to enhance the capability of MFI to cope with new trends of market, such as discovering process models and service models. Almost same time, a revising project of ISO/IEC11179 part-3 (registry metamodel and basic attribute: MDR) that is the core part of metadata registry standard was initiated. The MFI standards can be considered as extensions of the MDR core part by the sharing same registration mechanism and procedure. Then, a special study project for the harmonization of MDR and MFI was formulated. As a result of the study, the common facilities were defined to be used in both MDR and MFI standards. It was expected that MDR and MFI could be more closely related and integrated for the benefits of the users who need more effective sharing of information or more sophisticated system interoperation. A design guideline to keep consistency on representing metamodel using UML was defined to be used in the developing MFI standards Then, this new edition of this part was revised to provide a clear view to MFI and illustrate overall architecture of the MFI family of standards reflecting major changes mentioned above. 5

7 Information technology Metamodel framework for Interoperability (MFI) Part 1: Framework, edition 2 1 Scope This standard is a part of ISO/IEC19763 (Metamodel framework for interoperability: MFI) series of standards. As the first part of MFI (part 1), this document provides an overview of MFI series of standards. Especially, the background, underline concept, overall architecture and requirements to the development of other parts of MFI standards. The ISO/IEC19763 (Metamodel framework for interoperability: MFI) family of standards were prepared to provide standard facilities to register any kind of models through the metamodel for registration. 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 , Information technology Metadata registries (MDR) - Part 1 : Framework ISO/IEC , Information technology Metadata registries (MDR) - Part3 :Ed3 Metamodel ISO/IEC 19501:2005, Information technology - Open Distributed Processing- Unified Modeling Language (UML) Version ISO/IEC 19502:200X, Information technology - Open Distributed Processing- Unified Modeling Language (UML) Version [NOTE;] Should we need MOF/XMI as normative? nniso/iec 19502:2005, Information technology Meta Object Facility (MOF) ISO/IEC 19503:2005, Information technology MXL Metadata Interchange (XMI) 3 Terms, definitions and abbreviated For the purposes of this document, the terms and definitions were given as followed. Terms and Definition Terms 5.2 administered_item 5.3 concept unit of knowledge created by a unique combination of characteristics NOTE Concepts are not necessarily bound to particular languages. They are, however, influenced by the social or cultural background which often leads to different categorizations. 5.4 domain model A model which represents a particular domain 6

8 5.5 interoperability 5.6 Identification_Item 5.7 metadata Data which describes other data. See. ISO/IEC See. ISO/IEC [NOTE] 5.8 metamodel A model which governs other models. See ISO/IEC See. Modeling Facility [NOTE] 5.9 model A representation of concept in an universe of discourse (UOD) using a normative modeling facility and modeling constructs model element element or component in a model [see: ISO/IEC part 10] 5.11 information model NOTE NOTE 5.12 model construct A unit of notation for modeling. Note: More generic term for modeling element. Sometimes the term is used to include metadata, code and object patterns rather than the notations of a particular modeling facility such as UML Model element 5.14 modeling facility A set of rules and notations for use when modeling. Note: UML is a typical example modeling Language 7

9 5.16 model mapping 5.17 ontology 5.18 registration 5.19 registry 5.20 repository 5.21 process model 5.22 RGPS model 5.23 Service model Abbreviations BPMN EDI ebxml Electronic business XML IDEF1X MDA Model Driven Architecture MOF Meta Object Facility See: ISO/IEC 19502: MFI Metamodel Framework for Interoperability Note: This family of standards (ISO/IEC 19763) 8

10 3.2.8 SDO UML Unified Modeling Language UOD Universe of Discourse 9

11 4 Concept and Architecture of MFI In this section, the background and basic concept that is underlining to all parts of ISO/IEC (MFI) and the overall structure of the MFI family of standards should be explained. ISO/IEC (MFI) is a set of metamodel standards. Most of the metamodels are prepared for the registering models to the model registries, such as, generic information models, process models, service models and roles & goal models, in order to materialize the interoperability among systems or peoples. 4.1 Background and purpose of the MFI standards To enable the discovering and the sharing of information on the heterogeneous network societies, some sort of specific information that describes data or model, must be needed. Sometime, those specific information are called metadata or metamodel to be disclosed to the society. The term metadata is defined as a data that describes other data. That is common acceptable basic notion of metadata. NOTE Heterogeneous environment Even in the bilateral communication or interchanging of information between company A and B, there must be a common agreement on the description or representation of information to be shared. In the early stage of EDI (Electronic Data Interchange), those descriptions or representations were stored in a particular database called the metadata registry and shared by A and B. However, the manner or the style for description and representation were depending upon the agreement between A and B. Along with the proliferation of the Internet, the manner for describing information, become recognized to be standardized, such as the metadata or metamodel standards. By the standardizations in the EDI or the Electronic Business area, those manners for describing information were uniformly defined as metadata standards or registry standards. However, each industry defined their own registry contents with their own manner. Today, SDO such as ISO, IEC or some other standard consortia developed and enforced so many metadata standards or registry standards, following their own industry or domain requirements. For instance, E-business, Healthcare, Electronic parts, Electronic documents, Library etc., those industries have own metadata standards. Then, It is still not easy to share information across deferent industries or domains without any specific mapping or translation tools between metadata in different registries. It must be one of obstacles for materializing a global and dynamic supply chain that penetrate different industries across countries. For instance, in the electronics manufactures, they has own product database while retailer also has their own item database. Each database was constructed following particular metadata standards that were specified by industry consortium or SDO. However, it is not easy to keep the interoperation among those on the same products data. There must be some sort of mapping function to connect different data on a same product. [see. figure-1] 10

12 At the moment, instances of those metadata mapping have to be specified by human efforts discussing the difference between manufacturing product and sales item. They have to compare metadata. At that time, they have to refer to information model to understand the nature of data. Then, the sharing of information model could be indispensable in the defining data as metadata, also, understanding metadata. Fig-1 Current status of the cross industries interoperation Why model to be shared Therefore, before defining data as metadata, an information model that reflects the target domain in discourse must be needed. To understand the semantic meaning of single piece of data, it should be indicated which property of an object class in the model, were represented. 1) Better understanding and definition of data ISO/IEC (Metadata Registry: MDR) standards provided a domain independent metadata representation and registration attributes of a metadata registry. Also, the MDR provides facility to register object classes and attributes and conceptual domain, these were came from information models to make data more understandable and provide a scheme to investigate the sameness or oneness of data. Then, the model sharing must be necessary in the better definition of a piece of metadata and make them interoperable among different domains. 2) System interoperability Not only for understanding of data, various types of information models were used widely. In the software development area, the information models using UML or IDEF1X, etc., were used as the software specifications. To capture the essential context of a target domain, normative representation technic were used to promote software design and development involving different peoples. In those environments, the model sharing must be necessary. Also, to involve 11

13 engineers who are working in the different countries, so called Offshoring, they need the model sharing supported by specific platform or infrastructure. MFI provides basis for the model sharing infrastructure, in term of the model registry. The model sharing could be accelerated by the registering models to a registry (Model registry) and make it easier to discover an appropriate model. The MFI is a set of normative metamodel to be used for the model registration, just like the MDR provides normative metamodel for registering the metadata Fig. XX Basic concept of the model sharing through the Model Regis 4.2 What is MFI metamodel MFI is a set of metamodels to be used in the Model regisration. The Major purpose of metamodels Is to make the model registration become more easier and to enable the registration consistency. Here, the term Metamodel is recognized as a model that describes a model. However, More detailed insight of the metamodel should be provided in the later potion of this document [see ANNEX A] Fig X shows the basic concept of model registration. The MFI metamodel provides to registrar normalized view to registering. Also, the metamodel specifies the structure of registration information to be stored into the registry. 12

14 Fig x Basic concept MFI registration and metamodel A metamodel for registering model was specified by MFI part 10 (formally part 2): That is the core model and basic mapping. According to the core model, MFI other parts provide some specialized metamodel for the convenience of the registering specific modes; Ontology model (MFI part-3) Process model (MFI part-5) Service model (MFI part-7) Goals and Roles model (MFI part-8) Information model (MFI-12) Registry summery model (MFI-6) MFI would not specify any implementation requirements for the registry or the repository, only specifies metamodel for various types of models, in term of registration. That means how to capture a model for the registration Some metamodel in MFI l(mfi-2) represents registration mechanism as the core model to be used by other parts of MFI. Also, another metamodel that represents registry itself as profile on a particular registry is prepared to make the registry interoperation becomes possible..in the MFI, the model registry does not store any model instance into the data bases, only model information could be stored, while the model repository could accommodate instances of model in the databases. Usually, the model repository used for storing a model into a database to be used for recalling and represent model exactly again by the modeling tools. However, the model registry, keeps only model administration information, such as, location of model, owner of model etc. could be available. Through the registry, it could be available to know the exact place where actual model is stored in a model repository. Generally, the registry is the place where records of some events or entities are put and kept for the publicly disclose. 13

15 Then, MFI registries stores only information about those model and model components as followed. Where the model exists, who is owner, registration date What components are consist of the model and where does it exist What are relationships among components Then, MFI supposes that actual models to be shared were stored in a particular model repository outside. In MFI, any representation style of model, such as UML, IDEF1X, ER, NIAM or BPMN can be registered. Also, any kinds of domain models are available to be registered Major application area of MFI standards The ISO/IEC (MFI) was prepared to make the interoperability possible among system or people that are relying upon network. Especially, the interoperability of data that means the sharing data and models semantically across different domains or societies, facilitating the registries.. However, there are a lot of different individual domains in the world that were supported by IT or network. Some of them had already constructed metadata registry or data dictionary. It is unrealistic to integrate them into a single registry to materialize the interoperability Interoperation among cross industry or domain E-business and E-commerce have proliferated over the world, facilitating specific standards such as ebxml or RosettaNet. By the nature of E-business, it is not limited to a single industrial domain or territory. Different domains are linked by the internet, and inevitably users or consumers will need to access different private individual registries. Figure X - System interoperation among different industries 14

16 The metamodel framework family of standards facilitates business collaborations through E-business or E-commerce by providing mechanisms for describing metamodels in each registry in order that they may be shared among different business domains. Particularly, the core model of the metamodel framework provides a mechanism for describing each different metamodel in local registries and enables their registration in the registry. Also, the metamodel framework for model mapping provides a facility for registering mapping rules to enable federation among different registries On Demand Model discovery Figure ROR (Registry of Registries) Figure XX Registry of registries 15

17 6. MFI and MDR Architecture The metamodel framework for interoperability (MFI) family of standards consists of multiple parts which are to be used in the sharing of information models, services, role & goal specification and ontologies through the registration. 6.1 Overall structure of MDR/MFI Each part of this family of standard specifies metamodel (by UML) that enable to register of artefacts, such as various types of models, services, and ontologies. Through the registration of models or services, information systems or human activities were expected to be more interoperable or understandable. All of parts in MFI are close related to ISO/IEC11179 (MDR: Metadata registry). Then, MFI is an extension of MDR. Figure-3 illustrates the overall structure of both standards. Figure X Overall structure of the MFI and MDR standards 6.2 Core facility 16

18 6.3 Internal structure of MFI In the MFI family of standards, many part were prepared according to the current industrial and personal requirements for finding and discovery of models, services, and onotologies. Figure X Parts relationship in the MFI family of standards Part 1 Reference model This part of the standard describes the concepts and an overall architecture of the metamodel framework standard to be applied in the development and the registration of the following individual metamodel frameworks. Part 10 Core model and basic mapping This part of the standard describes the core model of the metamodel framework to be used in the development of metamodel framework standards. The core model provides a mechanism for metamodel description and normative constructs to be used in the development of metamodel framework standards. Part 3 Metamodel for ontology registration 17

19 This part of the standard describes a metamodel that provides a facility to register administrative information of ontologies. Part 5 Metamodel for process model registration This part of standard provide a metamodel that provide a facility to register any kind of process model. The register following this standard become able to be RGPS registry. Part-6 Registry summery This part of standard provides a metamodel of registry summery information that to be installed on any kind of registry. By those summery information could be collected and conform a ROR (Registry of Registries). Part 7 Metamodel for service registration This part of standard provides a metamodel for service registration. The services in this standard are considered mostly the Web service. However, generic service that supported by a set of processes could be Part 8 Metamodel for RGPS registration This part of standard provides a metamodel for Role and Goal registration. A goal decomposed into a couple of Role. Part 9 On demand model selection (TR) This part of standard provide an idea and a methodology to use model registry contents,such as, Process model, Service model and Roles & Goals model from the view point of ODMS (On Demand Model Selection). Part 11 Structured registering (TR) TBD Part 12 Metamodel for registering information model This part of standard provide a super type of information models as a common view to different modeling facilities such as, UML, IDEF1X,etc. 18

20 7. Model registration concept The term Registration means the recording of the things, such as some new events, or occurrence of new entities, officially. Generally, these records are kept in the specific files called the registries, and they could not be updated. Those records are referred and used by others, publicly. Then, the record in the registry should be clearly defined and format, item to be registered must be standardized. Some time, record type and format might be the legal issues. A registration record should contain following items. 1) The time to be recorded 2) The ownership of the things 3) Types of the things 4) Name of registrar 5) Name of registration authority 6) Submission status Fig XXX Registry entry and metamodel The MFI and MDR, both share the same registration mechanism, such as, administered_item and Identification_item. In MFI, the registration record was inherited from the registration record that was standardized ISO/IEC (MDR). 19

21 7 Conformance ISO/IEC specifies no conformance requirement. Other parts of this family of standards specify their own conformance requirements as appropriate. 8 Bibliography [1] ISO/IEC TR 9007:1987, Information processing systems Concepts and terminology for the conceptual schema and the information base TR 9007 provides information on conceptual modelling. [2] ISO/IEC 10027:1990, Information technology Information Resource Dictionary System (IRDS) Framework ISO/IEC describes the concept of levels of modelling. [3] ISO/IEC TR 15452:2000, Information technology Specification of data value domains TR describes the specification of value domains. It is expected to be replaced by ISO/IEC TR [4] ISO/IEC TR :200n, Information technology Achieving metadata registry content consistency Part 1:Data elements TR , which is under development at the time of publication of ISO/IEC , will provide guidelines for recording data elements in a metadata registry. [5] ISO/IEC TR :200n, Information technology Achieving metadata registry content consistency Part 3:Value domains TR , which is under development at the time of publication of ISO/IEC , will provide guidelines for recording value domains in a metadata registry. [6] [MDA] Policies and Procedures for MDA: OMG, 2001, pp/ [7] [ebrim] ebxml Registry Information Model. Version Working Draft. 2/28/2001. ebxml Registry Project Team. [8] [ebrs] ebxml Registry Services. Version Working Draft. 2/28/2001. ebxml Registry Project Team. 20

22 ANNEX A: (Informative) Basic concept of MFI metamodel A1 What is Metamodel This ANNEX provides the concept of the model and metamodel that were used in this standards. Before discussing metamodel, the concept of model to be discussed in this standard should be defined. A1.1 Model Model is a representation of concept. NOTE major citations should be made, here. Fig Model and metammodel A2. Metamodel MFI is a set of metamodels that are prepared for the particular use, such as the registration of models. Metamodel is also a model. Usually, same modeling language, such as UML is used to represent both metamodel and model. Generally, the term metamodel is defined a model which describes other models. Another aspect of metamodel is that a model which governs other model. Then, the role of metamodel can be classified as followed. (1) Provide modeling constructs (i.e, diagram notations) with its semantics and syntax to the model. Metamodel guides modeling under uniform representation manner. Ex. UML metamodel Provide specific modeling concept for modeling with its constructs, such as Object, Class. Realationsgip, etc (2) Here, the modeling concept means what kind of modeling manner should be used, such as Object modeling, NIAM modeling, IDEF1X modeling or others. 21

23 Ex. MOF (Meta Object Facility) (3) Provide specialized modeling construct as template to view and capture the reality as concept in a particular domain. Ex. SPEM( Software Process Engineering Metamodel: OMG), Usually, applying a metamodel to a modeling effort could be done by the inheriting modeling constructs to the model to be defined. Every metamodel in the MFI standards is considered to be 3) above mentioned, providing special dedicated modelling views in term of the model registration Figure types of Metamodel and model 22

24 A3 Typical MFI metamodel for registration 23

25 24