1. Status Report of MFI-4 ISO/IEC 19763-4 SC32/WG2 Jeju Korea 25/06/09 Masaharu Obayashi WG2 N1282

2. 2 Update of MFI-4 FCD2 Ballot close: 10 July 2009 Ballot will be closed on 10 th July Documents 32N1846T-text_for_ballot-FCD2_1963-4 32N1847-disp_of_comments-FCD_19763-4

3. 3 Discussion Points on FCD (1) CA01: Definition of ‘pattern’ CA04: Definition of ‘M1 Layer, M2 Layer CA05: Abbreviations of ‘MM-M’, ‘M-V’ CA06: Definition of ‘MOF extent’ CA07: Definition of ‘MM Level’, ‘M Level’ and ‘V-Level’ CA08-11: Explanation of arrow symbols GB03: Definition of ‘Computation’ GB05: usage of term ‘model’ GB06: synonyms of term ‘relation’ and ‘relationship’ GB09: Abbreviations (CA05) GB10: Definition of ‘Layer’ (CA04) GB11: "The MFI Model Mapping is shown as a series of UML Class diagrams, …“ GB12: Datatypes of Attribute definition withdrawn GB14: Abbreviations of ‘MM-M’ (CA07) Metamodel-Model Pair, Model-Value Pair GB15: If this figure is an accurate depiction of the concepts in the standard, it would appear that the concepts are unlikely to support accurate and realistic mapping between models. There are at least two concerns. (1) This implies that when mapping models there is always a one-to-one mapping between 'model instances', whereas in reality mapping is usually many-to-many. (2) As shown in the Figure it would be possible to mismatch "Model Instances" and "Model Concepts". These are serious errors that require the complete revision of the body of the document. GB17: Notation of ‘(from MFI-Core) ’ GB18: "The identifier of sets of transformations rules"

4. 4 Discussion Points on FCD (2) GB19: ‘Code’ in Table 1 should not specified in Conceptual Model GB20: set of valid values in Table1, fixed or expand? GB21: ‘Code’ in Table2 (GB19) GB22: Table 2 cell contents are incorrectly justified. GB24: term "ruleDefinition" does not match GB30: ‘Code’ in Table4 (GB19) GB31: set of valid values in Table4, fixed or expand? (GB20) GB34: ‘Code’ in Table5 (GB19) GB35: set of valid values in Table5, fixed or expand? (GB20) GB36: Figure 3 is unclear GB37: Figure 4 is unclear GB38: "name" and "kind" are inherited from the superclass and should not be redefined here. GB40: ‘Code’ in Table6 (GB19) GB41: set of valid values in Table6, fixed or expand? (GB20) GB42-43: Figure5 and Figure6 is unclear

5. 5 Discussion Points on FCD (3) GB46: It should be made clear how this requirement will be tested. GB48: Annex A is very difficult to read and it is unclear GB49: Annex A: the word “compiler” "Simply stated, a model compiler is a program that reads a transformation definition written in one formal language - the source model - and translates it into an equivalent model in another metamodel - the target model." GB50: Annex B is very difficult to read and it is unclear GB51: Annex C is very difficult to read and it is unclear US02: Is the bold face the correct style for the expansion of the abbreviations? US03: The words “conforming MOF standards” in the following sentence is ambiguous. “The MFI Model Mapping registry model is specified using Administered Items as defined in the Metadata Registry (MDR), and conforming Meta Object Facility (MOF) standards.” Do you mean to exclude standards that are not conforming to MOF? Or something else?

6. 6 Discussion Points on FCD (4) ISO01: Documents listed in Clause 2 shall be referenced "normatively" elsewhere in the document, ISO03: Document incorrectly references itself as "this standard". ISO04: Abbreviated terms are not numbered in International Standards. Caps not necessary and used inconsistently. ISO05: Clause 2 is the conformance clause in International Standards.

9. 2016/2/1(c) 2007 Masaharu Obayashi 9 What is Model Mapping? Framework for Metamodel Interoperability （ MFI ） ISO/IEC DIS 19763-1 Reference model ISO/IEC FCD 19763-2 Core model ISO/IEC DIS 19763-3 Metamodel for ontology registration ISO/IEC CD19763-4 Metamodel for model mapping

10. 2016/2/1(c) 2007 Masaharu Obayashi 10 Objectives This standard is a part of the metamodel framework family of standards. It is based on inheritance of the core model. Modelling method with using UML is coming into common use and MDA （ Model Driven Architecture ） promoted by OMG is a new approach that has come from considering the importance of modelling and model transformation technique. The metamodel framework for model mapping provides a normative metamodel which allows the describing of differences regarding formats and types of objects to be exchanged or shared. This metamodel framework also provides a capability for describing transformation rules between different objects in term of a meta ModelInstances.

11. 2016/2/1(c) 2007 Masaharu Obayashi 11 Model Transformation The tool based on MOF is useful for specifying and implementing the transformation rules. Such supporting tools use specialized transformation description languages. A formal transformation description language is needed to define complex transformation rule and share transformation among different tools. For example, OMG MOF QVT (Query, View and Transformation) is a formal transformation language to specify transformation rules precisely and availably. The model compiler is the function of generating simple codes from a model. A main important function supporting MDA is a function of transformation between one model and the other model. Illustrates the basic structure of the MFI for Model Mapping that could be minimal set of metamodel for representing both mapping targets and mapping rules.

12. 2016/2/1(c) 2007 Masaharu Obayashi 12 Terminology on QVT MOF QVT (Query, View and Transformation) a formal transformation language used to specify transformation rules Mapping a mapping is a potentially directed transformation implementation pattern a pattern describes the ’shape' of an object it will be matched against pattern matching a process whereby parts of a model are matched against a pattern Query a query takes as input a model and selects specific elements from that model Relation, relationship a multi-directional transformation specification, relations are not executable in the sense that they are unable to create or alter a model; they can, however, check two or more models for consistency against one another. transformation a process of automatic generation of a target model from a source model according to a transformation definition NOTE Transformation is the umbrella term for relation and mapping. view a view is a model that is derived from another model

13. 2016/2/1(c) 2007 Masaharu Obayashi 13 RDF OWL Common Logic Topic Map Mapping UML to RDF Mapping RDF to OWL Mapping OWL to CL Mapping Examples UML Mapping Topic Map to OWL

14. 2016/2/1(c) 2007 Masaharu Obayashi 14 MFI-4 Package

15. 2016/2/1(c) 2007 Masaharu Obayashi 15 MFI model mapping Metamodel

16. 2016/2/1(c) 2007 Masaharu Obayashi 16 Kind of Transformation

17. 2016/2/1(c) 2007 Masaharu Obayashi 17 Translation Rule Type

18. 2016/2/1(c) 2007 Masaharu Obayashi 18 MM-M Transformation Kind (1)

19. 2016/2/1(c) 2007 Masaharu Obayashi 19 MM-M Transformation Kind (2)

20. 2016/2/1(c) 2007 Masaharu Obayashi 20 Transformation Kind (1) Example UMLOWL Mapping UML to OWL

21. 2016/2/1(c) 2007 Masaharu Obayashi 21 M-V Transformation Kind (1)

22. 2016/2/1(c) 2007 Masaharu Obayashi 22 M-V Transformation Kind (2)

23. 2016/2/1(c) 2007 Masaharu Obayashi 23 Transformation on HL7 (1)

24. 2016/2/1(c) 2007 Masaharu Obayashi 24 Transformation on HL7 (2)

25. 2016/2/1(c) 2007 Masaharu Obayashi 25 Transformation on ebXML (2)

26. 2016/2/1(c) 2007 Masaharu Obayashi 26 Transformation on ebXML (1)

27. 2016/2/1(c) 2007 Masaharu Obayashi 27 Transformation on MDA

28. 2016/2/1(c) 2007 Masaharu Obayashi 28 Transformation on CWM (1)

29. 2016/2/1(c) 2007 Masaharu Obayashi 29 Transformation on XSLT

30. Sample models (UML version) (original from Keith of UK)

31. Component with Classifier B::UNIT A::DEPOT C::UNIT TYPE C::UNIT B::UNIT B::SUPPLY UNIT B::OTHER UNIT A::DEPOT A::SUB DEPOT A::SUPPLY UNIT A::UNIT

32. Domain Profile A::DEPOT A::SUB DEPOT A::SUPPLY UNIT A::UNIT B::UNIT B::SUPPLY UNIT B::OTHER UNIT C::UNIT TYPE C::UNIT A::DEPOT B::UNIT C::UNIT TYPE Domain Profile::UNIT MODEL

33. Sign-Concept- Component Set and Selection A::DEPOT A::SUB DEPOT A::SUPPLY UNIT A::UNIT B::UNIT B::SUPPL Y UNIT B::OTHER UNIT C::UNIT TYPE C::UNIT A::DEPOT B::UNIT C::UNIT TYPE Domain Profile::UNIT MODEL Concept::UNIT Component Set:: UNIT MODEL Sign::unit Sign::depot Sign::sub depot Sign::supply unit Selection::UNIT

34. Conceptualization by Abstract Syntax- Expression A::DEPOT A::SUB DEPOT A::SUPPLY UNIT A::UNIT B::UNIT B::SUPPLY UNIT B::OTHER UNIT C::UNIT TYPE C::UNIT A::DEPOT B::UNIT C::UNIT TYPE Domain Profile::UNIT MODEL Concept::UNIT Component Set:: UNIT MODEL Sign::unit Sign::depot Sign::sub depot Sign::supply unit Selection::UNIT

35. Model Mapping A::DEPO T A::SUB DEPOT A::SUPPLY UNIT A::UNI T B::UNIT B::SUPPL Y UNIT B::OTHER UNIT C::UNIT TYPE C::UNIT A::DEPOT B::UNI T C::UNIT TYPE Domain Profile::UNIT MODEL Concept::UNIT Component Set:: UNIT MODEL Sign::unit Sign::depo t Sign::sub depot Sign::supply unit Selection::UNI T MM-Level M-Level

36. Model Domain Profile Model Domain Profile Model Component Set Model Component Set Model Component Model Classifier ModelByMOF Model Component Model Classifier ModelByMOF Model Domain Profile Model Domain Profile Model Instances Model Concept Model Concept Model Instances Model Component Set Model Component Set Model Component Model Classifier ModelByMOF Model Component Model Classifier ModelByMOF value Metamodel Level Rule Model Level Rule Relationship Mapping Source Target

37. Model DomainProfile Model ComponentSet Model DomainProfile Model ComponentSet Projection II Relationship Act Role Source ModelComponent Target ModelComponent Source ModelComponent Target ModelComponent Role Act RIM DMIM RMIM Act1 Role1 Act2 Role2

38. Model DomainProfile Model ComponentSet Model DomainProfile Model ComponentSet Compilation Relationship Act Role Source ModelComponent Target ModelComponent Source ModelComponent Target ModelComponent Role Act RIM HMD RMIM Act3 Role3 Act2 Role2 DMIM HDF RMIM Mapping

39. Model DomainProfile Model ComponentSet Model DomainProfile Model ComponentSet Transfer Relationship cc1 cc2 Source ModelComponent Target ModelComponent Source ModelComponent Target ModelComponent CC3 CC4 CCLib BCC/ ACC BBIE/ ABIE Acc1 Bcc1 Abie1 Bbie1 BCC/ ACC

40. Model DomainProfile Model ComponentSet Model DomainProfile Model ComponentSet Transfer Relationship Cc1 Cc2 Source ModelComponent Target ModelComponent Source ModelComponent Target ModelComponent Cc2 Cc1 CCLib BPM BBIE/ ABIE Abie1 Bbie1 Abie1 Bbie1 BCC/ ACC UMM BBIE/ ABIE Relationship Instance of

41. Model ComponentSet Model Component Set Projection I table2 table1 Source ModelComponent Target ModelComponent Source ModelComponent Target ModelComponent table3 table4 SQL Value1 Value2 value1 value2 value4 value3 Compilation Computation Mapping Instance of

42. Model DomainProfile Model ComponentSet Model DomainProfile Model ComponentSet Transfer Relationship MetaClass 1 Source ModelComponent Target ModelComponent Source ModelComponent Target ModelComponent CWM ER SQL table2 table1 table4 table3 MetaClass 3 MetaClass 2 Instance of

43. Model ComponentSet Model ComponentSet Compilation element2 element1 Source ModelComponent Target ModelComponent element3 element4 XML Value1 Value2 value1 value2 value4 value3 Computation Mapping Instance of