1. ISO/IEC/JTC1 SC32/WG2 Jeju Meeting 2009/06/22-27 Updated 2009/08/17, 2009/08/20, 2009/11/17 Masaharu Obayashi (kanrikogaku Ltd.) WG2N1349 Basic Idea on MFI-2 core Model

2. Meaning Triangle (1) Real WorldIn Computer Assignment: Colour := ‘red’; Colour type={‘red’,‘yellow’,‘blue’} “Colour” ‘red’ “Colour” ‘blue’

3. Meaning Triangle (2) UML/ Program “Colour” In Computer

4. Meaning Triangle (3) Attribute “bodyColour of Car” In Computer

5. Meaning Triangle (4) Table “car spec” namebodyColour namebodyColour In Computer

6. “Colour” Component Model Component ModelbyMOF ModelClassifier

7. Model Component Set “Colour” Model Instances Component, Component Set and Instances

8. Sign and Selection Model Component Set “Colour” Model Instances Model Selection sign

9. “Colour” Model Domain Profile specified by specificationModelbyMOF Concept and Domain Profile classifier

10. “Colour” Component and Selection Model Selection

11. “Colour” Model Domain Profile specified by specificationModelbyMOF Concept and Instances classifier Model Instances conceptualized by

12. ModelComponent is unit of registered elements. Actually there are various granularities and abstraction levels. ModelComponentSet is aggregation of ModelComponent. The instance of ModelComponentSet is derived one from power set of ModelComponent. ModelComponent has ModelByMOF s as a formal definition, also includs ModelClassifiers, that are exported from the ModelComponent. ModelClassifier is a role to identify the particular concept and its meaning is specified in the ModelComponent. The instance of ModelComponentSet is the classified grouping elements of ModelComponent. ModelInstance is a role to conceptualize the grouped ModelComponentSet by upper defined ModelConcept. ModelInstance is aggregation again of ModelComponentSet. It seems double packaging of ModelComponent. It intents that ModelComponentSet of ModelInstance is able to be chosen for alternative ModelComponentSet elements. For example, it can be versioning of ModelComponentSet, new one will be added the ModelInstances that has old version of ModelComponent Set. Above all (ModelComponent, ModelComponent Set, ModelInstances) should be registered as common use as possible. The other hand, ModelConcept is designated with ModelSign for human communication. (ModelConcept can exist without any ModelSign). ModelSign is to designate ModelConcept, it is possible to put many ModelSigns to the same ModelConcept as synonym. For example, different terms are used for the same concept if the domains are different. Finally, ModelSelection, it is a very important notion in the MFI core model. ModelInstance consists of ModelComponentSet as mentioned above. The ModelInstances is specified (conceptualized) with upper ModelConcept. However, it has no sign (term) to point it for human communication. ModelSelection is a role of labeling the interesting ModelInstance with registered ModelSign. And, it is able to select the ModelComponentSet in ModelInstances by the selection condition. In sum, ModelSelection is grouping the registered ModelComponents and labeling it with the sign, It includes the intentions such as what ModelSign should be used, which ModelInstances should be adopted, which ModelComponentSet in ModelInstances should be selected. In fact, a ModelComponentSet has different ModelSign via different ModelInstance. From the other side, a ModelSign can be used to stand for the different ModelComponents. ModelSelection, for example, is a role to specify the standard ModelComponentSet such as adopted by each region, business field, group, or company. ModelComponent is able to have sub ModelComponent via ModelSelection. It means that ModelComponent is not directly connected to another ModelComponent. Concrete actual use ModelComponent can be decided from selected ModelInstances, which has the same function (concept), according to the selection condition. In this way, managing and registering information such as framework is able to search the information from various viewpoints according to many purposes. In the example of RoR, the Registry type on display is handled in ModelSign internally in the MFI registry. Comparing selected ModelComponentSet for each business field and analyzing labeled ModelSign, we can find the proper difference of Concept and understand the “ontology” in the true sense of the term. Informal description of MFI-core model

13. Overview sign component instances domain selectioncomponentSet classifier

14. ModelComponent ModelDomainProfile: “MFI-5 ProcessModel” ModelSelection ModelClassifier ２１ ４ ３ Atomic processComposite process MFI-2 and MFI-5 １２３ １ ２ ４ ５ ３ ６ ７８９ ５

15. ModelDomainProfile: “MFI-5 ProcessModel” ModelSelection ModelClassifier ２１ ３ ４ Atomic processComposite process ５ MFI-2-4 and MFI-5 １２３ １ ２ ４ ５ ３ ６ ７８９ １ ２ ３ ４ ５ ６ ７８９

16. Process Metamodel of MFI-5 Complex Process Input Port Simple Process Output port component instances domain profile selection comonentSet classifier １ ２ ３ １ ２ ４ ５ ３ ６ ７８ ９ １ ２ ３ ４ ５ ６ ７ ８ ２１ ３ ４ ５ Process Model

17. A Trial for Implementing ROR 17 http://modelregistry.tiu.ac.jp/

18. Experimental trials RaaS Client Browser SOAP http://mr-devel.tiu.ac.jp http://modelregistry.tiu.ac.jp http://serviceregistry.tiu.ac.jp/WS/mdr ROR Service Registry SOAP WSDL http://serviceregistry.tiu.ac.jp/WS/mfi 18 MDR Registries MFI Registries (Registry Service Integration) 2009/6/1812th Open Forum for Metadata Registry, Seoul, Korea

19. 19 ModelRegistry site as a Registry Service

20. 20 MDR Registries

21. 21 MFI Registries

22. A Trial Implementation for MFI-2-4 model mapping 22 http://serviceregistry.tiu.ac.jp/mfi/project/version3.5/

23. 23 MFI-2-4 Registries

24. 24 MFI-2-4 Registries