SC 32 WG 2 N 1130 Request for

SC 32 WG 2 N 1130 Request for Study Period on “MFI for ROR” Hajime Horiuchi Tokyo International University May 28, 2008 “Sharing and advancing knowledge and experience about standards, technologies and implementations. 1

Topics • • • Type of Registry (Difference of Architectures ) What is ROR Background of ROR project Overall structure of ROR Issues “Sharing and advancing knowledge and experience about standards, technologies and implementations. 2

Evolution of Registry Technology Semantic Registry Metadata Registry Sharing of Discover & Casting Web Sharing of Service knowledge Cross Domain Interoperation ROR Software Sharing of Data DD/DS Sharing of development Methodology “Sharing and advancing knowledge and experience about standards, technologies and implementations. 3

A Taxonomy of Architecture Types Target of the Standardizations Process High (Narrow) SOS Contents System of Systems Model Dependent (Structural) limited Alliance Domain Specialty ROR Registry Of Registries Cross Industries Low (Generic) Cross Homes 102 Metadata Dependent (Non Structural) SOA/Saa. S Diversity of Stakeholder 108 High 4 “Sharing and advancing knowledge and experience about standards, technologies and implementations.

DIFFERENCE OF REGISTRY TYPE “Sharing and advancing knowledge and experience about standards, technologies and implementations. 5

Registry to Support Engineering Registry to support Engineering High (Narrow) SOS System of Systems Model Dependent (Structural) limited Alliance Domain Specialty ROR Registry Of Registries Cross Industries Low (Generic) Cross Homes 102 Metadata Dependent (Non Structural) SOA/Saa. S Diversity of Stakeholder 108 High 6 “Sharing and advancing knowledge and experience about standards, technologies and implementations.

Registry to Support Engineering Registry Integration Product Specifications Part Library Process Models Products Models Domain Ontology “Sharing and advancing knowledge and experience about standards, technologies and implementations. 7

Registry to support Cross Industries Registry for Interoperation High (Narrow) SOS System of Systems Model Dependent (Structural) limited Alliance Domain Specialty Registry Of Registries ROR Metadata Dependent (Non Structural) Cross Industries Low (Generic) Cross Homes 102 SOA/Saa. S Diversity of Stakeholder 108 High 8 “Sharing and advancing knowledge and experience about standards, technologies and implementations.

Registry to support Cross Industries Registry Product Information Business Information Party Information Business Process Model Supply Chain Domain Ontology “Sharing and advancing knowledge and experience about standards, technologies and implementations. 9

Registry for Discovery Registry for Discovering High (Narrow) SOS System of Systems Model Dependent (Structural) limited Alliance Domain Specialty ROR Cross Industries Metadata Dependent (Non Structural) SOA/Saa. S Low (Generic) Cross Homes 102 Diversity of Stakeholder 108 High 10 “Sharing and advancing knowledge and experience about standards, technologies and implementations.

SOA/Could Computing Saas Cloud Saas “Sharing and advancing knowledge and experience about standards, technologies and implementations. 11

Registries to support SOA Ontology Object-URI Saas Access Protocol Ontology Saas Object-URI Access Protocol Saas “Sharing and advancing knowledge and experience about standards, technologies and implementations. 12

In the Future ? Web service Registry as Service Saas “Sharing and advancing knowledge and experience about standards, technologies and implementations. 13

ROR: Registry of Registries TO SUPPORT CROSS INDUSTRIES “Sharing and advancing knowledge and experience about standards, technologies and implementations. 14

What is ROR • ROR (Registry of Registries) is trial uses of the MFI on the cross industries business processes – MFI: ISO/IEC 19763 (Metamodel Framework for Interoperability) • Goal: – Reification of the interoperability among heterogeneous domain registries • A formal committee under IPSCJ(JTC 1 Japan) – SC 32 WG 2 + TC 184/SC 4 + ECOM + LCDM members – Just started at officially on this April “Sharing and advancing knowledge and experience about standards, technologies and implementations. 15

Original goals of ISO/IEC 19763 standards ROR: Registry of Registry ROR Registry Retails Heterogeneous Registries Registry Logistic Registry Manufacturing Registry Interoperation 16 “Sharing and advancing knowledge and experience about standards, technologies and implementations.

WHY WE NEED ROR ? 17 “Sharing and advancing knowledge and experience about standards, technologies and implementations.

What is the Registry, again • Registry has several meanings, all of which generally relate to its original or historical meaning as a written, official or formal record of information, or the place where such records are kept. • Office where registrations are recorded; database for storing system configuration information. (Wikipedia) 18 “Sharing and advancing knowledge and experience about standards, technologies and implementations.

Current status of the registry • Today, a lot of actual registries are enforced and working in various business domains. • They were developed mostly according to requirements in their specific domains. • Each registry has own structure, fashion and procedure. • Most of them did not pay attentions to other registries. • Even if, they could follow particular standards, most of those standards themselves might be domain specific. 19 “Sharing and advancing knowledge and experience about standards, technologies and implementations.

Different Views by industries on 　 a same product Home electronic Products ISO 13584　 standards Home Electronic Category Electronic Parts Category Metadata Item-Number Product-Number Attributes for Retailing Attributes for Manufacturing PLIB GS 1, EPCG No interoperability Item Master DB 20 “Sharing and advancing knowledge and experience about standards, technologies and implementations.

Closed Processes and Registries Manufacturing Retailing Design Merchandising Assembling Buying Inspection Delivery PLIB Item Master Selling Invoice 21 “Sharing and advancing knowledge and experience about standards, technologies and implementations.

Emerging needs for the Model Sharing Actual reification of Cross Industries Interoperation is needed Product Life Cycle Management Retail ing Manufacturing Hazardous Materials Management Product Industrial Waste Processing Logistic & Distribution Product Traceability Consumer Artery & Vein 22 “Sharing and advancing knowledge and experience about standards, technologies and implementations.

Every domain has own Registry Product Life Cycle Management Registry Retail ing Manufacturing Registry Hazardous Materials Management Product Industrial Waste Processing Logistic & Distribution Registry Product Traceability Consumer 23 Artery & Vein “Sharing and advancing knowledge and experience about standards, technologies and implementations.

Some of actual registries in Japan – JEITA（ECALGA, PLIB） – JEMA（Heavy electric parts） – JEMIMA(Electric Measurement Instruments ) – CEDI（Petro Chemical） – JAPIA/JAMA（Automobile） – JASTPRO（Shippers codes） – JEDIC（EDI standards） – JICFS/DRS（Company code, Item code in retailing ） – JACIC LCDM（Construction Engineering） – www. registry. go. jp etc. “Sharing and advancing knowledge and experience about standards, technologies and implementations. 24

EDI Related Standards Rosetta. Net Industrial St. GS 1 IETF - AS 2 W 3 C - XML De Jure ISO - EDIFACT - eb. XML　- PLIB OASIS - eb. MS -WS - R&R CIDX e. Business Asia EPCグローバル UN/CEFACT CEN JIS EDIFACT/CII ANSI X 12 WCO HL 7 25 JADM SWIFT “Sharing and advancing knowledge and experience about standards, technologies and implementations.

Product Tracing by RFID tag “Sharing and advancing knowledge and experience about standards, technologies and implementations. 26

A Draft of Framework for Information Infrastructure (ECOM, 2007) Web Service Providers Ordering Service Item Reg. Service MSDS Reg. Service Part Retrieval Service Accounting Service Portal Service UDDI ROR Business　Oriented Process Integration 27 Retail Item DB PLIB MSDS Material Oriented Process Integration Cargo Tracking Tax DB “Sharing and advancing knowledge and experience about standards, technologies and implementations.

What is MFI • Metamodel Framework for Interoperability • ISO/IEC 19763 series of standards • A set of Metamodels for; Registering Models (Not for describing model or ontology) • MFI is an Application of MOF (1. 4) 28 “Sharing and advancing knowledge and experience about standards, technologies and implementations.

ROR by MFI（ISO/IEC 19763） series of standards Metamodel for process registration Metamodel for ontology registration Core model Metamodel for model mapping Registration Procedure ROR Mapping Registry Industrial registries (Cross Domain Registry) Registry 29 “Sharing and advancing knowledge and experience about standards, technologies and implementations.

Cross Domain ROR Registration Authority OID UUID RA Model Mapping Service Domain B Domain Ontology RA Data Elements 基本情報要素 Value Domain A UID Domain Model ROR Ontology Search Service MFI Registry UID Basic Ontology Domain Ontology RA Registry Terminology Registration Procedure Industrial domain Registration 30 Quality “Sharing and advancing knowledge and experience about standards, technologies and implementations. Terminology

ISSUES FOR ROR & MFI Standards “Sharing and advancing knowledge and experience about standards, technologies and implementations. 31

Issues • • • How to Discover and Cast registries How to Make Mappin How to provide a Universal ID How to specify Data Quality Registration Procedure All of above are under discussion. “Sharing and advancing knowledge and experience about standards, technologies and implementations. 32

Use Case Home electronic Products ISO 13584　 standards Home Electronic Category Electronic Parts Category Product-Number PLIB GS 1, EPCG Mapping Item-Number Item Master DB 33 “Sharing and advancing knowledge and experience about standards, technologies and implementations.

Issues Home electronic Products ISO 13584　 standards GS 1, EPCG Home Electronic Category Electronic Parts Category Product-Number Mapping PLIB RA/RO 34 Data Quality Specification Mapping Change Control Item-Number Item Master DB Registration Procedure Global Unique ID Ontology Casting “Sharing and advancing knowledge and experience about standards, technologies and implementations.

How to Cast a registry call Level 1 ROR Search Level 2 PLIB Metamodel M 2 ITEM Master Metamodel Inquire Level 3 M 1 PLIB Model JAITA PLIB Model ITEM Master Instance JAMIMA “Sharing and advancing knowledge and experience about standards, technologies and implementations. 35

Level 1 Mapping Variation • Exactly Same • Similar to • Looks like “Sharing and advancing knowledge and experience about standards, technologies and implementations. 36

How to Map • MFI-2 (Core Model) is used for registration of metamodel • MFI-4 (Model Mapping) to be used for describe model mapping • The eb. XML Core Component to be used for type matching “Sharing and advancing knowledge and experience about standards, technologies and implementations. 37

Use case 2 • Stock take Metamodel of target registries • If they do not have any metamodel, metamodel should be developed using CWM metamodels • Assign Core component of the eb. XML to each element of the Schema “Sharing and advancing knowledge and experience about standards, technologies and implementations. 38

Metamodel Mapping eb. XML CC Metamodel PLIB Metamodel Item Master Metamodel CWM Mapping Rule Instance Mapping Process MFI: Metamodel for Mapping “Sharing and advancing knowledge and experience about standards, technologies and implementations. 39

MFI 4: Model Mapping “Sharing and advancing knowledge and experience about standards, technologies and implementations. 40

Type Matching through CC eb. XML Core Component 1 (ACC: nn) 1 * * Item Master Element PLIB Element GS 1 ID Mapping TS- TV-42 - name (ACC-nn) TV-42 -Toshiba name (ACC-nn) “Sharing and advancing knowledge and experience about standards, technologies and implementations. 41

eb. XML Core Component • Standardized Information elements for Business Information to be used in the electronic business Core Component Business Information Aggregated Core Person Component Core Component Type CCT Text Health. record 0. . * ACC Aggregated Business Information Entity ABIE ASCC Resident BCC Location Business Information Entity *. . 1 BIE Basic Core Component Patient. Person 42 “Sharing and advancing knowledge and experience about standards, technologies and implementations.

Metamodel of CC CCTS : Core Component Tech. Spec. V-3. 0 “Sharing and advancing knowledge and experience about standards, technologies and implementations. 43

CWM: Relational Data model “Sharing and advancing knowledge and experience about standards, technologies and implementations. 44

CWM: Metamodel for Record Traditional COBOL file, CSV file “Sharing and advancing knowledge and experience about standards, technologies and implementations. 45

PLIB Class (Not UML) identified_by class_BSU supplier_BSU described_by L[0: ? ] property_BSU defined_by (DER) subclasses SET[0: ? ] String definition String note String (DER) known_applicable_properties SET[0: ? ] (ABS) class defined_types S[0: ? ] (DER) known_applicable_data_types SET[0: ? ] its_superclass remark (ABS) document data_type_BSU revision source_doc_of_definition time_stamps String dates names String preferred_name short_name item_names String synonymous_name S[0: ? ] icon (ABS) graphics “Sharing and advancing knowledge and experience about standards, technologies and implementations. 46

PLIB Property (Not UML) identified_by (ABS) class property_BSU String (ABS) data_type domain described_by L[0: ? ] definition String formula note (ABS) String remark (ABS) document property_DET synonymous_symbol S[0: 2] source_doc_of_definition (ABS) graphics revision figure String mathematical_string preferred_symbol time_stamps det_classification String dates names String preferred_name String short_name synonymous_names S[0: ? ] item_names icon String (ABS) graphics “Sharing and advancing knowledge and experience about standards, technologies and implementations. 47

Mapping PLIB Class Part Record. File ITEM_Master PLIB property Record. Field Part_Number Item_Number “Sharing and advancing knowledge and experience about standards, technologies and implementations. 48

Re: GEN (General k. Nowledge Navigator) OKABE, Masao Corporate Systems Department Tokyo Electric Power Company Inc. (TEPCO) 2008. 5. 20 “Sharing and advancing knowledge and experience about standards, technologies and implementations. 49

What is GEN? • GEN is General k. Nowledge Navigator, – which is a kind of ontology editor/repository mainly for knowledge management for human, – which TEPCO already developed but may need some refinements and enhancements. • GEN is very generic like Protégé. So, it can be easily enhanced either to – an ontology repository that is managed by Ro. R or – an experimental implementation of OOR or Ro. R itself. “Sharing and advancing knowledge and experience about standards, technologies and implementations. 50

Two possible positions of GEN Ontologies other than Semantic Web ontologies OOR based on GEN = MFI Ontology registration registry based on GEN Swoogle = Ro. R from the perspective of MFI Ontology registration based on GEN Repository that conforms to (X)MDR ・・・ ・・ ・ Repository Repositories GEN for PSL *2 that conform knowledge management to PLIB *3 Note： IOO repository*4 for OWL-DL ontologies Ontologies in RDF/XML identified by URI * 1: ISO 18629 Process Specification Language * 2 : ISO 13584 Parts Library * 3: INTAP Owl Ontology repository, whose specifications are under development by INTAP, Japan “Sharing and advancing knowledge and experience about standards, technologies and implementations. 51

Architecture of GEN (1 of 2) • Gen is a client-server system with – PCs installed GEN-client with Squeak virtual machine as clients and la network Drive installed omni. Base DB as a file server. ・ ・ ・ “Sharing and advancing knowledge and experience about standards, technologies and implementations. 52

Architecture of GEN (2 of 2) • It is easy to transform it to rich client Web environment with – Web browsers installed GEN and Squeak as plugins l. Web server with Squeak and ・ ・ ・ + l. DB server with omni. Base DB or any other object-oriented DB such as Gem. Stone. “Sharing and advancing knowledge and experience about standards, technologies and implementations. 53

Main functionalities of GEN (1 of 2) • Main functionalities of GEN are; 1. Process Ontology （業務プロセスオントロジー） – to describe process flows 2. Know-how Ontology（業務ノウハウオントロジー） – for large-grained ontology for engineering rules for specific jobs 3. Basic Ontology（基礎オントロジー） – for small-grained ontology, usually common to all jobs 4. Notepad（雑記帳） – to take any kinds of notes freely and easily 5. Collaborative evolution on ontologies above and multi-version support 6. Links to anything identified by URI outside GEN 7. Scheduling expert subsystem for a specific job “Sharing and advancing knowledge and experience about standards, technologies and implementations. 54

Main fanctionalities of GEN (2 of 2) • Among them, the followings are essential and reusable to an ontology repository which managed by Ro. R and/or an experimental system of OOR and Ro. R. 2. Know-how Ontology（業務ノウハウオントロジー） 3. Basic Ontology（基礎オントロジー） 5. Collaborative evolution on ontologies above and multiversion support 6. Links to anything identified by URI outside GEN “Sharing and advancing knowledge and experience about standards, technologies and implementations. 55

Know-how Ontology and Basic Ontology (1 of 4) • From the point of GEN functionalities, Know-how Ontology and Basic Ontology are exactly the same. – Know-how Ontology is for large-grained ontology and Basic Ontology is for small-grained ontology. • For details, see my presentation on Open Forum 2008. • These functionalities are similar to the one of Protégé 3. X, but are more end-user oriented. • End-user can design a schema of ontology (i. e. class structure), concerning only “reference” and/or “attribute”. – Need not care about a directional “slot” and its “inverse slot”. – To define one “reference” automatically creates bidirectional relation and a inverse references, which is also naviable. “Sharing and advancing knowledge and experience about standards, technologies and implementations. 56

Know-how Ontology and Basic Ontology • Know-how Ontology and Basic Ontology do not support import/export facilities to (2 of 4) any specific syntax and format such as OWL in RDF/XML. • But, the (meta) structure of them are almost same as RFDS except that Ø its data types are different from the ones of RDF(S) and Ø its cardinality constraint is similar to the one of UML, which is not supported either in RDF(S) nor even in OWL 1. 0. • It is not difficult to enhance GEN so that it can import/export ontolgies in RDF(S)/XML under the restrictions above. • But it is better to use OWL 2. 0 syntax sugar to express Ø its UML-like cardinality constraints and Ø automatically defined inverse object properties. “Sharing and advancing knowledge and experience about standards, technologies and implementations. 57

Know-how Ontology and Basic Ontology (3 of 4) • It might be better to enhance GEN to support facilities; Ø to define a sub-class in terms of property, which a basic feature of DL, and Ø to support SPAQRL-like query. “Sharing and advancing knowledge and experience about standards, technologies and implementations. 58

• Know-how Ontology and Basic Ontology (4 of 4) User interface is a kind of mixture of Protégé, IE and Explorer. l. Address of the instance selected and their history – 選択されているインスタンスのアドレス l“Definition”, “Format” and “Instance Browser” tabs l. Instance browser l. Class hierarchy tree lgo back, forth and up l“Comment” and “Unstructured link” tabs l. Instance expression lコメント、リンク領域 l. Comments “Sharing and advancing knowledge and experience about standards, technologies and implementations. 59 59

Proposal • TEPCO may make GEN a kind of closed share-domain program with several NPOs such as – Wuhan university, – Korean university, – Lawrence Berkeley National Laboratory, – Tokyo International University and/or SC 32/WG 2. Note: I cannot commit this now. I need to negotiate this with TEPCO. • With your help, at least GEN should be internationalized and be made applicable to rich-client Web environment. • Then, based on GEN, we all can develop easily Ø an experimental implementation of OOR or Ro. R and also Ø an ontology in GEN that can be managed by OOR or Ro. R. “Sharing and advancing knowledge and experience about standards, technologies and implementations. 60

Thank you hori@tiu. ac. jp “Sharing and advancing knowledge and experience about standards, technologies and implementations. 61