1 / 61

Request for Study Period on “MFI for ROR” Hajime Horiuchi Tokyo International University

Request for Study Period on “MFI for ROR” Hajime Horiuchi Tokyo International University May 28, 2008. SC32WG2N1130. Topics. Type of Registry (Difference of Architectures ) What is ROR Background of ROR project Overall structure of ROR Issues. Evolution of Registry Technology.

cathy
Download Presentation

Request for Study Period on “MFI for ROR” Hajime Horiuchi Tokyo International University

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Request for Study Period on “MFI for ROR” Hajime Horiuchi Tokyo International University May 28, 2008 SC32WG2N1130

  2. Topics • Type of Registry (Difference of Architectures ) • What is ROR • Background of ROR project • Overall structure of ROR • Issues

  3. Evolution of Registry Technology Discover & Casting Web Service Semantic Registry Sharing of knowledge Cross Domain Interoperation Metadata Registry ROR Sharing of Software Sharing of Data DD/DS Sharing of development Methodology

  4. A Taxonomy of Architecture Types Target of the Standardizations Process Contents High (Narrow) SOS System of Systems Model Dependent (Structural) limited Alliance Domain Specialty Registry Of Registries ROR Cross Industries Metadata Dependent (Non Structural) SOA/SaaS Low (Generic) Cross Homes Diversity of Stakeholder High 102 108

  5. DIFFERENCE OF REGISTRY TYPE

  6. Registry to Support Engineering Registry to support Engineering High (Narrow) System of Systems SOS Model Dependent (Structural) limited Alliance Domain Specialty Registry Of Registries ROR Cross Industries Metadata Dependent (Non Structural) SOA/SaaS Low (Generic) Cross Homes Diversity of Stakeholder High 102 108

  7. Registry to Support Engineering Integration Registry Product Specifications Part Library Process Models Products Models Domain Ontology

  8. Registry to support Cross Industries Registry for Interoperation High (Narrow) SOS System of Systems Model Dependent (Structural) limited Alliance Registry Of Registries Domain Specialty ROR Metadata Dependent (Non Structural) Cross Industries SOA/SaaS Low (Generic) Cross Homes Diversity of Stakeholder High 102 108

  9. Registry to support Cross Industries Registry Product Information Supply Chain Business Information Party Information Business Process Model Domain Ontology

  10. 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/SaaS Low (Generic) Cross Homes Diversity of Stakeholder High 102 108

  11. SOA/Could Computing Saas Saas Cloud Saas Saas

  12. Registries to support SOA Saas Ontology Ontology Ontology Object-URI Object-URI Object-URI Saas Access Protocol Access Protocol Access Protocol Saas Saas Saas

  13. In the Future ? Web service Registry as Service Saas Registry as Service Saas Saas Saas

  14. ROR: Registry of Registries TO SUPPORT CROSS INDUSTRIES

  15. 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(JTC1 Japan) • SC32WG2 + TC184/SC4 + ECOM + LCDM members • Just started at officially on this April

  16. Original goals of ISO/IEC19763 standards ROR: Registry of Registry ROR Registry Registry Registry Registry Retails Logistic Manufacturing Registry Interoperation Heterogeneous Registries

  17. WHY WE NEED ROR ?

  18. 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)

  19. 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.

  20. Different Views by industries on a same product Home electronic Products ISO13584 standards GS1, EPCG Home Electronic Category Electronic Parts Category Item-Number Product-Number Metadata Attributes for Retailing Attributes for Manufacturing Item Master DB PLIB No interoperability

  21. Closed Processes and Registries Manufacturing Retailing Merchandising Design Buying Assembling PLIB Item Master Selling Inspection Invoice Delivery

  22. Emerging needs for the Model Sharing Actual reificationofCross Industries Interoperation is needed Manufacturing Product Life Cycle Management Hazardous Materials Management Retail ing Product Industrial Waste Processing Logistic & Distribution Product Traceability Consumer Artery & Vein

  23. Every domain has own Registry Registry Registry Manufacturing Registry Product Life Cycle Management Hazardous Materials Management Retail ing Product Registry Industrial Waste Processing Registry Logistic & Distribution Registry Product Traceability Consumer Artery & Vein

  24. 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.

  25. EDI Related Standards RosettaNet GS1 Industrial St. CIDX De Jure IETF - AS2 W3C - XML • OASIS • ebMS • WS • - R&R • ISO • EDIFACT • - ebXML- PLIB EPCグローバル eBusiness Asia UN/CEFACT JIS EDIFACT/CII CEN WCO ANSI X12 JADM HL7 SWIFT

  26. Product Tracing by RFID tag

  27. A Draft of Framework for Information Infrastructure (ECOM, 2007) Web Service Providers MSDS Reg. Service Part Retrieval Service Accounting Service Ordering Service Item Reg. Service Portal Service UDDI ROR BusinessOriented Process Integration Material Oriented Process Integration Tax DB Retail Item DB PLIB MSDS Cargo Tracking

  28. What is MFI • Metamodel Framework for Interoperability • ISO/IEC19763 series of standards • A set of Metamodels for; Registering Models (Not for describing model or ontology) • MFI is an Application of MOF (1.4)

  29. ROR by MFI MFI（ISO/IEC19763） series of standards Metamodel for process registration Metamodel for ontology registration Core model Metamodel for model mapping Registration Procedure ROR (Cross Domain Registry) Mapping Registry Registry Registry Registry Industrial registries Registry Registry

  30. Cross Domain ROR OID MFI Registry Registration Authority RA UUID Model Mapping Service Domain Model ROR Data Elements 基本情報要素 Ontology Search Service Value Domain Basic Ontology Domain A Domain B UID Domain Ontology UID Domain Ontology RA RA Registry Registry Terminology Terminology Terminology Terminology Registration Procedure Industrial domain Industrial domain Registration Quality

  31. ISSUES FOR ROR&MFI Standards

  32. 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.

  33. Use Case Home electronic Products GS1, EPCG ISO13584 standards Home Electronic Category Electronic Parts Category Mapping Item-Number Product-Number PLIB Item Master DB

  34. Issues Data Quality Specification Home electronic Products GS1, EPCG ISO13584 standards Mapping Home Electronic Category Electronic Parts Category Change Control Mapping Ontology Item-Number Product-Number RA/RO Registration Procedure Global Unique ID Casting PLIB Item Master DB

  35. How to Cast a registry call Level 1 ROR Search Level 2 PLIB Metamodel ITEM Master Metamodel M2 Inquire Level 3 PLIB Model ITEM Master Instance PLIB Model M1 JAITA JAMIMA

  36. Level 1 Mapping Variation • Exactly Same • Similar to • Looks like

  37. 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 ebXML Core Component to be used for type matching

  38. 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 ebXML to each element of the Schema

  39. Metamodel Mapping ebXML CC Metamodel PLIB Metamodel Item Master Metamodel CWM CWM Mapping Process Mapping Rule Instance MFI: Metamodel for Mapping

  40. MFI 4: Model Mapping

  41. Type Matching through CC ebXML Core Component (ACC: nn) 1 1 * GS1 ID * PLIB Element Item Master Element Mapping TS- TV-42- name (ACC-nn) TV-42-Toshiba name (ACC-nn)

  42. ebXML Core Component • Standardized Information elements for Business Information to be used in the electronic business Core Component Business Information Aggregated Business Information Entity Aggregated Core Component Person Health.record ACC 0..* ABIE Core Component Type ASCC Business Information Entity Resident *..1 CCT BCC BIE Basic Core Component Patient.Person Text Location

  43. Metamodel of CC CCTS : Core Component Tech. Spec. V-3.0

  44. CWM: Relational Data model

  45. CWM: Metamodel for Record Traditional COBOL file, CSV file

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

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

  48. Mapping PLIB Class RecordFile Part ITEM_Master PLIB property RecordField Part_Number Item_Number

  49. Re: GEN(General kNowledge Navigator) OKABE, Masao Corporate Systems Department Tokyo Electric Power Company Inc. (TEPCO) 2008.5.20

  50. What is GEN? • GEN is General kNowledge 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 RoR or • an experimental implementation of OOR or RoR itself.

More Related