Final Study Report on ROR

Final Study Report on ROR

May 2010SC32WG2 Kunming, China

Hajime Horiuchi

SC32WG2-N1423

Background• The study period project was initiated at the SC32 Sydney

Meeting (May 2008) and extended one year at the SC32 Jeju Meeting (Jun 2009).

• The project was being in charge of the investigation of many possibilities of “Registry Interoperability” In term of ROR (Registry of Registries).

• The final conclusion was made as a standard by which any heterogeneous registries could be described as simple profiles.

• The standard for the registry profile could be a part of the MFI-6 (Registration procedure).

Objectives of the study

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

•Originally, ISO/IEC 19763 (MFI: Metamodel Framework for Interoperability) in SC32 was 　 addressing the ROR concept.

Cases investigated

• Case-1: Registry Integration Service• Case-2: Hierarchical Registry Connection• Case-3: Registry Interface Virtualization• Case-4: Registry Profile

Case-1: ROR as a Registry Service IntegratorUser

Catalogue Information

Service InterfaceSpecification

Metadata usedby Service

RaaS

Registry Service

ServicePlatform (J-SaaS)

ServicePlatform (SFDC)

S1S2

S4S3

Reference

Registry Service

Service enjoyService lookup

★:Targets to be standardized

★★★

★

★

ServiceIntegrator ★

Sn: Service

Registry ServiceFederation

Service Profile Specification in the Registry

Interface Specification between Service Integrator and Platform

Interface Specification between Service Registry and Service Integrator

2010/05/17 13th Open Forum for Metadata Registry, Kunming, China

CloudROR

Experimental trials on RaaS

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

MDR Registries

MFIRegistries

(Registry Service Integration)


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

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

Case-2 : Service Hierarchy

SaaS vender

SaaS vender

SaaS vender

Service Integrator

Service Integrator

Tier-1

Service User

Tier-2

Tier-3 Service User

RaaSVender

Service Registry

RegistryService Integration

Registry Service

Registry as a Service

ebXML RR

Case-3: Registry Service Virtualization

PLIB

XML base Registry

MFI Registry

MDR Registry

Unique independent Interface

RegistryIntegration Service

StandardInterface

Web SErvice


Might invite Confusions

Registry Service = Service Registry

?

Case-4: Registry Profile• Only collection of Registry Profiles• Everybody can collect and store a set of profiles• Change will be informed by Notification(RSS)

10

MFI Registry

Registry Profile

Registry Profile

Registry Profile

Registry Profile

MDR Registry

ebXML Registry

ROR

ROR

11

Metamodel for Registry ProfileInformation of RA and owner of

this registry system.

Information of Registry system.

Information of access interfaces to registry system.

㩷class Service Profile

Organization. Details

+ Name: Text+ Identification: Identifier+ Description: Text

Contact. Details

+ Identification: Identifier+ Department Name: Text+ Description: Text

Address. Details

+ Identification: Identifier+ Postcode: Code+ Line One: Text+ Line Two: Text[0..1]+ Line Three: Text[0..1]

Communication. Details

+ URI: Identifier[0..1]+ Complete Number: Text[0..1]+ Use: Code[0..1]

Picture. Details

+ Digital Image: Binary Object+ Identification: Identifier+ Subject: Text+ Type: Text

Composit Service. Details

+ Identification: Identifier+ Name: Text+ Description: Text[0..1]+ Version: Identifier[0..1]+ Public Flag: Indicator[0..1]+ Publication: Date Time[0..1]+ Level: Numeric[0..1]+ Knowlege: Indicator

Classification. Details

+ System: Identifier[0..1]+ Class: Code[0..1]+ Class Name: Text[0..*]+ Description: Text[0..*]

Document. Details

+ Identification: Identifier+ Name: Text+ Description: Text

Binary File. Details

+ Identification: Identifire[0..1]+ Title: Text[0..*]+ Version: Identifire[0..*]+ File Name: Text[0..*]+ MIME: Code[0..*]+ Includes: Binary Object[0..*]+ Description: Text[0..*]

Interface. Details

+ Identification: Identifier+ Name: Text+ Description: Text+ EndPoint: Identifier+ Version: Identifier+ Publication Limits: Indicator

Period. Details

+ Start: Date Time[0..1]+ End: Date Time[0..1]

Service Collaboration. Details

+ Identification: Ideitifier+ Connecting From: Identifier+ Connecting To: Identifier

Software Service. Details

+ Identificetion: Identifier[0..*]+ Name: Text[0..*]+ Description: Text+ Version: Identifier+ Platform Name: Text[0..*]

Sales Information. Details

+ Identification: Identifier+ Payment: Indicator+ Price Description: Text[0..1]

+Attached

+Logo

+Postal

+Telephone

+URI

+Primary

+Category

+Logo

+Primary

+Application

+Attached

+Attached

+Accesse　Availability+Conststing

+Application

Application

+Conststing

+Conststing

12

Metamodel for Registry Profile

Contact Attribute DataType MultiplicityIdentification Identifier 1..1Department　Name Text 1..1Description Text 1..1

Reference Class MultiplicityPostal Address 0..1URI Communication 0..1Telephone Communication 0..1

Address Attribute DataType MultiplicityIdentification Identifier 1..1Postcode Code 1..1Line　One Text 1..1Line　Two Text 0..1Line　Three Text 0..1

Communiceation Attribute DataType MultiplicityURI Identifier 0..1Complete　Number Text 0..1Use Code 0..1

Picture Attribute DataType MultiplicityDigital　Image Binary　Object 1..1Identification Identifier 1..1Subject Text 1..1Type Text 1..1

Composite Service Attribute DataType MultiplicityIdentification Identifier 1..1Name Text 1..1Description Text 0..1Version Identifire 0..1Public　Flag Indicator 0..1Publication Date　Time 0..1Level Numeric 0..1Knowledge Indicator 1..1

Reference Class MultiplicityLogo Picture 0..1Primary Contact 0..1Category Classification 1..*Application Document 0..1Consisting Software　Service 1..*Connecting Software　Service 0..1

Sales　Information 0..1

Classification Attribute DataType MultiplicitySystem Identifier 0..1Class Code 0..1Class　Name Text 0..*Description Text 0..*

Document Attribute DataType MultiplicityIdentification Identifier 1..1Name Text 1..1Description Text 1..1

Reference Class MultiplicityAttached Binary　File 0..*

Sales Information Attribute DataType MultiplicityIdentification Identifier 1..1Payment Indicator 1..1Price　Description Text 0..1

Interface Attribute DataType MultiplicityIdentification Identifier 1..1Name Text 1..1Description Text 1..1EndPoint Identifier 1..1Version Identifier 1..1Publication　Limits Indicator 1..1

Reference Class MultiplicityAttached Binary　File 0..*

Software Service Attribute DataType MultiplicityIdentification Identifier 0..*Name Text 0..*Description Text 1..1Version Identifier 1..1Platform　Name Text 0..*Composite　Service　Identification Identifier 0..*

Reference Class MultiplicityApplication Interface 0..*

Service Collaboration Attribute DataType MultiplicityIdentification Identifier 1..1Connecting　From Identifier 1..1Connecting　To Identifire 1..1

Binary File Attribute DataType MultiplicityIdentification Identifier 0..1Title Text 0..*Version Identifire 0..*File　Name Text 0..*MIME Code 0..*Includes Binary　Object 0..*Description Text 0..*

Reference Class MultiplicityAttached Binary　File 0..*Access　Availability Period 0..*Consisting Service　Collaboration 1..1

Period Attribute DataType MultiplicityStart Date　Time 0..1End Date　Time 0..1

Organization Attribute DataType MultiplicityName Text 1..1Identification Identifier 1..1Description Text 1..1

Reference Class MultiplicityPrimary Contact 0..1Logo Picture 0..1

Composite　Service 1..*

Data Type: Core Component Data Type.

Registry Profile

13

Any Provider

Registry Profile

Registry Profile

Registry Profile

Unique IDType DEN Description Biz. Context ・・・・UN01000026 ABIE Basic_　Work　Item.　Details A　basic　item　of　work.

UN01000027 BBIE Basic_　Work　Item.Identification.　Identifier

The　unique　identifier　for　thisbasic　work　item.

UN01000028 BBIEBasic_　Work　Item.Reference_　Identification.Identifier

The　unique　identifier　ofanother　work　item　referencedby　this　basic　work　item.

UN01000029 BBIE Basic_　Work　Item.　Primary_Classification.　Code

A　code　specifying　theprimary　classification　for　thisbasic　work　item.

UN01000030 BBIEBasic_　Work　Item.Alternative_　Classification.Code

A　code　specifying　analternative　classification　forthis　basic　work　item.

M2

M1

UN/CFACT CCL Registry

Registry Profile

M2

PLIB Registry

英数表記日本語表記英数表記日本語表記英数表記日本語表記最小値最大値J N000000001 BDヘッダ C00001 ＢＤデータ作成日時 18041 ＢＤデータ作成日 X 8 1 1J N000000002 BDヘッダ C00001 ＢＤデータ作成日時 18042 ＢＤデータ作成時刻 X 6 1 1J N000000003 BDヘッダ C00002 送信者 18014 送信者コード X 20 1 1J N000000004 BDヘッダ C00002 送信者 18015 送信者コード管理組織 X 10 1 1J N000000005 BDヘッダ C00003 受信者 18018 受信者コード X 20 1 1J N000000006 BDヘッダ C00003 受信者 18019 受信者コード管理組織 X 10 1 1

J N000000007 BDヘッダ C00004 ビジネスドキュメントの識別 18035 ビジネスドキュメント

標準 X 5 1 1


のバージョン X 14 1 1


ＩＤ X 7 1 1

J N000000010 BDヘッダ C00005 ビジネスサービス条件 18002 コンプレックスビジネス

DコラボレイションＩ X 8 1 1

J N000000011 BDヘッダ C00005 ビジネスサービス条件 18003 ビジネスコラボレイショ

DンＩ X 7 1 1

基本項目名項目識別子データ型桁数繰返し数文書の分類名集約項目名

M1

XXX Registry

ROR

Registry Profile

Registry Profile

Collection of profile

Service Registry(UDDI)

Difference between ROR and UDDI

Find Service

Establish collaboration

Use Service

(Interchange )

Service Provider

Service Provider

Service Provider

Service Provider

Data/Model/Semantic

Registry

Service Provider

Service Provider

ROR

AutomobileElectronics Parts

1 234

Data/Model

/Semantic Registry

Final Decision• Let the Registry Profile be a part of MFI-6

(ISO/IEC19763-6: Registration procedure)

ROR StudyProject

Registry ProfileMetamodel

Registration ProcessRegistration

ProcessRegistration Process

Core Registration package

MFI-6

MDR/MFIHarmonization

Project

16

Relationship among MFI & MDR Packages

MDR/MFI Registration Core

Package

RegisteredItem Instances

MFI-6Registration

Process

•Model • Model Constructs•Service• Service Constructs•RGPS• RGPS Constructs

Registration Record

MDR-6Registration

Process

MFI -2 Metamodel

(Model )

MFI -3Metamodel(Ontology)

MFI -5Metamodel

(Process Model)

MFI-7 Metamodel

(Service )

MFI-8 Metamodel

(Service )

Registration Process

Specify

Specify

MDR/MFI Registration Common Core Package

17

• 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 profile

From ISO/IEC 11179 ED3

ISO/IEC 11179-3 Ed3

use use use

MFI-6 package (Registration)

18


Registration


<<Use>><<Use>>



Basic

MDR-6(ISO/IEC11179-6)

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

Out of scope of this document


Registration




Basic

How MFI metamodels to be used in the Registration

19

MFI Registration

Processes

MFI-6 (ISO/IEC19763-6)

Registration of Model Proc.

Registration of Ontology

Registration of Service

Lifecycle Process (Service)

Registry Profile

MFI Registry

Service

MFI MetamodelMFI

Metamodels

Specify

•RA,•Registrar,•Stewards,•Submitters

register

Registry Common process

Registration of Role & Goal

Documents

Final Study Report on ROR