DOC

32N1819T-text_for_ballot-CD_19763-5doc - SubCommittee Name

By Dolores Arnold,2014-11-25 23:06
11 views 0
32N1819T-text_for_ballot-CD_19763-5doc - SubCommittee Name

Committee Draft ISO/IEC CD 19763-5

    Date: Reference number:

    2009-01-13 ISO/JTC 1/SC 32N1819

    Supersedes document 32N1791

    THIS DOCUMENT IS STILL UNDER STUDY AND SUBJECT TO CHANGE. IT SHOULD NOT BE USED FOR REFERENCE PURPOSES.

    ISO/IEC JTC 1/SC 32 Circulated to P- and O-members, and to technical committees and Data Management and organizations in liaison for voting (P-members only) by:

    Interchange

    2009-04-13 Secretariat:

    USA (ANSI) Please return all votes and comments in electronic form directly to

    the SC 32 Secretariat by the due date indicated.

ISO/IEC CD 19763-5: 2009(E)

    Title: Information technology - Metamodel framework for interoperability (MFI) Part 5:

    Metamodel for process model registration

    Project: 1.32.22.01.05.00

Introductory note:

    The attached document is hereby submitted for a 3-month letter ballot to the NBs of ISO/IEC JTC 1/SC 32. The ballot starts 2009-01-13. No disposition of comments is provided because this is a new project edition approved Sydney 2008-05-30.

    Medium: E

    No. of pages: 26

    Dr. Timothy Schoechle, Secretary, ISO/IEC JTC 1/SC 32 Farance Inc *, 3066 Sixth Street, Boulder, CO, United States of America Telephone: +1 303-443-5490; E-mail: Timothy@Schoechle.org available from the JTC 1/SC 32 WebSite http://www.jtc1sc32.org/ *Farance Inc. administers the ISO/IEC JTC 1/SC 32 Secretariat on behalf of ANSI

    ISO/IEC JTC 1/SC 32 N 1819

    Date: 2009-1-7

    ISO/IEC CD 19763-5

    ISO/IEC JTC 1/SC 32/WG 2

    Secretariat: ANSI

    Information technologyMetamodel framework for interoperability (MFI)

    Part 3: Metamodel for process model registration

    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.

Document type: International Standard

    Document subtype:

    Document stage: (50) WorkingDraft

    Document language: E

ISO/IEC CD 19763-5:2009(E)

    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. + 41 22 749 01 11

    Fax + 41 22 749 09 47

    E-mail copyright@iso.ch

    Web www.iso.ch

    Reproduction may be subject to royalty payments or a licensing agreement.

    Violators may be prosecuted.

iii ? ISO/IEC 2009 All rights reserved

    ISO/IEC CD 19763-5:2009(E)

Contents

    Foreword .............................................................................................................................................................. vi Introduction ........................................................................................................................................................ vii 1 Scope ........................................................................................................................................................ 1 2 Normative references ............................................................................................................................... 2 3 Definitions and abbreviated terms .......................................................................................................... 2

    3.1 Definitions ......................................................................................................................................................... 2

    3.2 Broad terms ....................................................................................................................................................... 2

    3.2.1 process model ............................................................................................................................................ 2

    3.2.2 sub-process ................................................................................................................................................ 2

    3.3 Abbreviated terms ........................................................................................................................................... 2

    3.3.1 MFI Process registration ........................................................................................................................... 2

    3.3.2 MFI Core ................................................................................................................................................... 3

    3.3.3 MFI-3 ........................................................................................................................................................ 3

    3.3.4 OWL-s ....................................................................................................................................................... 3

    3.3.5 PSL ............................................................................................................................................................ 3 4 Structure of MFI Process registration ..................................................................................................... 3

    4.1 Overview of MFI Process registration .............................................................................................................. 3

    4.2 Relationship between MFI Core and MFI Process registration ........................................................................ 5

    4.3 MFI Process registration ................................................................................................................................... 5

    4.3.1 Goal ........................................................................................................................................................... 5

    4.3.2 Process....................................................................................................................................................... 6

    4.3.3 Process_Modeling_Language ................................................................................................................... 6

    4.3.4 Atomic_Process ......................................................................................................................................... 7

    4.3.5 Composite_Process ................................................................................................................................... 7

    4.3.6 Input .......................................................................................................................................................... 7

    4.3.7 Output ........................................................................................................................................................ 8

    4.3.8 Artifact ...................................................................................................................................................... 8

    4.3.9 Constraint .................................................................................................................................................. 8

    4.3.10 Artifact_Constraint .................................................................................................................................... 9

    4.3.11 Control_Constraint .................................................................................................................................... 9

    4.3.12 Condition ................................................................................................................................................... 9

    4.3.13 Precondition .............................................................................................................................................. 9

    4.3.14 Postcondition ........................................................................................................................................... 10

    4.3.15 Control_Construct ................................................................................................................................... 10

    4.3.16 AnyOrder ................................................................................................................................................. 10

    4.3.17 Choice ..................................................................................................................................................... 10

    4.3.18 Join .......................................................................................................................................................... 10

    4.3.19 Sequence ................................................................................................................................................. 10

    4.3.20 Split ......................................................................................................................................................... 11 ? ISO/IEC 2009 All rights reserved iv

    ISO/IEC CD 19763-5:2009(E)

5 Conformance .......................................................................................................................................... 12

    5.1 General ............................................................................................................................................................ 12

    5.2 Degree of conformance ................................................................................................................................... 12

    5.2.1 General .................................................................................................................................................... 12

    5.2.2 Strictly conforming implementation........................................................................................................ 12

    5.2.3 Conforming implementation ................................................................................................................... 12

    5.3 Implementation Conformance Statement (ICS) .............................................................................................. 12

Annex A (informative) Examples of MFI Process registration .......................................................................... 13

    Annex B (informative) Collaboration between MFI members ........................................................................... 17

    Annex C (informative) List of process modelling languages ........................................................................... 18

Figures and tables

    Figure 1 Scope of MFI Process registration ........................................................................................................... 1

    Figure 2 Base Model of MFI Process registration.................................................................................................. 3

    Figure 3 Process Control Model of MFI Process registration .............................................................................. 4

    Figure 4 Relationship between MFI Core and MFI Process registration............................................................ 5

    Figure 5 Registration information of BravoAir Reservation Service .................................................................. 14

    Figure 6 Registration Information of top level process for manufacturing GT350 .......................................... 15

    Figure 7 Registration information of some sub-processes of manufacturing GT350 ..................................... 16

    Figure 8 Semantic interoperation based on MFI Process registration and MFI Ontology registration ........ 17

    Table 1 List of Process_Modelling_Languages ................................................................................................... 18 ? ISO/IEC 2009 All rights reserved v

ISO/IEC CD 19763-5:2009(E)

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. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.

    International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. 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.

    Attention is drawn to the possibility that some of the elements of this part of ISO/IECWD 19763 may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 19763 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information Technology, Subcommittee

    SC 32, Data Management and Interchange.

    ISO/IEC 19763 consists of the following parts, under the general title Information technology Metamodel

    Framework for Interoperability:

    Part 1: Reference Model

    Part 2: Core Model

    Part 3: Metamodel for ontology registration

    Part 4: Metamodel for model mapping

    Part 5: Metamodel for process model registration

    vi ? ISO/IEC 2009 All rights reserved

ISO/IEC CD 19763-5:2009(E)

Introduction

    Today, in the EB(E-Business) or EC(E-Commerce) through the internet, the effective interchange of business transactions or other related information across countries and cultures became the first concerns for people in both IT industry and other non-IT industries.

    It is increasingly popular that resources with different representations and formats are organized to perform various practices within/across enterprises and domains. Process models, involving business process, workflow, Web services and etc., are deemed as a special kind of information resources with complex structure, rich semantics and behavioral features. They are the knowledge carriers of how to fulfill business cooperation, process integration, Web service composition and other web-based applications, including data exchange, state transfer and other behavioral details.

    To follow the current trends of EB or EC and utilize scattered resources in an effective manner, industrial consortia mainly contributed to standardization of domain specific process models using various representation notations and description languages for specific domains, such as BPMN (Business Process Modeling Notation) for business process and OWL-s for Web services. They are very active to standardize expressions and modeling constructs of process models in some specified domains. Especially, ISO 18629 PSL (Process Specification Language) prepared common a set of lexicon and axioms for processes, independently of the behaviors and capabilities of the processes

    However, these specifications mainly concentrate on how to unify the representation of process models from different perspectives, rather than share their reusable pieces and semantic constraints for meaningful interoperation as well as combine them for web-based integration applications. Whats more, not all of them are insufficient to handle

    semantics and support necessary semantic annotation for further intelligent process discovery or integration. More specifically, ISO 18629 was developed to exchange and share discrete manufacturing process information within one industrial department or through several ones. Neither input/output messages nor semantics of the participants is taken into account when creating specification of relevant process information, which might hinder semantic interoperability and coordination of process models across or even beyond manufacturing domain. For this purpose, a unified metamodel is needed to standardize registration and management of heterogeneous process models on the semantic web and facilitate process integration across organizations or domains based on their domain-independent administrative information.

    This part of ISO/IEC 19763 intends to provide a unified framework to register administrative structural information and meaningful semantics of various kinds of process models, based on the ISO/IEC 19763-2 Metamodel Framework for Interoperability Part-2 Core model and ISO/IEC 19763-3 Metamodel Framework for Interoperability Part-3 Metamodel for ontology registration.

vii ? ISO/IEC 2009 All rights reserved

ISO/IEC CD 19763-5:2009(E)

Information TechnologyMetamodel Framework for Interoperability

    Part 5: Metamodel for process model registration

    1 Scope

    The primary purpose of the multipart standard ISO/IEC 19763 is to specify the framework for metamodel interoperability. This part of ISO/IEC 19763 specifies the metamodel that provides a facility to register administrative structural information and meaningful semantics of process models, including workflows, business processes, Web services, etc.

    Figure1 shows the scope of this part of ISO/IEC 19763. The metamodel intends to promote the interoperation among varied kinds of process models and application systems, and finally support process models integration within/across organizations or domains. The objective can be achieved by effectively registering domain-independent administrative information of process models, such as their constitution and corresponding semantic relations.

    Since this part of ISO/IEC 19763 is identified as a common and abstract facility for process model, process model registry based on this metamodel can be used to register and manage administration information of process models, which are widely applied into different domains and application systems.

    MFI CoreMFI Core

    Scope of MFI Process registrationScope of MFI Process registration

    MFI Ontology MFI Ontology Scope of MFI-3Scope of MFI-3MFI Process registrationMFI Process registrationRegistrationRegistration

    Admin. Info. AAdmin. Info. AAdmin. Info. BAdmin. Info. B

    OntologyOntologyProcess modelProcess modelAdministrative information Administrative information Administrative information Administrative information registryregistryregistryregistryof process model Aof process model Aof process model Bof process model B

    referredToreferredTo

    Specifications Process modelProcess modelProcess model AProcess model AProcess model BProcess model Bsupportsupportsuch as PSLrepositoryrepositoryfor application system Afor application system Afor application system Bfor application system B

    Application Application Application Application Application Application interoperationinteroperationinteroperationsystem Bsystem Bsystem Bsystem Asystem Asystem A

    Figure 1 Scope of MFI Process registration

    Additionally, many specifications (such as PSL, OWL-s, etc.) have been developed for different aspects of process information. And as Figure 1 suggests, they can be treated as supplement facilities to enable syntax and semantic interoperability of process models adopted in application systems. Meanwhile, ontology has been widely accepted as the key to realize semantic interoperability of heterogeneous information resources and models. Since the ontology

?ISO/IEC 2008 All rights reserved 1

    ISO/IEC CD 19763-5:2009(E)

    registration metamodel proposed in MFI-3 (Ed1) benefits semantic interoperation based on ontologies, the semantics captured in the registered ontologies based on MFI-3 can be used to promote semantic interoperation between those process models. That is to say, these two members of MFI family can coordinate with each other to support information sharing, exchange and integration among applications on the semantic web.

Notes that the following are outside the scope of ISO 19763-5:

    - modeling notations or descriptive languages for process models;

    - runtime environment or implementation platforms for the execution of process models;

    - protocol and formats details for interoperation between process models.

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 19763-1, Information technology Metamodel framework for interoperability (MFI) Part 1: Reference model

ISO/IEC 19763-2, Information technology Metamodel framework for interoperability (MFI) Part 2: Core model

ISO/IEC 19763-3 (Edition 1), Information technology Metamodel framework for interoperability (MFI) Part 3:

    Metamodel for ontology registration

3 Definitions and abbreviated terms

    3.1 Definitions

    The definitions provided in ISO/IEC 19763-1, ISO/IEC 19763-2 and ISO/IEC 19763-3 shall apply to this part of ISO/IEC 19763.

3.2 Broad terms

    3.2.1 process model

    the result of process modeling, carrying the process knowledge of how to do things in a given context.

3.2.2 sub-process

    component process of composite process models. The instances of sub-processes can be process models at different level of granularity.

3.3 Abbreviated terms

    3.3.1 MFI Process registration

    ISO/IEC 19763-5, Information technology Metamodel Framework for Interoperability Part-5 : Metamodel for

    process models registration

    ? ISO/IEC 2009 All rights reserved 2

    ISO/IEC CD 19763-5:2009(E)

3.3.2 MFI Core

    ISO/IEC 19763-2, Information technology Metamodel Framework for Interoperability Part-2 : Core model

3.3.3 MFI-3

    ISO/IEC 19763-3 (Edition 1), Information technology Metamodel Framework for Interoperability Part-3 : Metamodel

    for ontology registration

3.3.4 OWL-s

    OWL Web Ontology Language for Web services

3.3.5 PSL

    PSL Process Specification Language

4 Structure of MFI Process registration

    4.1 Overview of MFI Process registration

    MFI provides basic information to facilitate registry of various process models and describes administrative information with respect to structure and inherent constraints within process models, including the corresponding constitution, sequence constraints and other semantic restrictions. In MFI Process registration, Base Model and Process Control Model are designed to record structural information and relevant constraints of process models respectively.

    1GoalProcess_Modeling_Language

    -modelType

    1-hasInput-referredToInput1..**

    -realizes1..**ProcessArtifact

    -type : boolean(idl)11

    -hasOutput-referredToOutput2..*1

    *

    1..**

    1Composite_ProcessAtomic_Process

    Figure 2 Base Model of MFI Process registration

    As Figure 2 suggests, Base Model is provided to capture the common structural information of various kinds of process models, such as which sub-processes are involved in the process model, and which artifacts participate in fulfilling the expected purpose. In Figure 2, Process_Modeling_Language is used to specify the modeling language

    that registered process model expresses in. Goal states the purpose that should be achieved by fulfilling the process model, i.e. its main functions. Generally speaking, one process model will have one or more Input to generate one or

    ? ISO/IEC 2009 All rights reserved 3

Report this document

For any questions or suggestions please email
cust-service@docsford.com