ISO/IEC/JTC1 SC32/WG2 Jeju Meeting

2009/06/22-27

Updated 2009/08/17, 2009/08/20, 2009/11/17

Masaharu Obayashi

(kanrikogaku Ltd.)

WG2N1349Basic Idea

on MFI-2 core Model

Meaning Triangle (1)

Real World In Computer

Assignment: Colour := ‘red’;

Colour type={‘red’,‘yellow’,‘blue’}

“Colour” ‘red’“Colour”‘blue’

Meaning Triangle (2)UML/ Program

“Colour”

In Computer

Meaning Triangle (3)

Attribute

“bodyColour of Car”

In Computer

Meaning Triangle (4)

Table

“car spec”

name bodyColour

name bodyColour

In Computer

“Colour”

Component

Model Component

ModelbyMOF

ModelClassifier

Model Component Set

“Colour”

Model Instances

Component, Component Set and Instances

Sign and Selection

Model Component Set

“Colour”

Model Instances

Model Selection

signsign

sign

sign

“Colour”

Model Domain Profile

specified by

specification ModelbyMOF

Concept and Domain Profile

classifier

“Colour”

Component and Selection

Model Selection

“Colour”

Model Domain Profile

specified by

specification ModelbyMOF

Concept and Instancesclassifier

Model Instances

conceptualized by

• ModelComponent is unit of registered elements. Actually there are various granularities and abstraction levels .

• ModelComponentSet is aggregation of ModelComponent. The instance of ModelComponentSet is derived one from power set of ModelComponent.

• ModelComponent has ModelByMOF s as a formal definition, also includs ModelClassifiers, that are exported from the ModelComponent.

• ModelClassifier is a role to identify the particular concept and its meaning is specified in the ModelComponent.

• The instance of ModelComponentSet is the classified grouping elements of ModelComponent.

• ModelInstance is a role to conceptualize the grouped ModelComponentSet by upper defined ModelConcept.

• ModelInstance is aggregation again of ModelComponentSet. It seems double packaging of ModelComponent. It intents that ModelComponentSet of ModelInstance is able to be chosen for alternative ModelComponentSet elements. For example, it can be versioning of ModelComponentSet, new one will be added the ModelInstances that has old version of ModelComponent Set.

• Above all (ModelComponent, ModelComponent Set, ModelInstances) should be registered as common use as possible.

• The other hand, ModelConcept is designated with ModelSign for human communication. (ModelConcept can exist without any ModelSign).

• ModelSign is to designate ModelConcept, it is possible to put many ModelSigns to the same ModelConcept as synonym. For example, different terms are used for the same concept if the domains are different.

• Finally, ModelSelection, it is a very important notion in the MFI core model.

• ModelInstance consists of ModelComponentSet as mentioned above. The ModelInstances is specified (conceptualized) with upper ModelConcept. However, it has no sign (term) to point it for human communication.

• ModelSelection is a role of labeling the interesting ModelInstance with registered ModelSign. And, it is able to select the ModelComponentSet in ModelInstances by the selection condition.

• In sum, ModelSelection is grouping the registered ModelComponents and labeling it with the sign, It includes the intentions such as what ModelSign should be used, which ModelInstances should be adopted, which ModelComponentSet in ModelInstances should be selected.

• In fact, a ModelComponentSet has different ModelSign via different ModelInstance. From the other side, a ModelSign can be used to stand for the different ModelComponents.

• ModelSelection, for example, is a role to specify the standard ModelComponentSet such as adopted by each region, business field, group, or company.

• ModelComponent is able to have sub ModelComponent via ModelSelection. It means that ModelComponent is not directly connected to another ModelComponent. Concrete actual use ModelComponent can be decided from selected ModelInstances, which has the same function (concept), according to the selection condition.

• In this way, managing and registering information such as framework is able to search the information from various viewpoints according to many purposes.

• In the example of RoR, the Registry type on display is handled in ModelSign internally in the MFI registry.

• Comparing selected ModelComponentSet for each business field and analyzing labeled ModelSign, we can find the proper difference of Concept and understand the “ontology” in the true sense of the term.

Informal description of MFI-core model

Overview

sign

sign

sign

sign

sign

sign

sign

sign

component

instances

domain

selectioncomponentSet

classifier

class Registry

ModelSign

name space: string[1..1]sign: string[1..1]

ModelConcept

ModelComponentSet

component type: typeCodeformat: string[1..1]

ModelInstances

conceptualization type: typeCode[1..1]

Component::ModelComponent

component type: typeCodeconformance: string[0..*]name: string[1..1]

Component::ModelClassifier

attachement type: string[0..1]attachment: URI[0..1]classifier name: string[1..1]model type: typeCode[1..1]usage type: typeCode[1..1]xmi text: string[0..1]

Target::ModelDomainProfile

conformance: string[0..*]domain name: string[1..1]

MDR-ByMOF::AdministeredItem

Component::ModelSelection

conceptualizes 0..*

conceptualized by 1

gr oupes

1 grouped by

0..*

expresses 0..*

expressedby

1

selected by

0..*

selects

1

has as construct

0..*

has as upper0..*

has as lower 0..*

designated by

0..*

designates

1

specifies 0..*

specified by 1

binding constraint

classif ies

0..*classified by

1

refers asconst ruct

0..*

Process

Process_Modeling_LanguageGoal

Input

Output

Referent

Atomic_ProcessComposite_Process

1

-realizes

1

-modelType11..*

1

-hasInput

1..*

1 -hasOutput

1..*

-referredTo

*

*

-referredTo

**

1

2..*

ModelComponent

ModelDomainProfile:“MFI-5 ProcessModel”

ModelSelection

ModelClassifier

２１４３

Atomic processComposite process

MFI-2 and MFI-5

１ ２ ３

１ ２４

５

３６７ ８ ９

５

class Registry

ModelSign

name space: string[1..1]sign: string[1..1]

ModelConcept

ModelComponentSet

component type: typeCodeformat: string[1..1]

ModelInstances

conceptualization type: typeCode[1..1]

Component::ModelComponent

component type: typeCodeconformance: string[0..*]name: string[1..1]

Component::ModelClassifier

attachement type: string[0..1]attachment: URI[0..1]classifier name: string[1..1]model type: typeCode[1..1]usage type: typeCode[1..1]xmi text: string[0..1]

Target::ModelDomainProfile

conformance: string[0..*]domain name: string[1..1]

MDR-ByMOF::AdministeredItem

Component::ModelSelection

conceptualizes 0..*

conceptualized by 1

gr oupes

1 grouped by

0..*

expresses 0..*

expressedby

1

selected by

0..*

selects

1

has as construct

0..*

has as upper0..*

has as lower 0..*

designated by

0..*

designates

1

specifies 0..*

specified by 1

binding constraint

classif ies

0..*classified by

1

refers asconst ruct

0..*

Process

Process_Modeling_LanguageGoal

Input

Output

Referent

Atomic_ProcessComposite_Process

1

-realizes

1

-modelType11..*

1

-hasInput

1..*

1 -hasOutput

1..*

-referredTo

*

*

-referredTo

**

1

2..*

ModelDomainProfile:“MFI-5 ProcessModel”

ModelSelection

ModelClassifier

２１

３

４Atomic process Composite process

５

MFI-2-4 and MFI-5

pkg MFI-Mappi...

Transformation

- name: string- transformationType: typeCode

Lev elPair Rule

- definitionType: typeCode- lowerRuleType: typeCode- name: string- ruleDefinitionURI: URI- upperRuleType: typeCode

MFI-Core::ModelDomainProfile

MFI-Core::ModelComponentSet

MDR-ByMOF::Adminstered Item

MFI-Core::ModelComponent

MFI-Core::ModelByMOF

MFI-Core::ModelClassifier

targetLower

0..1

sourceLower

1

+targetUpper1

+sourceUpper

1

+levelPairRule

1.. *

１ ２ ３

１ ２４

５

３６７ ８ ９

１２ ３

４

５

６７ ８ ９

Process Metamodel of MFI-5

Complex ProcessComplex Process Input PortInput PortSimple ProcessSimple Process

Output portOutput port

component

instances

domain profile

selectioncomonentSet

classifier

１ ２

３

１ ２４

５

３

６７ ８

９

１ ２ ３４

５６

７ ８

２１ ３４

５

Process ModelProcess Model

A Trial for Implementing ROR

17

http://modelregistry.tiu.ac.jp/

Experimental trials

RaaS

Client

Browser

SOAP

http://mr-devel.tiu.ac.jp　

http://modelregistry.tiu.ac.jp　

http://serviceregistry.tiu.ac.jp/WS/mdr

ROR

Service Registry

SOAP

WSDL

http://serviceregistry.tiu.ac.jp/WS/mfi

18

MDR Registries

MFIRegistries

(Registry Service Integration)

2009/6/18 12th Open Forum for Metadata Registry, Seoul, Korea

19

ModelRegistry site as a Registry Service

20

MDR Registries

21

MFI Registries

A Trial Implementation

for MFI-2-4 model mapping

22

http://serviceregistry.tiu.ac.jp/mfi/project/version3.5/

23

MFI-2-4 Registries

24

MFI-2-4 Registries