We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byMarc Cramton
Modified about 1 year ago
ECIMF relationship to ebXML, RosettaNet & OAGIS Andrzej Bialecki Chief System Architect CEN/ISSS/WS-EC Plenary Meeting, Oslo, 12 June 2001
Copyright © WebGiro AB, All rights reserved. ECIMF Scope Scope: Interoperability of different e-commerce frameworks Integration of internal business processes with external e-commerce interfaces Methodology: Semantic mapping of corresponding concepts Process mediation between differing business process definitions Syntax mapping between differing message formats and transport protocols Primary goal: e-commerce partners interoperability
Copyright © WebGiro AB, All rights reserved. ebXML, RN & OAG: scope Current ebXML scope: no usable common Business Document definitions no usable common dictionary (CC) Well-specified BPSS, CPP/CPA and TRP Primary goal: e-commerce partners interoperability Current RN scope: No Reg/Rep, discovery, CPP/CPA Continuing alignment with ebXML Well-specified BP, TRP, business messages Primary goal: e-commerce partners interoperability Current OAG scope: TRP not in scope Well-specified business messages BP definitions: ? (loosely defined scenarios ???) Primary goal: e-commerce applications interoperability
Copyright © WebGiro AB, All rights reserved. RosettaNet & OAG Common approach: Development of unified dictionary, message and business process definitions Integration / interoperability achieved by partners’ full conformance to the common model Prerequisites: Integration of internal processes & applications to conform to the common interface (using unspecified means…) All parties MUST conform to the common framework in their external interfaces Areas of concern: How to integrate internal processes to the required external interface?
Copyright © WebGiro AB, All rights reserved. RN & OAG: Conclusions RosettaNet and OAG bring a wealth of industry- specific, concrete and common models and scenarios ECIMF addresses topics that are prerequisites to integration of RN or OAGIS interfaces with internal processes and applications CONCLUSION: Both RNIF and OAGIS should be considered as important reference frameworks to check the ECIMF concept significant reuse of industry-specific models and scenarios will help ECIMF ECIMF can help businesses to integrate RN or OAG specifications with their internal applications/processes
Copyright © WebGiro AB, All rights reserved. ECIMF and ebXML Focus on Business Process Modeling and top-down approach Formal methodology to model e-business interactions from BP to Message to Protocol levels Interoperability between differing specifications Formal specification for achieving interoperability in case of different interfaces/preferences ebXML: CPP/CPA ECIMF: MANIFEST Layered approach to interoperability
Copyright © WebGiro AB, All rights reserved. ebXML CPP: CPA formation Prerequisites: Use of common semantics, BP model and syntax (based on e.g. ebBPSS) Use of common business document formats (implied) Areas of concern: How the “match” is defined and established? ebCCP p. 85 describes only very simple example, where the BP specs don’t differ How to “match” BPs based on different standards (e.g. RosettaNet PIP and OAG BOD)? (different semantics, models and interactions) How to express message format transformations, if needed? Role Packaging Transport Role Packaging Transport match
Copyright © WebGiro AB, All rights reserved. E-Commerce Framework 1 (F1) Interoperability: ECIMF approach Meta-framework for defining the transformation rules between similar Business Processes, but expressed using different frameworks Uses semantic alignment, process mediation and syntax mapping to ensure interoperability even between different frameworks Applicable also to integration of internal processes to external interfaces (which is a special case of differing frameworks) Areas of concern: Complex – needs good tools to simplify the task for end-users Partially overlaps with other approaches needs coordination with widely recognized methodologies, most of all with UMM ECIMF Navigator Semantic mapper Common F1 unique F2 unique Conflict Process mediator F1 M F2 Actors Roles Use cases Scenarios Processes Transactions Activities Messages Data elements Packaging Protocols Syntax mapper F1 Map F2 E-Commerce Framework 2 (F2)
Copyright © WebGiro AB, All rights reserved. ECIMF Navigator Semantic mapper Common F1 unique F2 unique Conflict Process mediator F1 M F2 Syntax mapper F1 Map F2 Interoperability: ECIMF vs. CPP/CPA approach ebXML CPP/CPA Uses fixed (common) semantics Uses common BP specification for both parties Assumes that parties are able to (somehow) interface internal processes to the common BP Allows for negotiation of interoperability on the Role level (choosing from a list), and transport/packaging level (part of ECIMF Syntax level). ECIMF Aligns the semantics of different frameworks Uses mediation between different BP specifications Can be applied to integrate internal processes with external interfaces Specifies transformations of different message formats, packaging and protocols Role Packaging Transport Role Packaging Transport match different semantics common semantics different BPs common BP common messages different messages
Copyright © WebGiro AB, All rights reserved. ECIMF and ebXML: conclusions Currently CPA addresses only simple cases of common models and semantics It doesn’t specify formal process/approach to form CPA in case of differing semantics and process definition It doesn’t specify more complex transformations between incompatible message formats and data elements It doesn’t address the issue of interfacing internal processes to common external BP specifications ECIMF will address these issues by semantic mapping, process mediation and syntax mapping ECIMF could use extended CPP/CPA and BPSS to express the transformation rules CONCLUSION : Alignment and close cooperation between ECIMF and ebXML (CPP/CPA & BP work) is very desirable and should benefit both projects.
Copyright © WebGiro AB, All rights reserved. Alignment of ECIMF with UMM More and more frameworks use RUP and UMM RosettaNet and ebXML UMM represents accumulated knowledge of many domain experts UMM is based on widely accepted industry standard (RUP) Current status: ECIMF: Semantics UMM: BOV + FSV ECIMF: Dynamics UMM: FSV + BOV + IFV ECIMF: Syntax UMM: IFV
Copyright © WebGiro AB, All rights reserved. Summary ECIMF project needs very close cooperation with ebXML, RosettaNet, OAG and TMWG All projects should benefit from the cooperation, because the strengths of one seem to match the weaknesses of others Significant reuse of concepts and experiences is expected, desirable and much welcome Proposed action point: Establish a task force team including representatives from each project to work on common strategy
Copyright © WebGiro AB, All rights reserved. Questions & comments Andrzej Bialecki
Agent Based Software Development Michael Luck, Ronald Ashri and Mark dInverno Chapter 4: Methodologies and Modeling Languages.
Chapter - 5 Understanding Requirements Unit II. Introduction Definition : “The broad spectrum of tasks and techniques that lead to an understanding of.
HL7 Templates A means to Manage Complexity. Objectives What is an HL7 Template? What types of constraints can HL7 Templates define? What types of HL7.
Status on the Mapping of Metadata Standards ISO/IEC 11179, SDMX, and Others Arofan Gregory, Executive Manager Open Data Foundation, Inc. METIS Meeting,
An Introduction to Object Modeling An Introduction to Object Modeling The approach of using object modeling during systems analysis and design is called.
Model Driven Software Development KP-IT Shared Application Services – EIS/SOA Rex Lam, Pascal Mattiocco, Enrique Meneses, Michael Rossman April, 2012.
05/10/20101 MODEL DRIVEN INTEROPERABILITY First Workshop on.
Module 2: National IEA process design and organization.
Standards & Interoperability Kickoff HHS – ONC September 20, 2010 Office of Standards and Interoperability 1.
Metadata and Digital Library Development Introduction: Background, Goals, and Course Outline Course design: David Ruddy Cornell University Library 1.
3rd meeting COTS team April 25, 2007, Helsinki. AGENDA 9.00Opening of meeting 9.05Approval of agenda, minutes, Goal setting 9.15Feedback on the specific.
WS Choreography v.0-1 Overview This is work-in-progress David Burdett, Commerce One 18 June 2003.
Practical ebXML Registry uses for interoperable eBusiness Open Forum 2003 on Metadata Registries 8:40am to 10am January 22, 2003.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Copyright OASIS, 2001 OASIS Recent Technical Developments John Borras Office of e-Envoy Cabinet Office UK Government June 2003.
Software Reuse and Component-Based Software Engineering CIS 376 Bruce R. Maxim UM-Dearborn.
1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Process Improvement IS301 – Software.
2/5/2014 4:51 PM SAEAF Education Series Session 1: Introduction and Overview September 2009 HL7 Services-Aware Enterprise Architecture Framework (SAEAF)
Automated eContract Negotiation in Web Service Environment: Trust Management and Electronic Contract Management Aspects Doctoral student Marius Šaučiūnas.
Competence is the demonstrated ability to apply knowledge and/or skills and, where relevant, personal attributes. A certification scheme contains.
Introduction to knowledge management. What is knowledge management Knowledge management can be difficult to define, because it encompasses a wide range.
Software Engineering Model Driven Architecture Software Engineering 2011 Department of Computer Science Ben-Gurion university Based on the book: MDA Explained:
1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Quality Management IS301 – Software.
Aggregating Web Services: Choreography and WS-CDL Nickolaos Kavantzas, Web Services Architect Designer and Lead Editor of WS-CDL Oracle Corporation, April.
1 Notes content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. System Models IS301 – Software.
Introduction to Design Rules in NATO NISP. Integrated EA conference London March
Service Framework Reference Models Bill Olivier Director, CETIS.
BPEL4WS Business Process Execution Language for Web Services Jim Clark eBusiness Strategist
Practitioners Workshop on the "Standards for baseline scenario identification and baseline emission calculations" 4-5 March 2011 in Bonn, Germany March.
© 2016 SlidePlayer.com Inc. All rights reserved.