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 Interoperability
ISO/IEC 19763
Meta Modeling
Facility (MOF)
Defining Facility
(ISO11179 MDR)
Ｃｏｒｅ ｍｏｄｅｌ ｏｆ Meta Model Frameworks
ISO/IEC19763
Part-1： Reference Model
Part-2： Core model
Metamodel for Ontology
Metamodel for
Model Mapping
Common Identification
& Classification
Part-3： MM for Ontology
Metamodel for
Model Constructs
Mapping Rules
metadata
Mapping
Targets
Codes
Sharable
model
Value Domains
Patterns
Model Mapping
Common
Modeling Facility (UML)
Parｔ-4: MM for Model Mapping
Common Model
Constructs
MOF and ODM
(OMG)
Metamodel Framework Architecture
M3
MOF Model
inherit
Core Model
inherit
MFI
Metamodel
Metamodels
M2
describe
Domain
Models
Modeling
Facility
refer
Common Data
Element
use
M1
Object Patterns
Modeling Constructs
Values
Concept
M0
Real World
MFI structure
Registration
Procedure
<<extension>>
Ontology Evolution
Model
Mapping (Part-4)
Model constructs
Ontology
Registration
Registration (Part-3)
Core model (Par-2)
Reference Model (Part-1)
Specific metamodel for the
mapping, defined on the core
model
Specific metamodels defined on
the core model
Provides model registration
mechanism as metamodel
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
MOF Model (M3 layer)
ModelElement
Namespace
Constraint
TypedElement
Tag
Import
Feature
Generalizabl
eElement
Constant
BehavioralF
eature
Package
Association
StructuralF
eature
TypeAlias
Parameter
Classifier
Datatype
Class
Operation
Exception
Attribute
Reference
AssociationEnd
ISO/IEC 19763-2 : Core Model
(Overview)
ModelDomain
conformance
0..* +specified by
ModelSign
nameSpace
sign
+having
1
+generally expressed by
+expressing
+specified by
0..*
1
Administered Item
data_identifier : String
version : String
1..*
ModelSelection
condition
ModelClassifier
model type
+concept usage type
xmi text
1
0..1 attachment type
attachment
1
+governed by
1
ModelConcept
modelType
1..* +governing
1..*
+selected by
1
+selecting
ModelInstances
componentType
format
1
0..*
+referent
ModelComponent
EX: Registration of Model Concept
Concept
Upper Model
Model Type
Classifier
Model
Sign
Model
Concept
Model Domain
Profile
Attachment
Model
Selection
Model
Instance
XMI schema
Target of
registration
A Model
Model Specification
Document
Relationships are not in one
type
W
Super - Sub
Y
Type Instance
X
Z
Syntax Expression
Base Variant
V
How to represent relationships
Upper Model
ISO/IEC 19763-2 :
Framework for Metamodel
Framework for Interoperability:
Core Model
•Type and Instance
•Super and Sub
•Base and Variant
•Abstract Syntax and Expression
Target Model
MOF and MFI Core
MOF
M3 Layer
<<instanceOf>>
M2 Layer
<<instanceOf>>
MDR-ByMOF
<<instanceOf>>
MMF-Core
Classifier
<<use>>
<<use>>
<<reference>>
Target
<<reference>>
ObjectByMOF
<<use>>
<<use>>
<<reference>>
<<use>>
Target Models
Level Pair
Registry
<<use>>
Relationship
<<use>>
Common facility of
MDR(ISO/IEC11179)
MOF
ISO/IEC19763-3
Metamodel for ontology registration
MFI-2
MFI Core
model
MDR standards
MFI-3
Metamodel for
MDR(ISO/IEC11179)
registration
Metamodel
for Ontology
Registration
Administration Record
ODM
Metamodel for
Metamodel for DL
Metamodel for OWL
Describe
Data Elements
Terminology
Basic Classes
Basic Relationship
Any Ontology
Ontology by ODM
Key Objectives of MFI-3
Admi. Info
Upper Ontology or Existing Ontology
Concept）
Concept）
Concept）
Reference
Ontology
Concept）
Concept）
Concept）
Registry
Admi. Info
Local Ontology
Concept）
Concept）
Concept）
Concept） Concept） Concept） Concept）
ODM（Ontology Descriptive Metamodel）
•MOF compliant Ontology Description Metamodel
•Metamodels for OWL（Web Ontology Language）,DL（Description Language）,
CL（Common Logic）, etc.
RDF
Schema
M3
Meta-meta model (MOF)
M2
Mapping
Other
UML
profile
Ontology
UML
profile
M1
Models
ODM
OWL
OWL
Expectations to MFI
Role of MFI
NRR
NRR: National Repository &
Registry
International
Industry specific
Models
InterCompany
Industry specific
Models
Company A
Company B
Model
IntraCompany
システム開発
System
Dev.
Toolsツール
アプリケーション
Application
システム
System
Web system
LCDM Project in Construction Industry
of Japan
Road
Road
Disaster
Disaster
Traffic
River
River
Traffic
Weather
Weather
Standard
LCDM Platform
Where is
my home
Data Integration
Citizen
Address?
Place?
Point?
Location
?
Industrial Expectation
System Integrator
Management
MFI Registry
ERP Vender
Planer
Requireme
nt
Real
World
Busines
s
process
ASP Venders
Programmer
Model
System Function
Project
Management
Program
DBMS Venders
Web Service
Venders
Registry Federation
Trading
Automobile
Transport
Constru
ction
物流CC/BIE
自動車CC/BIE
貿易CC/BIE
建設CC/BIE
鉄鋼CC/BIE
流通CC/BIE
Iron Steel
Hong-Kong
CC/BIE
UN/CEFACT
TBG
KIEC
CC/BIE
ECOM
CC/BIE
ISO/IEC SC32 + eAC
Ad-Hoc Project
＆
ICG/ATG
ebXML Asia Registry
Common Platform for EC (ECOM Japan)
Software
Vender
Collaboration
ASP
Interoperation
流通業界
標準
COXEC
標準
System
Collaboration
YYY
標準
Business
Information
Common Registry
As Platform
Transmission
Protocol
XXX
標準
Operation
Representation
自動車業界
標準
ECALGA
標準
UN/CEFACT標準
Korea St
Taiwan ST
China ST
MFI-New Parts under the
Study
http://www.tiu.ac.jp/org/forum01/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
We need
some
measures
to resolve
the
conflicts
We need add
class A, remove
individual i…
Possible
conflict !
Domain
experts
We need keep
class B,
individual i…
Ontology
engineer
Change Closure
Consistency Closure
Evolution Strategy
Information
system engineer
Final Change Set
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? Kernel Model
• What kind of change can be identified and
described by MFI-3?
Change Model
• How to realign the dependent ontologies
during the evolution process? Constraint Model
Change Propagation Model
• How to keep the evolution information
Evolution Information Model
about ontologies
Our solution (2/2)
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
MIT
HB
BPMN
Collaboration
Notation
Model Contents
UN/CEFACT
BCF
Metamodel
Methodology
UML
CPFR, ARTS
UMM
IDEF 3
EXpress
Comparative Analysis
Upper
Ontology
MIT
HB
PSL OWL SPE
-S
M
X
X
Pattern
X
X
Metamodel
X
OWL
Profile
X
Method
X
Collaboration
of Process
X
X
Registration
X
CPF
R
X
X
X
X
X
X
X
X
X
X
X
Contents
IDEF HL7
3+5
X
X
Notation
BPMN UM
M
X
X
X
X
X
X
X
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
t1
Ontology (t1)
t2
Process X
Ontology(t2)
Ontology(t2) = processX (Ontologyt(t1))
Why we need MFI-5
•
Web service
–
–
•
Business process
–
•
interoperation and cooperation within/across the enterprises
MFI family focuses on the static resources on the web
–
–
•
one of the important resources on the semantic web.
characterized with dynamic features.
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
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.
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
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
Oberndorf
Software Engineering
Institute
Carnegie Mellon
University
Pittsburgh, PA, USA
15213
{djc, po}@sei.cmu.edu
Another View of the Interoperation
Service base Interoperation
Semantic base Interoperation
SOAP, UDDI, BPMN,
RDF, OWL, SPARQl,
Model base Interoperation
UML, MOF, XML, XQUERY
Object base Interoperation
SQL, MDR, IRDS
Data 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”
To be modeled
UML
Common sense ?
Software
UOD
Multi-meaning
Limitation of modeling
モデラー
Modeling view
モデラー
モデラー
Integration of Models Metadata and
Ontologies,
Metamodel
Ontology
Terminology
Model
Information
Systems
+
Web system
Reality
Metadata
Information
Instance
Integration of Modeling and Ontology
Ontology
Model
“Employee”
Employee
Concept） “person”
Concept）
Concept）
Concept）
Concept）
Concept）
Terminology
Term Def.
Term Def.
OMG OUP
• OUP: Ontology UML Profile
– Ontology development by UML models
OWL based
Ontology
UML Models
OUP
Interoperable Models
Metamodels
Common
Modeling Views
Common Patterns
Model
Common
Modeling
Language
(UML)
Modeling Constructs
Common
Metadata
Common
Ontology
Common
Classification
Common
Profiles
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
Consumer
Lifecycle
Inspection &
Certification
Products
Business
Model &
Specification
Business
Business
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)
•ECCMA(TC184)
•TC64(Banking)
•TC215（Health Care）
Domain specific
terminology,
classification &
Ontology
•ISO/IEC 15944-4 （Openedi, JTC1 /SC32WG1）
•ISO15000 （ebXML-CC,
ISO/TC154）
•ISO/IEC20744
（ Common Logic,
JTC1/SC32WG1 ）
•TC127 (Earth Moving
Machine)
•JTC1 SC36
(Learning Metadata)
•TC37
(Terminology)
•TC46
（Dublin Core）
Domain Free
terminology,
classification &
Ontology
OWL/RDF (W3C)
Descriptive method
Registration
JTC1/SC34, Topic
Map
•ISO/IEC19763 (MMF :JTC1 SC32WG2）
•ISO/IEC 15944 （ Open-edi, JTC1 SC32WG1）
•REACH (EU, Chemical Industry & all related)
Another Issue for Metadata;
Cultivating
XMDR + MMF
Domain Ontology
Semantic
elements
Extraction
Defining
Ontology
Ontology
Metamodel
メタデータ
メタデータ
Metadata
Registry
Existing
Registry
Terminology
ISO TC37
Metadata Standardization
Activities
UBL
HL7
OASIS Reg/Rep
ISO TC127
UN/CEFACT ebXML RIM
Earth Moving
machine
XML Registry
W3C
UDDI
XML,RDF,
OWL
Health
Informatics
Metadata
Standardization
UDDI
OMG
MOF, CWM,
ODM
ISO/IEC
11179
MDR
Metamodel
Framework
Geographical data
ISO TC 204
SQL
Catalog
E-Commerce
metadata
Library
metadata
ISO TC 46
Dublin Core
ISO TC211
Intelligent Transportation
Systems
Terminology
ISO TC 37
ISO TC 215
ISO/IEC JTC1 SC32
Topic map
ISO/IEC JTC1 SC34
Ｌｅａｒｎｉｇ Ｍｅｔａｄａｔａ
ISO/IEC JTC1 SC36
TC154
ebXML
Type of Metadata
Standards
Metadata Value
•ebXML RIM
•ISO/IEC19763(MMF)
Metadata
Instances
Registry
Representation
Administrative
Attributes,
Representation
Language
Storing Structure
•ISO/IEC10728(IRDS）
•ISO/IEC11179（MDR)
•ebXML Repository Service
•ebXML Core Component,
•Dublin Core,
•RSS
•Digital Library
•Image Processing
•Geographical Map
•Broad Casting Program
•Health Care
•elearning
•etc
XMDR
•MOF(ISO19502)、
•RDF、
•OWL、
•Topic Map
Subject Areas of Standardization
Describing
RDF,
OWL
Concept
Registration
Service Interface
IRDS,
ebXML RS
IRDS,
XQuery
Query
Meta
Information
MOF, 11179,
ebXML RIM
Interchange
Contents
Attributes
Registration ebXML CC,
IRDS,
Dublin
Core
Aspects
11179,
ebXML RIM
MMF
Common elements
Values
Metamodel
ISO Codes
Format
CDIF,
XMI,
PDES,
History of Metadata
2010 ~
Metamodel for Semantic
Interoperation
2000~
Registry
Metadata for Semantics Sharing
1990~
Metadata for Information Sharing
Repository
1980~
Metadata for Software Developments
1980~
Metadata for DBMS
DD/DS
1970~
Metadata for file items
Data Dictionary
Thank you
謝々