73
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 [email protected] 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,

  • View
    214

  • Download
    0

Embed Size (px)

Citation preview

Database requirements to support MFI:

Next Stage of The Metamodel Framework Standard

for Interoperability:(ISO/EC19763)

Hajime HORIUCHI ISO/IEC JTC1 SC32WG2,

Tokyo International [email protected]

Study Period Meeting,

Clearwater, FL, Jan. 05, 2007. JTC1 SC32N1635

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

Common Modeling Facility (UML)

metadata

Codes

Common   Model Constructs

Mapping Rules

Patterns

Mapping Targets

Common Identification & Classification

Sharable model

Value Domains

Metamodel for Model Constructs

Metamodel for Model Mapping

Model Mapping

Core model of  Meta Model Frameworks

Metamodel for Ontology

Meta Modeling Facility (MOF)

Defining Facility (ISO11179 MDR)

Metamodel Framework for InteroperabilityISO/IEC 19763

ISO/IEC19763

Part-1 :  Reference Model

Part-2 :  Core model

Part-3 :  MM for Ontology

Par t -4:   MM   for Model Mapping

  

     MOF and ODM

(OMG)

Concept

Modeling Constructs

Core Model

Modeling Facility

M3

M2

M1

M0 

MOF Model

Values

Common Data Element

Object Patterns

Metamodel

Domain Models

Real World

inherit

inherit

refer

use

Metamodels

describe

Metamodel Framework Architecture

MFI

MFI structure

Core model (Par-2)

Ontology Registration (Part-3)

Model constructsRegistration

Model Mapping (Part-4)

Registration Procedure

Provides model registration mechanism as metamodel

Specific metamodels defined on the core model

Specific metamodel for the mapping, defined on the core model

<<extension>>Ontology Evolution

Reference Model (Part-1) Defines over all concept of MFI

Latest Status of MFI StandardsISO/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 model2ndFCD, FDIS expected by July 2007

• Part-4: Metamodel for model mapping2nCD, FCD expected by July 2007

MOF Model (M3 layer)

Package

Feature

Behavi oral Feature

St ructural Feature

Constant

Parameter

TypeAl i as

At t r i buteAssoci at i on Cl assDatatype

Cl assi f i er

TypedEl ement

Except i onOperat i on

Associ at i onEnd

Ref erence

I mport

TagConst rai ntNamespace

General i zableEl ement

Model El ement

ISO/IEC 19763-2 : Core Model (Overview)

Administered Itemdata_identifier : Stringversion : String

ModelComponent

ModelClassifiermodel typeusage typexmi textattachment typeattachment

ModelDomainconformance

ModelInstancescomponentTypeformat

0..*

1 +referent

0..*

1

ModelSelectioncondition

11..*

+selecting

1

+selected by

1..*

ModelConceptmodelType

0..11

+concept

0..11

0..*

1

+specified by0..*

1

1

1..*

+governed by1

+governing1..*

ModelSignnameSpacesign

1

1..*

+generally expressed by1

+expressing1..*

10..*

+specified by

1

+having

0..*

EX: Registration of Model Concept

Model Concept

Model Sign

Model Selection

Model Instance

A Model

Model Domain Profile Classifier

Upper ModelModel Type

Attachment

XMI schema

Target of registration

Model Specification Document

Concept

Relationships are not in one type

X

YZW

VBase -Variant

Type - Instance Syntax -

ExpressionSuper - Sub

How to represent relationships

Upper Model

Target Model

•Type and Instance

•Super and Sub

•Base and Variant

•Abstract Syntax and Expression

ISO/IEC 19763-2 : Framework for Metamodel Framework for Interoperability: Core Model

MOF and MFI Core

MOF

MDR- ByMOF

MMF- Core

Classifier

RelationshipRegistry

Target

Level Pair

ObjectByMOF

<<instanceOf>>

<<instanceOf>>

<<instanceOf>>

<<reference>>

<<reference>>

<<reference>>

<<use>>

<<use>>

<<use>> <<use>>

<<use>>

<<use>> <<use>>

M3 Layer

M2 Layer

Target Models

Metamodel for Ontology Registration

Metamodel for MDR(ISO/IEC11179)

ODM

MFI Core model

Any Ontology

Common facility of MDR(ISO/IEC11179)

Data Elements

Terminology

Basic Classes

Basic Relationship

Metamodel for Metamodel for DL

Metamodel for OWL

MOF

MFI-2

MFI-3

MDR standards

Describeregistration

   Ontology   by ODM

Administration Record

ISO/IEC19763-3

Metamodel for ontology registration

Key Objectives of MFI-3

Concept )

Concept ) Concept )

Concept )Concept ) Concept )

Upper Ontology or Existing Ontology

Reference Ontology

Concept )

Concept ) Concept )

Concept )Concept ) Concept )

Local Ontology

Concept )

Registry

Admi. Info

Admi. Info

ODM ( Ontology Descriptive Metamodel )•MOF compliant Ontology Description Metamodel

•Metamodels for OWL ( Web   Ontology Language ) ,DL ( Description Language ) ,

CL ( Common Logic ) , etc.

Meta-meta model (MOF)

ODMOntology

UML profile

OtherUML profile

OWL

RDF Schema

Models

M3

M2

M1

Mapping

OWL

Expectations to MFI

Role of MFI

Intra-Company

Inter-Company

International

Model

システム開発ツール

System Dev. Tools

アプリケーションシステム

Application System

Web system

Industry specificModels

NRR

Company A Company B

NRR:   National Repository   & Registry

Industry specificModels

LCDM Platform

Road

LCDM Project in Construction Industryof Japan

Disaster River

WeatherTraffic

Citizen

Where is my home

Road

Disaster River

WeatherTraffic

Standard

Data IntegrationAddress?

Place?Point?

Location?

DBMS Venders

Requirement

ProgramSystem Function

Business

process

Model

Real World

ASP Venders

Web Service Venders

ERP Vender

System IntegratorManagement

Planer

Programmer

Project Management

Industrial Expectation

MFI Registry

Registry Federation

Hong-KongCC/BIE

KIECCC/BIE

鉄鋼 CC/BIE貿易 CC/BIE

自動車 CC/BIE

ECOMCC/BIE

流通 CC/BIE建設 CC/BIE

物流 CC/BIE

ISO/IEC SC32 + eACAd-Hoc Project

ebXML Asia Registry

UN/CEFACT

TBG

ICG/ATG

Iron Steel

TradingAutomobile Transport

Construction

Common Platform for EC (ECOM Japan)

System Collaboration

Business Information Representation

Operation

Transmission Protocol

Common RegistryAs Platform

Collaboration ASPSoftwareVender

Interoperation

COXEC標準

ECALGA標準

自動車業界標準

流通業界標準

XXX標準

YYY標準

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

Basic resolution provided by MFI-3

Domain experts

We need add class A, remove

individual i…

Information system engineer

We need keep class B,

individual i…

Possible conflict !

Ontology engineer

We need some measures to resolve the conflicts

ontology

Change Closure

Consistency ClosureEvolution Strategy

Final Change Set

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

Our solution (2/2)

Differences from DB Schema evolution

• Ontologies are data too

• Ontology themselves incorporate semantics

• Class and instances can be the same

• Etc.

“Ontology Evolution: Not same as the schema evolution” , Natalya F.Noy, Michel Klein

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

Upper Ontology or Abstract Syntx

Modeling Patters

NotationCollaboration

Model Contents

Methodology

UMM

BPMN

UN/CEFACT BCF

PSL,

MIT HB

UML

IDEF 3

EXpress

Metamodel

CPFR, ARTS

Comparative Analysis

MIT

HB

PSL OWL-S

SPEM

BPMN UMM

IDEF3+5

HL7 CPFR

Upper Ontology

X X X X X

Pattern X X X

Metamodel X X X X

Notation OWL X X X

Profile X X X

Method X X X X

Collaboration of Process

X X X X

Contents X X X X

Registration X

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

Ontology (t1) Ontology(t2)

t1 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)

MFI-5

PSL IDEF-3

• Objective

1. Provide a metamodel to register process models, including business process model and web service.

2. Focus on the relationship between process model described with different process description languages, especially the composite process consists of subprocesses expressed in different languages.

3. Promote semantic interoperation between various process models on the semantic web.

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

Base Model

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

Process Control Model

OWL-S --Top level of the Process Ontology--

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.

Requirements for DB Technologies

What are needed in the Future

Level of Interoperation

David Carney, Patricia OberndorfSoftware Engineering InstituteCarnegie Mellon UniversityPittsburgh, PA, USA 15213{djc, po}@sei.cmu.edu

Another View of the Interoperation

Data base Interoperation

Object base Interoperation

Model base Interoperation

Semantic base Interoperation

SQL, MDR, IRDS

UML, MOF, XML, XQUERY

SOAP, UDDI, BPMN, RDF, OWL, SPARQl,

Service base Interoperation

Integration• Data and Objects

• Text and Semantics

• Information and Process

• Model and Ontology

• Reference and Local Ontologies

• SNAP and SPAN Ontology

Nature of the modeling • “Some customers want to deliver their

order by the means they specify”

Software

UODTo be modeled

UML

Common sense ?

Multi-meaning

Limitation of modeling

モデラー

モデラー

モデラー

Modeling view

Integration of Models Metadata and Ontologies,

Metadata

OntologyMetamodel

ModelInformation

Systems+

Web system

Reality

Terminology

Information Instance

Concept )

Concept ) Concept )

Concept )Concept ) Concept )

Term Def.

Term Def.

Ontology

Employee

Model

Integration of Modeling and Ontology

Terminology

“person”“Employee”

OMG OUP

• OUP: Ontology UML Profile– Ontology development by UML models

UML ModelsOWL based

Ontology

OUP

Model

Metamodels

Common Metadata

Common Modeling Language

(UML)

Common Classification

Common Ontology

Common Modeling Views

Common Patterns

Common Profiles

Modeling Constructs

Interoperable Models

Integration of Data and Objects

• OR Mapping

• Data Oriented Object Modeling

• ORL

http://www.agiledata.org/stylesheet/global.css

Other issues

Reliable Common Registries

• Registration of ISO and major standards

The ISO Common Database Procedure

(Ontology for ISO standards?)

• Long Term transaction (5~30 years)

• Tracking registry change

• Reliable non profit organization for registry operation

Traceability & Long Term Transaction

Business

Products

Consumer

LifecycleInspection & Certification

Business

BusinessModel & Specification

OMG related Issues for SC32

• Current ISO version (ISO/IEC19502) of MOF is MOF1.4

• OMG had standardized MOF2.0, UML2.0• MOF2.0 (QVT) should be invited to ISO • Some other MOF based metamodel should be

invited.– ODM– SPEM– CWM– Etc.

Terminology(TC37) related Issues

• Semantics and metadata are rely upon the terminology definition

• SC32WG2 has shared issues with TC37

A trial on stock taking standardization Activities for Semantic Interoperations

(FYI)

Domain specific terminology, classification & Ontology

Descriptive method

Domain Free terminology, classification & Ontology

•ISO/IEC 15944-4 ( Open-edi, JTC1 /SC32WG1 ) 

•ISO15000  ( ebXML-CC, ISO/TC154 )

•ISO/IEC20744  ( Common Logic, JTC1/SC32WG1 )

Registration

•ISO/IEC19763 (MMF :JTC1 SC32WG2 ) 

•ISO/IEC 15944 ( Open-edi, JTC1 SC32WG1 )

•REACH (EU, Chemical Industry & all related)  

•ECCMA(TC184)

•TC64(Banking)

•TC215 ( Health Care )•TC127 (Earth Moving Machine)

•JTC1 SC36 (Learning Metadata)

•TC37 (Terminology)

•TC46 ( Dublin Core )

JTC1/SC34, Topic Map

OWL/RDF (W3C)

Another Issue for Metadata;Cultivating

メタデータメタデータ

Metadata Registry

Existing Registry

Domain Ontology

Defining Ontology

OntologyMetamodel

Terminology

ISO TC37

Extraction

XMDR + MMF

Semantic elements

Metadata Standardization Activities

ISO/IEC JTC1 SC32  

UN/CEFACT

OMG

ISO TC 37    ISO TC 204

Metadata Standardization

OASIS Reg/Rep

Intelligent Transportation Systems

ISO/IEC11179MDR

Metamodel Framework

W3C

XML Registry

UDDI

TC154

E-Commerce  metadata

XML,RDF,OWL

Terminology

UDDI

SQLCatalog

   ISO TC 215

HealthInformatics

ISO TC127

Earth Moving machine

ebXML  RIM

UBL

Dublin CoreISO TC 46

Library metadata

ISO TC211

Geographical data

HL7

ISO/IEC JTC1 SC36  

Learnig Metadata 

ISO/IEC JTC1 SC34  

Topic map

ebXML

MOF, CWM,  ODM

Metadata Instances

Administrative Attributes,

Storing Structure

•ebXML   RIM•ISO/IEC19763(MMF)

Representation Language

Representation

•ebXML Core Component,•Dublin Core,•RSS•Digital Library•Image Processing•Geographical Map•Broad Casting Program•Health Care•elearning•etc

•MOF(ISO19502)、•RDF 、•OWL 、•Topic Map

•ISO/IEC10728(IRDS )•ISO/IEC11179 ( MDR)•ebXML Repository Service

Metadata Value

Registry

Type of Metadata Standards

XMDR

Subject Areas of Standardization

Meta Information

 Interchange

Attributes Format

Metamodel

Contents

   Common elements

Service Interface

Registration

Values

Registration Aspects CDIF,

XMI, PDES,

IRDS, 11179, ebXML RIM

MOF,  11179, ebXML RIM

IRDS, ebXML RS

ebXML CC, Dublin Core

ISO Codes

MMF

Concept

DescribingRDF, OWL Query

IRDS, XQuery

History of Metadata

Metadata for file items

Metadata for DBMS

Metadata for Software Developments

Metadata for Semantics Sharing

1970~

1980~

1980~

1990~

2000~

Metadata for Information Sharing

DD/DS

Repository

Registry

Data Dictionary

Metamodel for Semantic Interoperation

2010 ~

Thank you謝々