1. ISO/IEC CD 19763-2 and WD19763-4 : Core Model and Model Mapping ISO/IEC JTC1/SC32/WG2 18-21 April 2005-Berlin, Germany SC32/WG2 Japan (Kanrikogaku Ltd) Masaharu Obayashi

2. MMF-2 Status ISO/IEC 19763-2 Core model Information technology -- Framework for Metamodel interoperability Part 2: Core model Progress status WD 2003-11-06 SC32 N1065 1st CD 2004-02-04 SC32 N1086 (summary SC32 N1140) 2nd CD 2004-11-19 SC32 N1186 (summary SC32 N1234) Editor’s Draft for 3rd CD SC32WG2 Nxxxx dispositions  SC32WG2 Nxxxx for 1st CD 2004-02-04 SC32 N1086  SC32WG2 Nxxxx for 2 nd CD 2004-11-19 SC32 N1186

3. Feature of MMF Core Modeling Artifacts to be registered Metamodel, Model, Value sets, Vocabulary, Template, Pattern etc. UML (domain) profile including metamodel and model Artifacts based on OMG ODM (Part3) Artifacts based on MOF QVT (part4) The other such as document, spreadsheet, XMLshcema etc. Classification for components From viewpoint of “Sign-Concept-Instances” Basic Metadata Administered Item (from ISO/IEC 11179 MDR) Selection of instance sets for a particular purpose usage Assembly (Composition) of registered components Plug and Play with selection Core Framework for registering Ontology and Model Mapping

4. Changes at 2nd (draft) CD 1 st CD reviewed and revised based on 1 st CD comments and resolutions, also discussion with experts Change the relationship to MDR and MOF Administered Item from MDR Avoid direct inheritance from MOF (only use MOF/XMI) Change the package structure Divide normative part and informative part Harmonize metamodel with Ontology (part 3) and Model Mapping (part 4)

5. Changes at Editor’s draft 3rd CD Editorial Changes Fully Follow the disposition of 1st CD ballot summary Reflect the comment from the OMG expert Modified partially by the draft disposition of 2 nd CD ballot summary Metamodel Changes Introduce Association Type Refine the specification on the relationship between ModelConcept and ModelInstances Add Examples Add and replace Figures

6. 4 Layer Metadata Architecture LayerDescriptionExamples Metametamodel Foundation for a Metamodeling Architecture. Defining the language to describe metamodels MetaClass, MetaAttribute, MetaOperation Metamodel An Instance of a metametamodel. Defining the language to describe models. Class, Attribute, Operation, Component Model An Instance of Metamodel. Defining a language to describe the information object domain. Product, Unit Price, Customer, Sale, Detail User Objects （ User Data ） An Instance of a Model. Defines specific information Domain,, $100, $200

7. An Example: UML metamodel in the 4 Layer

8. What is Profile (cont’) Contains mechanisms that allow metaclasses from existing metamodels to be extended to adapt them for different purposes. This includes the ability to tailor the UML metamodel for different platforms (such as J2EE or.NET) or domains The profiles mechanism is consistent with the OMG MOF. A profile package can specify a related model library and identify a subset of the UML metamodel that is applicable for the profile A domain metamodel is defined as a UML profile.

9. Pattern : Universe of Discourse Modeling Constructs Metametamodel Stereotype : Template: MetaModel Modeling Facility governing M3 M2 M1 M0 Model Object Overview of Metamodel Framework

10. ProvinceCountryCity StateCountyPrefecture Political Boundary Model Metamodel Example

11. ProvinceCountryCity StateCountyPrefecture Country Japan City tofudokenshichokuson renaming refining specifying refining Political Boundary Model Base Model Japan Local Boundary Model Variant Model

12. Nara TokyoKyoto M0 M1 M3 M2 MOF Base-Variant Abstract Syntax- Expression

13. Kyoto Tokyo Vocabulary Prefecture To-do-fu-ken Super-Sub Vocabulary Example Nara To-do-fu-ken Japan Area Japan Region Global Region

14. Tokyo Nara Kyoto To-do-fu-ken Prefecture Area Region Vocabulary Global Region Boundary Japan Area Selected and specified selected Japan Region

15. Framework of Registering (Key Idea) Sign-Concept-Instances Sign  a symbol designating a named element in a namespace.  Namespace is a collection of signs Concept  specify meaning of sign.  generally expressed with sign. Instances  a set of instance of the Concept designated by a sign. Selection a result of selecting a set of model instance from referents designated by a sign.

16. Instances (of the model associated by the metamodels) Concept (expressed by metamodelsin domain) Concept, concept, …… Model Registering Sign (evoking Concepts) evokes refers to stands for Selection

17. “Auto cycle” Component “Bicycle” Component “Trailer” Component “Car” Component “Ambulance” Component “Bus” Component concept referesTo “Vehicle” Class Vehicle sign evoked “Truck” Component instances selection domain classifier

18. Basic Scheme of MMF Core Type1: Type-Instance Type2: Super-Sub Type3: Base-Variant Type4: Abstract Syntax-Expression

19. Type3: Base-Variant “Base-Variant” is an association type between a base model and its variant models that are created by modifying the base model according to the permitted operation. There are operations such as renaming, specifying, refining, substituting, extending and merging. In the association type “Base-Variant” many operations above are performed on a base model partially and many times. Eventually, the lower model will be derived from the upper base model. The detail specification on specifying such operations should be provided as a ModelSpecification for each registering target.

20. MMF Core Metamodel (1)

21. Framework of Registering Model Sign-Model Concept-Model Instances Model Sign  designate a named element in a namespace.  Namespace is a collection of signs defined by a submitted organization  Signs should be unique within the particular Namespace ModelSign

22. Framework of Registering (cont’) Model Sign-Model Concept-Model Instances Model Concept  Specify meaning of the sign.  Defined by a Model Classifier in the Model Domain Profile  The sign is corresponding to a Model Classifier ModelConcept ModelClassifier ModelDomainProfile

23. Framework of Registering (cont’) Model Sign-Model Concept-Model Instances Model Instances  Provide a set of instances of the Model Concept  Consists of a Model Component  should satisfy the constraints specified by the Model Concept. ModelInstances ModelComponent

24. Framework of Registering (cont’) Model Selection  Model Selection is a result of selecting a set of model components from Model Instances designated by the sign. ModelSelection

25. Target Objects World Structure of Registered Target Objects Multi-forest  There are many SDOs and organizations that will develop and register a Model Concept  A set of Model Concepts may be registered as a family Multi-layer  There are several types of association between a Model classifier in a Model Concept and a corresponding Model component in a Model instances.  A Model component may be also registered with another Model classifier in the same Model Concept or the other one (from multi-viewpoint). Multi-component  A Model classifier may consist of elements including external objects that are selected from in another registered Model instances

26. Metamodel of Registered Target Structure Model Domain Profile Model Specification Model Classifier Model Selection Model Component Upper Model

27. “Auto Bicycle” Component “School Bus” Component “Bicycle” Component “Sport Car” Component “Highway Bus” Component “F1 Car” Component concept Set of components referesTo “Vehicle” Class Vehicle sign evoked “Sedum” Component “Car” Class Car evoked instances “Automobile ” Class Automobile evoked “Bus” Class Bus evoked referesTo child

28. Administered Items in Core ModelComponent ModelSign ModelConcept ModelDomainProfile ModelInstances ModelSelection

29. Association Type 1 Type-Instance Super-Sub Base-Variant Abstract Syntax-Expression

30. Type 1: Type-Instance “ Type-Instance ” is an association type between a class and its object. The class diagram in a model package and its object diagram may be included.

31. “US” Object “Korea” Object “China ” Object “Japan ” Object “UK” Object “Canada” Object concept Set of Instance (Country) referesTo “Country” Type-Instance Country Class sign evoked

32. “US” Object “Korea” Object “China ” Object “Japan ” Object “UK” Object “Canada” Object concept Set of Instance (Country) referesTo “Country” Country Class sign referesTo “Asian Country” Asian Country Class Type-Instance evoked

33. Association Type 2 Type-Instance Super-Sub Base-Variant Abstract Syntax-Expression

34. Type 2: Super-Sub “ Super-Sub ” is an association type between a super class and its inherited sub classes. A model package and its sub packages may be included.

35. Asian Country Class APEC Country Class EU Country Class concept Set of Instance (Country Group) “Country Group” Country Class sign referesTo Super-sub (generalization) evoked

36. Association Type 3 Type-Instance Super-Sub Base-Variant Base is a source model such as pattern or template Variant is a derived model from the Base with operation such as renaming, specifying, refining etc. Abstract Syntax-Expression

37. Japan Local Boundary Model US Local Boundary Model Korea Local Boundary Model concept Set of Instance (Country Boundary Model) “Political Boundary Model” Political Boundary Model sign referesTo Base-Variant (derivedFrom) evoked

38. ProvinceCountryCity StateCountyPrefecture Country Japan City tofudokenshichokuson renaming refining specifying refining Political Boundary Model Base Model Japan Local Boundary Model Variant Model

39. Operations on Base-Variant OperationDescription Renaming Change the name of such as class and attribute into the appropriate name in the context Specifying Specify a model element of the base model within permissible range. For instance, -Fix the cardinality of an association end or limit the range. -Select a code set for an attribute or indicate permissible values. -Select effective attributes and remove unused ones. -Select and fix a subclass in a class hierarchy -Remove unused association Refining Refining the model elements in a base model. For instance, -Add a subclasses that is enhanced with attributes and operations -Add a constraint that is applied in the particular context Substituting Substituting the model component in a base model. For instance, -Replace a universal component into the component used in a particular local region. -Replace the old version of a component into the new one. Extending Add a new class or association to a base model Merging Combine and assemble base models into a new model.

40. Association Type 4 Type-Instance Super-Sub Base-Variant Abstract Syntax-Expression Upper Model provides Abstract Syntax Lower Model is a model expression with the syntax

41. Type4: Abstract Syntax-Expression “Abstract Syntax-Expression” is an association type between an upper metamodel and a lower model. In this case, the upper model in a ModelDomainProfile provides a metamodel. The lower model must be described according to the abstract syntax. Usually, stereotypes of UML are defined by such metamodels as a UML profile. The lower model will be drawn using those stereotypes.

42. Political Boundary Model US Local Boundary Model concept Set of Instances (Boundary Model) “Boundary Model” Boundary Metamodel sign referesTo Abstract Syntax-Expression (govern) evoked Japan Local Boundary Model Korea Local Boundary Model

43. Set of Area in Region Region in Global Area neighborhood Boundary Metamodel Expression Abstract Syntax Metaclass-Class

44. Example: The concept “Political Boundary Model” with Association Type 3 & 4

45. Japan Local Boundary Model US Local Boundary Model Korea Local Boundary Model concept Set of Instance (Political Boundary Model) “Political Boundary Model” Boundary Metamodel sign referesTo Base-Variant (derivedFrom) Political Boundary Model Abstract Syntax-Expression (governedBy) evoked

46. Example: Registry Target based on UML Profile

47. UML2.0 Core Package BtoB diabetes Observation Administration Author AssignedEntity Integer CloumnSet Table String Cloumn View M0 Vocabulary SQLTable Datatype Act Role Logistics lung cancer diabetes LOINC Observation M1 Base-Variant Type- Instance UML 2.0 Superstructure M3 M2 MOF Base-Variant Super-Sub Selected and specified selected Abstract Syntax-Expression MOF 2.0 CWM UML Profile EDOCMOF 2.0 QVTEAI Healthcare EHR

48. Issues and work items on CD 19763-2 Technical 3.1 MOF Terms used in specifying the MMF metamodel The MOF Terminology in this clause came from the Glossary of MOF 1.4 Specification in OMG. However, the MOF PAS submission as ISO/IEC 19502 does not include the Glossary. The definitions below should be reconsidered and checked if those are appropriate or not. 5. Conformance add the the statements about conformance criteria Editorial Refine the specification Cross check the content with the other parts. Proofreading and refinement as English Target Date for 3 rd CD circulate editor’s final draft 2005-05-15 request comment and review by 2005-5-20 submit the document 2005-06-01

49. MMF-4 Status ISO/IEC 19763-2 Metamodel for Model Mapping Information technology -- Framework for Metamodel interoperability Part 4: Metamodel for Model Mapping Progress status WD 2004-05-09 SC32 N1109 Expert’s Draft for 1st CD SC32WG2 Nxxxx

50. What is Model Mapping? Framework for Metamodel Interoperability （ MMF ） ISO/IEC CD 19763-1 Reference model ISO/IEC CD 19763-2 Core model ISO/IEC WD19763-3 Metamodel for ontology registration ISO/IEC WD19763-4 Metamodel for model mapping

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

52. Model Transformation Tool 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 MMF for Model Mapping that could be minimal set of metamodel for representing both mapping targets and mapping rules.

53. Overview of Model Mapping Example: A transformation from a domain model on PIM into the same domain model on PSM. Transformation tool should be specified Model transformation definition

54. Model Transformation types of model transformation Type1: from upper level model into lower level model Type2: from implementation model into object code Type3: from conceptual model into object code Type4: from conceptual model to conceptual model

55. Basic Framework of registering MMF model mapping

56. Framework for Model Mapping

57. Projection type1 and Compilation -Model Relationship -Model Renaming -Model Equivalence -Model Enhancement -Model Transformation -Model Generation -Model Migration -Model Derivation -Value Computation -Value Aggregation -Value Conversion

58. Projection type2

59. Metamorphosis

60. MMF model mapping Metamodel The MapTable is a metaclass designating the metamodel/model/vallue transformation definition between source and target metamodel/model/value. The ModelTable is a metaclass designating the source/target metamodel of metamodel transformation. The Transformation is a metaclass designating an unit of model transformation between source and target including metamodel, model and value transformation definition respectively.

61. Model Transformation Example Simple UML metamodel Simple RDBMS metamodel Reference: Revised submission for MOF 2.0 Query/View/Transformation RFP (ad/2002-04-10) QVT-Merge Group version 2.0

62. Model Transformation Example (cont ’ ) Graphical Notation Textual Notation

63. Issues and work items on CD 19763-4 Technical Provide the concrete example using MOF QVT add the the statements about conformance criteria Editorial Review and Refine the specification Cross check the content with the other parts. Proofreading and refinement as English Target Date for 1st CD circulate editor’s final draft 2005-05-15 request comment and review by 2005-5-20 submit the document 2005-06-01

64. Thanks obayashi@kthree.co.jp

65. Annex for discussion

66. Administered Items 19763-2 (core) 19763-3 (ontology) 11179-2 11179-3 MOF/ XMI 19763-4 (Model Mapping) ODM QVT OWL SCL RDF DL FOL TM OMG W3C ISO XMDR Access API ER ebXML Artifact HL7 Artifact MDR Artifact OMG Artifact Relationship among related Standards (for discussion) UML used registered

67. Metamodel Modeling ConstructsModeling FacilityDomain Model Metametamodel governing UOD Universe of Discourse governing Expression Vocabulary, Lexicon Language Architecture Syntax English

68. have I1 Car A have I2 Car B have I2 Car B Car A I1 SV NounVerb have car I want book We M0 Vocabulary Noun Verb O POS Sentence symbol … “S V O” is a rule for sentence I have a carWe have cars M3 M2-1 M1 … MOF “S” is a symbol for Subject “V” is a symbol for Verb “O” is a symbol for Object Noun is a POS (part of speech ) Verb is a POS Subject is Noun Object is Noun A rule is a sequence of symbols NL Metamodel supply I1 I2 Car A Car B Sign for “I” Sign for “Car” supply M2-2

69. “S” is a symbol for Subject “V” is a symbol for Verb “O” is a symbol for Object Noun is a POS (part of speech ) Verb is a POS Subject is Noun Object is Noun A rule is a sequence of symbols “S” have “O” have XA1 I1 I2 Car A Car B have car I want book We M0 Vocabulary Noun Verb Sign for “I” Sign for “Car” “I1” have a “Car A” X Y A1 A2 Sign for “I1” Sign for “Car A” M1-1 M1-2 S V O Base-Variant Type- Instance “S V O” is a rule for sentence M3 M2-1 M2-2 MOF Base-Variant Super-Sub NL Metamodel select Abstract Syntax- Expression

70. I Car have I a Car English have car I want book We M0 ModelDomain Noun Verb Japanese Profile (with metamodel) NL (Natural Language) metamodel … “English NL” Registry I have a car We have cars M3 M2-1 M1 M2-2 MOF Component (Vocabulary) Model Registry for “Noun”Registry for “Verb” … Registry for “Sentence” Wehave want MMF Core Model … supply register Registered objects with administered Item Base- Variant Abstract Syntax- Expression

71. CWM: SQL Metamodel

72. CWM: SQL Metamodel and Model M2 M1

73. UML2.0 Core Package BtoB diabetes M0 Logistics M1 M3 M2 MOF Base-Variant CWM Healthcare EHR CWM: SQL Metamodel BtoBHealthcare Abstract Syntax- Expression Base-Variant

74. View Table Vocabulary ColumnSet NamedColumnSet Super-Sub CWM: Vocabulary in SQL Metamodel QueryColumnSet

75. Observation Administration Author AssignedEntity Act Role View Table Vocabulary ColumnSet NamedColumnSet QueryColumnSet Healthcare Selected and specified selected CWM: Model