1. Issues for Discussion on MFI-9 Wang Jian, He Keqing, Wang Chong, Feng Zaiwen, Fie He Wuhan University, China ISO/IEC JTC1/SC32/WG2 N1526

2. Viewpoints from the Open Group SOA Reference Architecture (http://www.opengroup.org/projects/soa-ref-arch/)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.

3. Logical Solution View of the SOA Reference Architecture

5. The relationships among RGPS

6. 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.

7. 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.

8. Architecture of ODMS 8 MFI Model Registries Selection Record Cache S R G P Role&Goal Registry Process Registry Service Registry Ontology Registry ① ② ⑦ ③ ⑤ ④ ⑥ Model Selection Engine …

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

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

11. 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.

12. 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.

13. The common template for ODMS

14. The process-oriented template

15. The service-oriented template Input at least one of the three iterms

16. Model Selection Case(From Goal to Service)

17. Model Selection Case(From Process to Service)

18. An example Please refer to the document

20. From resolution of Wuhan Meeting, September, 2008 Scope 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

21. Basic 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

22. Contents 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