Issues for Discussion on Issues for Discussion on MFI-9MFI-9

Wang Jian, He Keqing, Wang Chong, Feng Zaiwen, Fie He

Wuhan University, China

ISO/IEC JTC1/SC32/WG2 N1526

Viewpoints from the Open GroupViewpoints from the Open Group SOA Reference Architecture (

http://www.opengroup.org/projects/soa-ref-arch/) The Open Group is a vendor and technology-

neutral industry consortium, currently with over three hundred member organizations.

Logical Solution View of the SOA Logical Solution View of the SOA Reference ArchitectureReference Architecture

The relationships among RGPSThe relationships among RGPS

Comments: How to register the relationships among RGPS, as well as the relationships between Ontology and RGPS?

We think that different relationships can be registered by different people, and we donnot need to maintain a separate registry to record the relationship among each part.

Process registry can register the relationships with Role&Goal; Service registry can register the relationships with Role&Goal, and Process.

The relationships between ontology and the RGPS registries should be recorded by each registry in RGPS.

Comments: The interaction between users and the selection engine should be clearly defined by a certain process language such as BPMN.

We have defined some interaction patterns between different kinds of users and selection engine. BPMN is used to describe these interaction patterns.

Architecture of ODMSArchitecture of ODMS

8MFI Model RegistriesMFI Model Registries

Selection Selection RecordRecordCacheCache

S

RG

P

Role&Goal Role&Goal RegistryRegistry Process Process

RegistryRegistry

Service Service RegistryRegistry Ontology Ontology

RegistryRegistry

①

②

⑦

③

⑤

④⑥

Model Model Selection Selection EngineEngine

……

The Interaction between User and Selection The Interaction between User and Selection Engine (General)Engine (General)

The Interaction between User and Selection The Interaction between User and Selection Engine (Detailed)Engine (Detailed)

Comments: Clarify the difference between MFI-9 and MFI-6(Registration Procedures).

We think that MFI-9 just specifies how different kinds of users can select their appropriate models/services based on the registered relationship among these registries. It does not consider the registration procedure of each registry, which is the focus of MFI-6.

MFI-6 concentrates on how to register models in each registry, and it is mainly used by technical experts; while MFI-9 focuses on how to use the registration information, and it can be used by end users.

Comments: Consider that different kinds of users (such as developer and end user) may use different template when defining templates.

We agree that different kinds of users may use different kinds of template.

The common template for ODMSThe common template for ODMS

The common template for ODMS

The process-oriented templateThe process-oriented template

The service-oriented templateThe service-oriented template

Input at least one of the three iterms

Model Selection Case(From Goal to Service)Model Selection Case(From Goal to Service)

Return services to the user

Achieves:Process->Goal

Performs:Service->Process

Can the resul ts sati sfy the user?

yes

TakesChargeOf Role->Goal

TakesChargeOf Role->Goal

Given the goal , search for i ts subGoals in

MFI-8 regi stry

Decomposes:Goal ->Operational Goal

Given a goal , search for the servi ces that achieve i t in MFI -7 regi stry

Given the goal , search for

processes that achieve i t and

thei r subprocesses in MFI-5 regi stry

Given a process, search for the services that perform i t in MFI-7 regi stry

no

Given the goal , search for the role that takes charge

of i t in MFI-8 registry

Given the role, search for other

rel ated goals taken charge by

i t in MFI -8 regi stry

Get users’ request(expressed as a

goal )

Return services to the user

Achieves:Process->Goal

Achieves:Service->Goal

Can the results satisfy the user?

yes

involvedByProcess->Role

involvedByProcess->Role

Given the process, search for its

subprocesses in MFI-5 registry

Decomposes:Process->subProcess

Given a process, search for the services that

perform it in MFI-7 registry

Given the process, search for goals

achieved by it and their subgoals in

MFI-8 registry

Given a goal, search for the services that

achieve it in MFI-7 registry

no

Given the process, search for the role that involves it in

MFI-8 registry

Given the role, search for other related processes involved by it in MFI-5 registry

Get users’ request(expressed as a

process)

Model Selection Case(From Process to Model Selection Case(From Process to Service)Service)

An exampleAn example Please refer to the document

From resolution of Wuhan Meeting, September, 2008

Scope of MFI-9Scope of MFI-9 Specify a technical guideline on how to use

RGPS metamodels to select appropriate combinations of models and/or services to meet users' goals.

Specify how to use the RGPS infrastructure to support operational harmonization and interoperability within and between industries.

20

Basic Idea of MFI-9Basic Idea of MFI-9

Faced with the personalized and diverse requests of users, how to select appropriate models from abundant and heterogeneous model resources These models registered in MFI registries can be

semantically annotated by ontologies and connected by RGPS.

According to the matching between users' requests and registration information of models, appropriate models can be selected to satisfy users' requests.

21

Contents to be covered in MFI-9Contents to be covered in MFI-9 The relationship of the RGPS models Specify the different kinds of users’ requests Define model selection strategy based on RGPS

relationship Model selection evaluation

Basic principle to evaluate the selection result from the viewpoint of the user and the registry