730 likes | 748 Views
This study examines the current status and expectations for the Metamodel Framework Standard for Interoperability (MFI), focusing on database requirements and other related issues. Topics covered include the MFI standards, requirements for DB technology, and the structure and registration process of MFI.
E N D
Study Period Meeting, Clearwater, FL, Jan. 05, 2007. JTC1 SC32N1635 Database requirements to support MFI: Next Stage of The Metamodel Framework Standard for Interoperability: (ISO/EC19763) Hajime HORIUCHI ISO/IEC JTC1 SC32WG2, Tokyo International University hori@tiu.ac.jp
Topics 1. Current Status of MFI (ISO/IEC 19763) Series of Standards 2. Expectations to MFI 3. What are needed 4. Requirements for DB technology 5. Other Issues
Metamodel Framework for InteroperabilityISO/IEC 19763 Meta Modeling Facility (MOF) Defining Facility (ISO11179 MDR) ISO/IEC19763 Part-1: Reference Model Part-2: Core model Part-3: MM for Ontology Part-4:MMfor Model Mapping Core model of Meta Model Frameworks Metamodel for Ontology Common Identification & Classification Metamodel for Model Mapping Metamodel for Model Constructs metadata Mapping Rules Codes Mapping Targets Value Domains Sharable model MOF and ODM (OMG) Patterns Common Modeling Facility (UML) Model Mapping CommonModel Constructs
Metamodel Framework Architecture M3 MOF Model inherit Core Model inherit MFI M2 Metamodel Metamodels describe Common Data M1 Domain Models Modeling Element Facility Object Patterns use refer Modeling Constructs M0 Values Real World Concept
MFI structure Registration Procedure <<extension>> Ontology Evolution Specific metamodel for the mapping, defined on the core model Model Mapping (Part-4) Model constructs Registration Ontology Registration (Part-3) Specific metamodels defined on the core model Core model (Par-2) Provides model registration mechanism as metamodel Reference Model (Part-1) Defines over all concept of MFI
Latest Status of MFI Standards ISO/IEC19763 : Information technology: Metamodel framework for interoperability • Part 1:Reference model • Part-3: Metamodel for ontology registration IS published on February 1st, 2007 • Part-2: Core model 2ndFCD, FDIS expected by July 2007 • Part-4: Metamodel for model mapping 2nCD, FCD expected by July 2007
Model Sign Model Concept Model Selection Model Instance EX: Registration of Model Concept Concept Upper Model Model Type Model Domain Profile Classifier Attachment A Model XMI schema Target of registration Model Specification Document
Relationships are not in one type Y W Z Type - Instance Syntax - Expression Super - Sub X V Base -Variant
How to represent relationships ISO/IEC 19763-2 : Framework for Metamodel Framework for Interoperability: Core Model Upper Model • Type and Instance • Super and Sub • Base and Variant • Abstract Syntax and Expression Target Model
MOF and MFI Core M3 Layer M2 Layer Target Models
Common facility of MDR(ISO/IEC11179) ISO/IEC19763-3 Metamodel for ontology registration MOF MFI-2 MFI Core model MDR standards ODM MFI-3 Metamodel for Ontology Registration Metamodel for MDR(ISO/IEC11179) Metamodel for Metamodel for DL Metamodel for OWL registration Administration Record Describe Data Elements Terminology Basic Classes Basic Relationship Any Ontology Ontologyby ODM
Concept) Concept) Concept) Concept) Concept) Concept) Key Objectives of MFI-3 Admi. Info Upper Ontology or Existing Ontology Reference Ontology Registry Admi. Info Local Ontology Concept) Concept) Concept) Concept) Concept) Concept) Concept)
ODM(Ontology Descriptive Metamodel) • MOF compliant Ontology Description Metamodel • Metamodels for OWL(WebOntology Language),DL(Description Language), • CL(Common Logic), etc. RDF Schema M3 Meta-meta model (MOF) M2 Mapping Other UML profile Ontology UML profile ODM OWL OWL M1 Models
Role of MFI NRR NRR:National Repository& Registry International Industry specific Models Industry specific Models Inter-Company Company A Company B Model Web system Intra-Company システム開発 ツール アプリケーションシステム System Dev. Tools Application System
LCDM Project in Construction Industryof Japan Road Road Disaster River Disaster River Weather Traffic Weather Traffic Standard Where is my home LCDM Platform Address? Place? Point? Location? Data Integration Citizen
Industrial Expectation System Integrator Management MFI Registry ERP Vender Planer Real World Business process Requirement ASP Venders Programmer Model DBMS Venders System Function Program Web Service Venders Project Management
Registry Federation Automobile Transport Trading Construction 物流CC/BIE 自動車CC/BIE Iron Steel 貿易CC/BIE 建設CC/BIE 鉄鋼CC/BIE 流通CC/BIE Hong-Kong CC/BIE KIEC CC/BIE ECOM CC/BIE UN/CEFACT TBG & ICG/ATG ISO/IEC SC32 + eAC Ad-Hoc Project ebXML Asia Registry
Common Platform for EC (ECOM Japan) Software Vender ASP Collaboration Interoperation Common Registry As Platform 流通業界 標準 COXEC 標準 System Collaboration Transmission Protocol YYY 標準 XXX 標準 Business Information Operation Representation ECALGA 標準 自動車業界 標準 UN/CEFACT標準 Korea St Taiwan ST China ST
MFI-New Parts under the Study http://www.tiu.ac.jp/org/forum-01/index.files/Page694.html
Works in the Study • A Metamodel for Ontology evolution and maintenance are under discussions as a part of MFI-3 (2nd Edition of MFI-3) • A metamodel for the process registration (process ontology) is also discussed in the SC32WG2. OWL-S or PSL(ISO) are being investigated.
Ontology Evolution(Candidate of 2ndED 19763 Part-3) Keqing He and Yangfang He, Wuhan Univ. China
We need some measures to resolve the conflicts We need add class A, remove individual i… Possible conflict ! Domain experts Ontology engineer We need keep class B, individual i… Change Closure Consistency Closure Information system engineer Evolution Strategy Final Change Set Basic resolution provided by MFI-3 ontology
Key Problems • How to registrate ontologies? • What kind of change can be identified and described by MFI-3? • How to realign the dependent ontologies during the evolution process? • How to keep the evolution information about ontologies
Our Solution (1/2) • How to registrate ontologies? • What kind of change can be identified and described by MFI-3? • How to realign the dependent ontologies during the evolution process? • How to keep the evolution information about ontologies Kernel Model Change Model Constraint Model Change Propagation Model Evolution Information Model
Differences from DB Schema evolution “Ontology Evolution: Not same as the schema evolution” , Natalya F.Noy, Michel Klein • Ontologies are data too • Ontology themselves incorporate semantics • Class and instances can be the same • Etc.
Comment at the Wuhan meeting • WD (Working Draft ) should be prepared by the NY meeting, July 2007.
Process Registration(Candidate of a new part of 19763) Keqing He and Wang Chong, Wuhan Univ., China
“process” & “process model” • Process is defined as • a set of work items, scheduled according to constraints, which all participate in fulfilling at a common purpose. [Breton and Bezivin 2001] • transformation of input to output. [ISO 1995] • one or more activities that occurs over a period of time in which objects participate. [ISO 18629] • Process model can be regarded as the product of process modeling.
Taxonomy of Processes Domain specific processes -In house Business process (Accounting, AR/AP) -Between Enterprises (Collaboration) -Industrial specific: Healthcare, Manufacturing, • Software Process • Dynamic aspect A part of an ontology • Ontology migration process • Registration process
Type of Process Model PSL, Upper Ontology or Abstract Syntx Modeling Patters BPMN MIT HB Collaboration Notation Model Contents UN/CEFACT BCF Metamodel Methodology UML IDEF 3 EXpress CPFR, ARTS UMM
Related work • PSL (ISO 18629) • a language enabling interoperability of process information among industrial applications. • IDEF-3 • captures process details. • BPMN • defines modeling notation for modeling business process. • BPEL4WS • provides a means of specifying the interaction of cooperating services. • OWL-s • define an ontology to describe the interface a service provides to the “outside world”. • only for Web Services • ……
Process Ontology t1 t2 Ontology (t1) Ontology(t2) Process X Ontology(t2) = processX (Ontologyt(t1))
Why we need MFI-5 • Web service • one of the important resources on the semantic web. • characterized with dynamic features. • Business process • interoperation and cooperation within/across the enterprises • MFI family focuses on the static resources on the web • MFI Core provides a very generic framework for various models. • MFI4Onto aims to the structure and semantics of ontology • A new part is needed to meet the requirements of dynamic resources (web services, business process etc.) on the semantic web • process model registration • process model integration with semantics • construction of customized services/process model
Scope of MFI-5 (1/2) • Objective • Provide a metamodel to register process models, including business process model and web service. • Focus on the relationship between process model described with different process description languages, especially the composite process consists of subprocesses expressed in different languages. • Promote semantic interoperation between various process models on the semantic web. MFI-5 … PSL IDEF-3
Scope of MFI-5 (2/2) • What to do • Structural information of process model • Which subprocesses are contained in process model • Which artifact participate in fulfilling the common purpose • Semantic constraints of process model • Semantic relation/contradiction between artifacts • Order • Mandatory sequence • Precondition and postcondition • User-defined constraints • …… • What not to do • Language specific details • Implementation level details
MFI Core & MFI-5 From MFI Core
Basic idea of MFI-5(1/2) • Base Model is proposed to register structure information of various process models • Goal: the purpose that should be archived by fulfilling the process model • Role: the actor who interact with the process • Artifact: the resources that participate in the process • Order: specifies the sequence of a composite process
Basic idea of MFI-5(2/2) • Process Control Model is defined to record three kinds of control constraints in process models • Sequence control • Specify the sequence followed by the subprocesses • Object control • Restrict the semantic relations between artifacts and avoid possible semantic inconsistency • Support semantic interoperation between process models based on ontology • User-defined control
Comments at the meeting • More research and investigation should be needed. • Is it premature to make it ISO standard? • Collaborative work with other group should be initiated.
Level of Interoperation David Carney, Patricia Oberndorf Software Engineering Institute Carnegie Mellon University Pittsburgh, PA, USA 15213 {djc, po}@sei.cmu.edu