Final Report onHarmonization of MFI & MDR

and Disposition

Hajime Horiuchihori@tiu.ac.jp

hhori@dance.plala.or,jp

May18, 2011

SC32WG2 N1533-R1SC32WG2 Meeting, May 2011, Kona, Hawaii

Company 　 Logo

Overview of the Study The study project on the harmonization of MDR &

MFI was initiated at the Jeju meeting (2009.06) and it was extended one more year at the Kunming meeting(2010.06)

This is the final report on the study.

Some recommendations were made.

However, it is premature to develop documents as the Reference model or the Framework for both MFI & MDR

Company 　 Logo

History of MDR &MFI

1997 2000 2005 2010

MDR 1,2,3,4,5,6

MDR ed.21,2,3,4,5,6

MFI 2,4

MFI 5MFI6MFI7

MDR 3-ed.3

20944

MFI 1

MFI3-ed2

MFI8

TR

MFI project started(2003.05)

ED2

MFI3

SC14

SC21WG3

MFI 10,11JTC1 SC32 Formulated

NWI

Company 　 Logo

Current MFI Structure ISO/IEC 19763-1 : Metamodel framework for interoperation Part-1: Reference model Part-2: Core model Part-3: Metamodel for ontology registration Part-4: Metamodel for model mapping Part-5: Metamodel for process model registration Part-6: Registration Procedure Part-7: Metamodel for service registration Part-8: Metamodel for Role & goal registration Part-9: On demand model selection (TR) Part-10: Core model and basic mapping Part-11: Advanced model mapping

Company 　 Logo

Current Status

Basic attribute Data Elements (E1)

IRDS

(SC14)(SC21WG3)

MDR-3

MDR-3 (E3)

MFI-1 MFI-2&4

MFI-3(E1)

(2003)

MFI-3 (E2)MFI-6MFI-7 MFI-8

MDR-1

(MDR-1(E3))

MFI-9 MFI-10

MFI-5

1997

(MFI-1(E2))

MDR-6(E2)

MDR-2 MDR-6MDR-4MDR-5

XXX-X : WDXXX-X : Published

XXX-X : CD

(E2)

XXX-X : Expected

MDR

MFI

Company 　 LogoMFI structure at the beginning

MFI-2

MFI-3 MFI-4

MFI-1Core model

Ontology registration

Model mapping registration

Reference model

AS of May 2003

ISO/IEC 19763 : Metamodel framework for Interoperability (MFI)

Company 　 LogoCurrent Part Relationship in MFI

Administered Item

Part-3 Part-5 Part-7

Part-1

Part-8

Part-6

Part-9(TR)Part-11

Part-10

RegistrationProcedure

Reference Model

Ontology Business Process Web service

Role & GoalAdvance Mapping

Core & Basic Mapping

ODMS

Company 　 Logo

Concept

Modeling Constructs

Modeling Facility

M3Level

M2 level

M1 level

M0level

Core ModelMFI

Values

Common Data Element

Object Patterns

Metamodel

Model

Real World

inherit

refer

Govern

use

Metamodel

MOF Metameta model

Original Idea of MFI

Company 　 Logo

Original Motivation of ISO/IEC19763(MFI) standards

9

Heterogeneous Registries Registry Interoperation

Registry Registry Registry

ROR

ManufacturingLogisticRetails

Registry

ROR: Registry of Registry

SC32 Seoul 0205064PDES/STEP

RegistryManufacturing

ebXML Registry

UDDI

Component Registry

GCI Registry

EAN Registry

CPFR Registry

RosettaNetRegistry

Business Negotiation

Vender Catalog

Shipper Catalog

Business Category

Shipping

Customer Support

Consumer Profile

CALS

Production Planning & Procurement

System Development

11179 Registry

Company 　 Logo

So Many different Viewsto Metamodel Framework !!

Company 　 Logo

Buyer Seller Buyer Seller

Industry Domain A Industry Domain B

Registry

Metamodel

Registry

Metamodel

Metamodel Registry MMF Core Model

MMF for Model MappingRegister

Meta Model Frameworks

Refer

describe

Mapping

Business Business

describe

Register

Expected Solution by MFI (at 2003)

Company 　 LogoModel Registration Concept (1)

ModelModel

Metamodel(UML)

CommonMetamodel

ModelModel

Metamodel(ER)

Register

• Collect well-known metamodels • Register individual models with normative administrative information• Benefit: Make model mapping make easy

MFI Registry

Model Repository

order Cust

Collection & Register

Target Model

Metamodel(UML)

orderr

Cust

Company 　 LogoModel Registration Concept, Today

ModelModel

Metamodel(UML)

CommonMetamodel

ModelModel

Metamodel(ER)

Registering

•Investigate and define common abstracted modeling contracts as Metamodel

• Register individual models with normative administrative information

MFI Registry

Model Repository

order Cust

abstraction

Target Model

Company 　 Logo

CommonMetamodel

MFI Registry

Administered_Item

Registry entry Identification

Naming

Registration Authority

Model representation Following Common Metamodel

Model Registration Concept (2)

order Cust

Target model

Order: Cust:

Company 　 Logo

Registrar, Registration Authority, Stewardship

Expanding of register targets

15

Data Element

Target Object Object Constructs

DEC, CD, VD

Model CompnentsConcept

Ontology components

Service Components

Codes

Terminology

Model

Ontology/ Concept System

Service

References

IdentificationDesignation Scheme

Classification Scheme

Administered ItemOuter Registry

Role & Goal

Company 　 Logo

Evolution of MDR & MFI (1)

16

Common Administration

Information

Metadata Registration

Model Registration

“Common Facility” for both MDR & MFI

ISO/IEC11179 Edition 2MOF (ISO/IEC19502)

ISO/IEC11179 Edition 1

Data ElementsSC14 IRDS (ISO/IEC 10728)

MOF (OMG)

ISO/IEC19763ISO/IEC11179 Edition 3

Company 　 Logo

Possible Integration

Registration Procedure,

Administer Item,

Basic Types,Naming,Identification,

Registry Summery

Models

Ontology

Services

Role & Goal

Data Elements

Concept

MDR(11179) MFI (19763)

Company 　 Logo

RecommendationRecommendations

Company 　 Logo

RECOMMENDATION　1

Define　“Common　Facility”　for　　both　MDR　&　MFI

Recommendation-1

Company 　 LogoMDR/MFI Registration Common Core Package

20

• Namespace• Registry Authority• Registrar• Administered_Item• Stewardship_Record• Submission_Record• Registration _Record

Registration

Identification Designation & Definition

MDR/MFI Registration Core Package

•Contact•Date-and Time•Individual•Language_Id•Organization•Phone_Number•Postal_address•Registration A_ID

Basic

Registry summery

From ISO/IEC 11179 ED3

ISO/IEC 11179-3 Ed3

use use use

Company 　 Logo

Recommendation 2

MFI-6　(Registry　summery　,　WG2N1506)　　should　be　integrated　in　MDR-6　(Registration　Procedure,).

MFI-6　should　　be　with　drawn　(Japan　NB　position).

Title　of　ISO/IEC11179-6　could　be　　　　　　　　　　“Registration　”.

Company 　 Logo

MDR/MFI-6 package (Registration)

22

• Namespace• Registry Authority•　 Registrar• Administered_Item• Stewardship_Record• Submission_Record• Registration _Record

Registration

Identification Designation & Definition

<<Use>><<Use>>

MDR/MFI Registration Core Package

•Contact•Date-and Time•Individual•Language_Id•Organization•Phone_Number•Postal_address•Registration A_ID

Basic

MFI Registration Process

Registry Profile

Lifecycle Process (Service)

Registration of Model (Service)

Registration of Ontology

(S)

Registration of Service

(S)

Registration of Goal & Role (S)

Registry Common Process

MDR/MFI -6

Company 　 Logo

ROR Collection　of　RS(Registry　Summery) RS　is　a　simple　artifact　that　describes　own　registry　to　enable　registry　discovery　

ModelRegistry

RS

OntologyRegistry

RS

ModelRegistry

RS

RSRSRS

ROR

Company 　 LogoMetamodel for Registry Summery㩷

class　Registry　summary

picture+ pictureId: string+ titleName: string+ mimetype: string+ digitalImage: string+ revision: long

category+ categoryId: string+ categoryName: string[0..1]+ description: string[0..1]+ revision: long

interface+ interfaceId: string+ interfaceName: string+ description: string[0..1]+ interfaceUr: string[0..1]+ interface_version: string[0..1]

provider+ providerId: string+ providerName: string+ description: string+ active: boolean+ revision: long

registrySummary+ registryId: string+ registryName: string+ description: string[0..1]+ version: string[0..1]+ serviceLevel: int[0..1]+ verification: boolean[0..1]+ standard: boolean[0..1]+ results: boolean[0..1]+ active: boolean+ releaseDate: date+ knowledge: boolean[0..1]+ priceInfo: string[0..1]+ revision: long

assembly+ assemblyId: string+ assemblyName: string+ description: string[0..1]+ version: string[0..1]+ originRegistryComponent: string[0..1]+ destinationRegistryComponent: string[0..1]

document+ documentId: string+ documentName: string+ description: string[0..1]+ version: string[0..1]+ fileName: string+ binaryObject: string+ mimetype: string+ revision: long

registryComponent+ ergistryComponentId: string+ registryComponentName: string+ description: string[0..1]+ version: string[0..1]+ platformName: string

referenceRegistryComponent+ registryComponentId: string+ registryComponentName: string+ providerName: string+ description: string[0..1]+ version: string[0..1]

extensionDefinition+ attributeId: string+ attributeName: string+ type: int+ revision: long

extensionValue+ extensionValueId: string+ attributeName: string+ type: int+ value: string

registryOption+ optionId: string+ optionName: string+ description: string[0..1]+ fee: decimal[0..1]+ initialCost: decimal[0..1]+ initialCostMemo: string[0..1]+ purchaseCost: decimal[0..1]+ cutOffDate: int[0..1]+ salesClass: int[0..1]+ firstMonthCalculus: int[0..1]+ lastMonthCalculus: int[0..1]+ active: boolean+ revision: long

㩷

<<abstract>>contact

0..1icon

+iconId

0..*

registry

+registryIdList

0..1

contactInfo+contactInfo

0..*

registry

+categories0..*

+parentId0..*

subcategory+subCategories0..1

0..1 logo

+logoId

0..1contactInfo

+contactInfo0..*

assembly

+assembly

0..*SLA+sla

0..*promotionDocs

+promotionDocs

0..*manual+manuals

0..*verificationDoc

+verificationDocs

0..1logo +logoId

0..*

slaOption

+slaOption

0..*interface

+interfaces

0..*referenceRegistryComponent

+referenceRegistryComponent

0..*extensionDefinition

+extensionDefinitions

0..*

registryOption

+registryOptions

reference+referenceId

1..*

registryComponent

+registryComponent

0..*interface+interfaces

0..*

specificationDoc

+specificationDocs

attributeId

+attributeId

0..*

extensions

+extensions

0..*assemblyDoc

+assemblyDocs

Company 　 Logo

Where RORs were located

Find Service

Establish collaboration

Use Service

(Interchange )

ROR

Model registry

Ontology registryMetadata

registryModel registryModel

registryMetadata registryMetadata

registry

ROR

Within a organization

Within a industry

Ontology registry

Company 　 Logo

Recommendation 3 Initiate　a　project　to　develop　a　common　reference　model　or　framework　that　defines　overall　architecture　of　both　MDR　&　MFI

Expected　MDR-1　and　MFI-1　should　be　integrated

Company 　 Logo

Recomendation

Basic attribute Data Elements (E1)

IRDS

(SC14)

(SC21WG3)

MDR-3

MDR-3 (E3)

MFI-1 MFI-2&4

MFI-3(E1)

(2003)

MFI-3 (E2)MFI-6

MFI-7 MFI-8

MDR-1

MDR-1(E3)

MFI-9 MFI-10

MFI-5

1997

MFI-1(E2)

MDR-6(E2)

MDR-2 MDR-6MDR-4MDR-5

XXX-X : WDXXX-X : Published

XXX-X : CD

(E2)

To be initiated

Company 　 Logo

Recommended

MDR/MFI Registration Core Package

MFI-10

MFI-3(E2) MFI-5 MFI-7

MDR/MFI-1

MFI-8

MDR/MFI-6

MFI-9(TR)

MDR/MFI Common Facility Registry Architecture

SOAArchitecture

MDR-3(E3)

Ontology Process Service

Role & Goal

Registry Core

Company 　 Logo

Goal of Harmonization

ModelRegistry

ServiceRegistry

Role &Goal

Registry

Metadata Registry

OntologyRegistry

ProcessModel

Registry

MDR-3Ed3

MDR/MFI Registration Procedure

MFI-10

MFI-3 MFI-5 MFI-7 MFI-8

MFI-9: On Demand Selection (TR)TR

Part-1

ISO/IEC24706

ISO/IEC20944

ISO/IEC 24707

ISO/IEC 20943(TR)

MDR/MFI Reference

Model

ROR

ROR

Registries

RS RS

RS RS RS RS

Company 　 Logo

the Architecture Establish an architectural framework to be referred in the

future standardization activities in the ISO/IEC SC32. The architecture should provide a structural view of related

standards, showing an information sharing infrastructure where each standard to be located , in order to increase the high level and smooth sharing of data, information and models through the registrations in the coming new paradigm such as the Cloud computing or the Grid computing.

The exchanging of data, information and models should be supposed to be done through the Web services.

Company 　 Logo

Architecture Issues

Company 　 Logo

New MFI Structure

MFI Part1ROR

Part2 &4 Part3 Part5 Part7 Part8Part 9Part6

?MFI Part1ROR

Part2 &4 Part3 Part5 Part7 Part8Part 9Part6

?

New Architecturefor Registry Interoperation

Company 　 Logo

Registry Architecture Types

33

Domain Specialty

Diversity of Stakeholder

SOS

Process Contents

SOA/SaaS

limited Alliance

High(Narrow)

ROR

Cross IndustriesMetadata Dependent(Non Structural)

Model Dependent(Structural)

Low(Generic)

High

Target of the Standardizations

System of Systems

Registry Of Registries

Cross Homes

102 108

Company 　 Logo

Needs for Architecture

ServiceService

ServiceService

ServiceService

UDDI

MDRegistryMD

RegistryMDRegistryMD

RegistryMetadataRegistry

MFIRegistryMFI

RegistryMFI

Registry

RORROR

RORROR

UDDI

Data SemanticsModel & Information Semantics

Customized collection of registry summery

ServiceService

ServiceService

ServiceProcess

Cloud

Company 　 Logo

Final disposition at the Meeting

InformationModel

Registry

ServiceRegistry

Role &Goal

Registry

Metadata Registry

OntologyRegistry

ProcessModel

Registry

MDR-3Ed3

MFI-6 Registry SummaryMDR-6 Registration

MFI-10

MFI-3 MFI-5 MFI-7 MFI-8

MFI-9: On Demand Model Selection (TR)

MFI-11: Advanced model mapping (TR)

ISO/IEC24706

ISO/IEC20944

ISO/IEC 24707

ISO/IEC 20943(TR)

MDR -1 Framework

MFI-1Reference

Model

MFI-12

Core facility

Company 　 Logo

Actions to be needed Common facility should be used in the next

edition of each part or parts in the WD stage of both MDR & MFI.

Integrate MFI-6 (Registry summary) into MFI-6 (MFI-6 should be withdrawn)

CD registration first. MFI-1 Edition 2 project should be initiated with co-editing, such as China, Korea and Japan

Company 　 Logo

Time line Extension of the harmonization study period for

one year. WD MFI-1 ED2 should be submitted to the next

interim meeting (Authorization should be done at the next SC32 meeting )

In the future, both MDR/MFI should be merged to one series of standard, (ex. ISO/IEC 11179)

Company 　 Logo

Company 　 Logo

THANK　YOU