Baba Piprani (SICOM Canada) Robert Henkel (Transport Canada) A Validation of ISO 19763-2: the Metamodel Framework for Interoperability - Core Model Baba Piprani (SICOM Canada) Robert Henkel (Transport Canada)

Your presenter…Baba Piprani, SICOM Canada Senior IT Consultant with over 30 yrs standardization experience…Computer Languages, SQL, Conceptual Schema, Data Modelliing, IRDS, Metadata Registry, MOF… Developed award winning implementations of standards-based Data Quality Firewalls with advanced generation architecture data warehouses and Web based applications using SBVR, ORM, NIAM, Master Data Management, Metadata Repositories/Registries using SQL DBMSs… Clients: Canadian Government departments Transport, Foreign Affairs, Defence, Superintendent of Financial Systems, Public Works…including private sector, and CNIS (China National Institute for Standardization) Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Agenda Overview of ISO 19763-2 Metamodel Framework for Interoperability - Core Model Object Role Model based schema for 19763-2 Validation Package approach Scoping and Transformation to attribute based model for prototype implementation The ISO 9075 SQL based physical prototype schema Validation Population Validation results Summary and Conclusions Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 The ISO/IEC 19763 Framework for Metamodel Interoperability standard consists of 4 parts: Part 1 – Reference Model Part 2 – Core Model Part 3 – Metamodel for Ontology Registration Part 4 – Metamodel for Model Mapping Part 1 describes concepts and architecture to be applied in the development and registration of individual metamodel frameworks in other parts. Part 2 specifies the core model to describe metamodel items Part 3 specifies the metamodel that provides a facility to register administrative information about ontologies Part 4 provides a metamodel for describing differences in format and type of objects and transformation rules to be exchanged or shared Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 19763-2 Objective: Standardize domain specific business models and standard modelling constructs Provide a unified framework for classifying and registering normative model elements Specify common bases for consistent development and registration of metamodels Establish harmonisation of metamodels that have been developed independently Facilitate their reuse widely across organisations Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 19763-2 Core provides: A set of modeling elements, including the rules for their use, with which to register models An infrastructure for sharing information enabling cooperation between companies in e-business and e-commerce Facilitates sharing of independently developed metamodels and models A set of modeling elements and the rules for their use to support development of metamodels Adherence to the four layer architecture of the Meta Object Facility (MOF) Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Metadata Architecture and artifacts for registration Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Main purpose of ISO/IEC 19763: Metamodel Framework for Interoperability (MFI) To achieve the sharing of common and useful modeling artefacts MFI core model is located within the MOF architecture as a metamodel conforming to MOF Other metamodels described using MOF can also be placed independently within the MOF architecture From the MFI viewpoint, those metamodels are referred as components defined by MOF and UML Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 MFI -Core Packages and Target Models Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

MFI core model as a MOF conforming metamodel MFI core model is located within the MOF architecture as a metamodel conforming to MOF Other metamodels described using MOF can also be placed independently within the MOF architecture Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 19763-2 MFI core model … The MFI core model is organized into five functional packages: Registry Package (normative) Target Package (normative) Relationship Package (normative) ModelClassifier Package (informative) LevelPair Package (informative) Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Figure 4- Registry package in MFI Core Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Figure 5- Target package in MFI Core Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Figure 6- Relationship package in MFI Core Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Agenda Overview of ISO 19763-2 Metamodel Framework for Interoperability - Core Model Validation Package approach Object Role Model based schema for 19763-2 Scoping and Transformation to attribute based model for prototype implementation The ISO 9075 SQL based physical prototype schema Validation Population Validation results Summary and Conclusions Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Validation Package Approach… Transform UML models in MFI packages to Object Role Model (ORM) schema (at the context class level) Analyze ORM schema for inconsistent semantics for further reference Transform ORM schema to attribute based data model using IDEF1X and associated tool ERWin Transform ERWin data model to ISO 9075 based SQL Schema DDL Create Database instance for prototype on MS SQL Server 2005 Populate sample instances in database to validate model as per inconsisten semantics developed in #2 Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Agenda Overview of ISO 19763-2 Metamodel Framework for Interoperability - Core Model Validation Package approach Object Role Model based schema for 19763-2 Scoping and Transformation to attribute based model for prototype implementation The ISO 9075 SQL based physical prototype schema Validation Population Validation results Summary and Conclusions Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Legend Grey : Figure 4 Red : Figure 5 Green : Figure 6 Integrated Object Role Model (ORM) Schema for 19763-2 Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

ORM analysis inconsistencies… Scenario 1: Component to DomainProfile – 2 paths Scenario 2: ComponentSet to Sign– 2 paths Scenario 3: Selection with incorrect association – 2 paths Scenario 4: Classifier to component to item 1 – 2 paths Scenario 5: DomainProfile to Concept to ComponentSet to Component – no reuse, data integrity issues Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Agenda Overview of ISO 19763-2 Metamodel Framework for Interoperability - Core Model Validation Package approach Object Role Model based schema for 19763-2 Scoping and Transformation to attribute based model for prototype implementation The ISO 9075 SQL based physical prototype schema Validation Population Validation results Summary and Conclusions Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 IDEF1X Data Model of Figs 4, 5 Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 ISO 9075 SQL based physical prototype schema…1 Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 ISO 9075 SQL based physical prototype schema…2 Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 ISO 9075 SQL based physical prototype schema…3 Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 ISO 9075 SQL based physical prototype schema…4 Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Agenda Overview of ISO 19763-2 Metamodel Framework for Interoperability - Core Model Validation Package approach Object Role Model based schema for 19763-2 Scoping and Transformation to attribute based model for prototype implementation The ISO 9075 SQL based physical prototype schema Validation population Validation results Summary and Conclusions Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Validation sample population.. Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Scenario 1: Component to DomainProfile – 2 paths ModelComponent population as per IS 19763-2 Fig 4 Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Scenario 1: Component to DomainProfile – 2 paths Populations: ModelComponentSet Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Scenario 1: Component to DomainProfile – 2 paths Populations: ModelConcept Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Scenario 1: Component to DomainProfile – 2 paths Populations: ModelDomainProfile Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Scenario 1: Component to DomainProfile – 2 paths ModelComponent population as per IS19763-2 Fig 4 – Fig 5 Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Scenario 1: Component to DomainProfile – 2 paths ModelComponent population as per IS19763-2 Fig 4 – Fig 5 Possible anomaly : “The [ModelDomainProfile consists of ModelComponent ] must be same as the [ModelDomainProfile that specifies ModelConcept that conceptualizes ModelComponentSet that has [ModelComponent]” Since there are 2 navigatable paths to ModelDomainProfile from ModelComponent when the Registry and Target Package models are integrated, either the rule is needed or the redundant path [ModelDomainProfile consists of ModelComponent] of Fig 5 does not belong. Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Scenario 2: ComponentSet to Sign– 2 paths ModelSelection Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Scenario 2: ComponentSet to Sign– 2 paths ModelSelection Anomaly: Valid values but incorrect associations…. Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Validation sample population..Now add FA2400… Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Scenario 3: Selection with incorrect association – 2 paths Introducing more Populations: ModelComponentSet Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Scenario 3: Selection with incorrect association – 2 paths Introducing more populations: ModelComponent Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Validation sample population..Note following slide discrepancy FA2400 Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Scenario 3: Selection with incorrect association – 2 paths Populations: ModelSelection Valid values but incorrect associations…. Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Scenario 4: Classifier to component to item 1 – 2 paths Add Populations: ModelDomainProfile Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Scenario 4: Classifier to component to item 1 – 2 paths Populations: ModelClassifier Association Anomaly: Currently reads as [ModelComponent has ModelClassifier] or alternatively [ModelClassifier owned by Model Component] Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Scenario 5: DomainProfile to Concept to ComponentSet to Component Add populations ModelComponentSet Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Scenario 5: DomainProfile to Concept to ComponentSet to Component Add populations ModelComponent No Reusability of Components: City, Province, Country Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Metadata Open Forum Sydney - 2008-05-20 Agenda Overview of ISO 19763-2 Metamodel Framework for Interoperability - Core Model Validation Package approach Object Role Model based schema for 19763-2 Scoping and Transformation to attribute based model for prototype implementation The ISO 9075 SQL based physical prototype schema Validation Population Validation results Summary and Conclusions Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Summary and Conclusions Unable to fit Model Component examples into schema Unable to reconstruct from inputed data Unable to reuse – granularity at lowest level not reusable Absence of model semantics rule check on inputted data IDEF1X & IDEF0 – an entity can be matched without constraint with a UML class for a given association---action NOT permitted across 2 semantic model sets IDEF1X can be shared in IDEF0 across 2 model semantics – permitted action this info is missing in model Incomplete solution Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20

Our Vision of 19763 Reference Model. Semantic Models (SBVR, ORM, OWL, RDF) MFI Core Schema Users MFI Services Model Integrity Model Validation Model Consistency Model Exchange Model Registry Model Transforms Attribute Based Models (UML,ER,Relational etc) Systems Applications Platform Independent Models MFI Metadata Registry Baba Piprani / Robert Henkel Metadata Open Forum Sydney - 2008-05-20