Copyright OASIS, 2004 David RR Webber XML eBusiness USA [email protected] ebXML Update Toward a SOA...

Copyright OASIS, 2004

David RR WebberXML eBusiness

[email protected]

ebXML Update

Toward a SOA Paradigm

ebXML Update

Toward a SOA Paradigm

Presentation, August 2004 NISTGaithersburg Maryland


ebXML in the News

"As ebXML becomes standardized, it will become the de facto way everyone does business."

--Tony Scott, CTO, General Motors

Interview in Information Week – March, 2004

http://www.informationweek.com/shared/printableArticle.jhtml?articleID=18201098

http://www.informationweek.com/shared/printableArticle.jhtml?articleID=18201098


ebXML in a nutshell

• Globally developed standard for

– Exchanging business messages

– Conducting trading relationships

– Defining and registering business processes

– Communicating data in common terms

– Assembling business transactions

• Using Internet as delivery vehicle


ebXML developed by

• United Nations Center for Trade Facilitation and Electronic Business

• Developers of EDIFACT

• One of four organizations in the world that can set de jure standards

• World’s largest independent, non-profit organization dedicated to the standardization of XML applications

• More than 400 members in 26 countries

Phase 1 completed May 2001 by 4500 participants representing

2000 organizations in 150 countries from all major

continents


ebXML Adoption - 2004

Comparison of ebXML adoption by region, number / size / scope of projects as of December 22, 2003

China – 11,000 ebMS

serversUSA – DOD

EMALL

EU – Formal Adoption


Backed by Industry Groups

The Open Healthcare Group


Interactivemodels

Conventionalmodels

A New Approach to Software Engineering

AnalysisSpecification

Design

Coding

Test

Maintenance

Developers

Adaptation, integrationInstallation

Use

Needs

Requirements

ProcurementBusinessUsers


• Traditional Approach– ETL– EAI– UML– Data warehouse– B2B + electronic commerce

• New Holistic Approach– Service Oriented Architecture– Business-centric models– Context driven environment– Semantic vocabularies and ontologies– Leverage XML

Paradigm Shift


Cross-Enterprise Service Centric Digitization

Transaction Centric Digitization of Simple Task & Processes

Process Re-Engineering

Process Improvement

Value Co-Creation via Customer Centric Collaboration

Extreme Mobility Infrastructure

Occasionally Connected Application

Wearable Computing

Business Process Evolution


Agenda • ebXML Today

– Why ebXML? (deployment Landscape)

– Classic ebXML

– Enhanced ebXML

– ebXML component drill-down

• What’s next? - Front-office EPR (Electronic PRocess) work

• ebXML in the marketplace - vendor products

• ebXML projects

• Summary


Deployment LandscapeDeployment Landscape

Today’s medium to large enterprises face a bewildering array of interchange format and mechanism choices

Chasing the technology ‘bouncing ball’; delivering real ROI for eBusiness


The CIO nightmare• What standards do I choose?• How do I build significant ROI for my organization?• Can I leverage my existing systems?• What resources are available to deploy my

solution?• What are my partners doing?• How much of this is real?• How do I avoid being in a vendor revolving doors

strategy?• What if I just build it my way and ignore everyone

else?


Identifying the Needs• What are you trying to build anyway?

• Better EDI system?

• Reach SME partners more effectively?

• eMarketplace solution?

• Next generation XML system and network?

• Open eGovernment systems?

• Customer facing service solution?

• Integration of major corporations applications?

• Common industry collaboration and vocabularies?


• People accept that a digital world is coming and are adjusting their work habits accordingly:

– virtual presentations and meetings

– all digital documents and transactions

– digital photographs, voices, sounds, RFID, and signatures (online banking, iTunes, UPS, Radio Shack, Home Depot).

• Digital artifacts shared factor – naturally multi-lingual.

• Vast gulf between First World and Third World.

The Challenge of Change


Business Challenges

• In determining operational needs there are four levels and areas to include:

– The first level is the overall operational approach to solving large enterprise level interactions,

– then enterprise to small business interactions,

– small business to small business interactions

– and service solution to customer.

1

2

3

4


Business Goals

• Since everyone’s business needs vary depending on their own circumstances, the focus here is on providing the means to understand the technology capabilities and then giving guidelines on how those relate to solving typical business needs

• Obviously the optimum business solution is to purchase just the right amount of technology to solve the given business requirements.


How do you put this all together?

Action Event

InformationRuleWhatWhy

How When

Where / Who Where / Who Where / Who

Action Event


How When

Action Event


How When


How the pieces fit together

Classic ebXMLClassic ebXML


Classic ebXML vision

• Two trading partners collaborate together to create working relationship

• Interchange defined as requestor / responder• Business transactions exchanged control the state

of the process• Sharing of definitions and business understanding

between partners within a community• Allows smaller companies to participate, not just

large corporations


Initial Pieces – Defining the Interaction

Bulk Buying

Business Process

Specifications(BPSS)

CollaborationAgreement

(CPA)Specifies Bulk Buying

Business Process

Check Product AvailabilityDealer LocationProduct RequirementsSubmit Purchase Order

Schema definitions (XSD) + content processing templates

Contains

Contains

Business Transactions

XML Messages Grammars

Supplier<<BinaryCollaboration>>

Dealer


Classic Two-Role Business Process• Requestor / Responder interaction model


ebXML components• Technical Architecture (TA1.04)

• Message Services (ebMS – MHS)

• Collaboration Protocol Agreements (CPA / CPP)

• Business Process ( BPSS )

• Registry Services / (RegRep / RIM)

• Core Components (CCTS / UBL)


ebXML CPA / CPP componentebXMLPARTNER A CPP

MESSA GE HA NDLI NG CONF I GURA T I ON:

P lace the interchange configurationyou want r ight here

A GREEMENT D A TE: Year: 2003 Month: 06 Day: 09 Time: 01:01 :00 Until: 2004

Party Name: C om pany A Web site: http: / / ourwebsite.com

Party ID: 123456 ID type: D UNS

Alias: AAA Role: initiator

Contact EMail: [email protected] Agreement Ref: autotech- bods- 01

Preferred standard: OA G BOD s Reference URL: http: / / ourwebsite.com / cpa/

Process Name: Autom otive assem bly supply

Process Script URL: http: / / m ywebsite.com / bpss/ autoasm 01.xm l

Description: This is an Autom otive S upplier Agreem entusing O AG BOD m essages

Me ssa ge ha ndlingConfi gura tions

Libra ry

Service Mode: system test

End Point URL: http:/ / 127.0.0.1:8080/ ebMS-MS/ m sh

Signature Keyname: I nitiator

S END

Item Name: S ending Message

Shortname: Msg_ O ut

Action Send Msg: Out_ XML

Action Respond Msg: Rspd_ X ML

RECEIVE

Item Name: Received Message

Shortname: Msg_ I n

Action Respond Msg: C onfirm _ XML

Action Recv Msg: I n_ XML

S EN D

CollaborationD eta ils

RECEI VE

S END

Item Name: default

RECEIVE

Item Name: default

CPA Status: proposed( p ro p o s e d / a cce p te d / p e n d in g )

S R M S H

ACK ALL NO ACK

P E R M S G S S L

S IG N RE S P ND

ParticipantInformation

Messagingpreferencesand configuration

Message exchange details


Classic ebXML exampleEach partnerhas ebMS exchangesystem

INTERNET

Partner A Partner B

Partn e rCPA(s) Partn e r

CPA(s)11

ebXMLebMS

ebXMLebMS Re spo nd e r

Do cume nts

Re qu e ste rDo cume nts

2

2

Excha ngeTra nsa cti ons

Excha ngeTra nsa cti ons

De live ryQue ueDe live ry

Que ue

XM L s che m a

XM L s che m a

Partner BBusiness

Application(s)

Partne r ABusiness

Application(s)

ebXM Lenveloping

anddelivery

S OA Pm essaging

44

5 5

6 6

configure

s

configures

SENDING

RECEIVING

3

3

BPSS implicitfrom exchange flow


Classic ebXML example + Registry

INTERNET

Partner A Partner B

Partn e rCPA(s) Partn e r

CPA(s)11

ebXMLebMS

ebXMLebMS

ebXMLRegistry

(optional)3

Re spo nd e rDo cume nts

Re qu e ste rDo cume nts

2

2

Excha ngeTra nsa ctions


De live ryQue ueDe live ry

Que ue

Clie n t Use rIn te rface

Us e r Profile sCPA look upDocum e nt De finitionsSche m a XSD

XM L s che m a

XM L s che m a

Partner BBusiness

Application(s)

Partner ABusiness

Application(s)

ebXM Lenveloping

anddelivery

S OA Pm essaging

44

5 5

6 6

configure

s

configures

SENDING

RECEIVING

Registryprovidescommon referencepoint

BPSS implicitfrom exchange flow


Extending the core architecture

Enhanced ebXMLEnhanced ebXML


Enhancing ebXML - Multiparty

• Need to handle complex flows beyond two-party configurations

• Today’s internet world is rarely simple

• Partners perform multiple roles and interact with and provide range of services

• Knowing context is vital

Partner A Partner B

Partner C

Partner D

Partner E

Partner F

Partner G

Partner F

Partner G

ebXMLBPSS

Model andScenario

com plete scenario of

co llabo ra tio n

1


Action checkBuye rsC red it

To Role buye r

Bu

yin

g A

ge

nt

Cre

dit

B

ure

au

Succe ss R espondC red itSta tus

condition

O K

Fa ilure cred itSta tusUnknown

condition in va lid

Pro

du

ce

r

Action R equestPr iceQ uo te

To Role trad ing se rv ice

Action R equestPr iceQ uo te

To Role buye r

Ma

rke

tpla

ce

Succe ss respondPriceQ uo tes

condition

O K

Fa ilure noSe lle rsR esponded

condition in va lid

Succe ss respondPriceQ uo te

condition

O K

Action D rawD ownC red it


Se

lle

r C

red

it

Se

rvic

e

Action Accep tPr iceQ uo te


Action igno rePriceQ uo te


Action R ep len ishC red it


Se

lle

r C

red

it

Se

rvic

eW

inn

ing

Pro

du

ce

rL

osin

gP

rod

uce

rs

Multiparty Model with BPSS


EventsRules

TransactionTransaction

SchemaSchema

ContractContractAgreement Pattern

WorkflowWorkflowModeling & Business Patterns

request

process

request

process

response

process

reject

accept propose

counter

Exchange Exchange

SpecificationSpecificationModel & Schemas

Nouns

VerbsTransport

RolesConceptConceptRegistry

Tem

plat

eT

empl

ate -- d

rive

n dr

iven

Business GoalsBusiness GoalsGoal Pattern

CAM templateCAM template

Context

Business Agreement Languages (RINs)

Choreography & Coordination Lang.

(BPSS)

Collaboration Profile Agreement (CPA)

Context Driven Information

Exchanges (CAM)

Semantic Registry

Implementation Through Component Layers


ebXML components work today• Technical Architecture (ebSOA)

• Message Services / Web Services (ebMS – MHS)

• Collaboration Protocol Agreements (CPA / WSDL)

• Business Process ( BPSS )

• Federated Registry Services / Semantic Content (RegRep / RIM / SCM – OWL)

• Core Components (CCTS / UBL)

• Content Assembly Mechanism (CAM)

• Context Management / State Management (new)


Enhanced ebXML

jCAM

W eb service(optional)

ebXMLRegistry

(optional)

Clie n t Use rIn te rface

S OA Pm essaging

ebXMLBPSS

Model andScenario Us e r Profile s

CPA de tailsDocum e nt De fin itionsSche m a XSDCAM te m plate sConte xt Ins tance s

BP S S script

Partne rCPAs

BPSSScrip t

Partic ip atin gDocu me n ts

XM L s che m a

CAMte mp late s

Conte x tV a ria ble s /

Rule s


ebXMLebMS

De live ryQue ue

PartnerBusiness

Application(s)

6

7

ebX M Lenveloping and

delivery

INTERNETExcha nge

Tra nsa ctions

8

Eachpartnerhasexchangesystem

1

2

1

3

4

5

Complete CollaborationDetails Drive each ebM S

VocabularyManagem ent

Serv ices

ContentManagem ent

Serv ices

W SDLin te rface (s) 9

EX CHANGEPACKAGES

conte x t + rule ste m pla te s


Modelling the Business Process• from the model –generates actual BPSS as XML instructions


Deterministic linking of BPM to layers• Each step consists of deterministic action and outcomes

Select associated responding document

GroupPossible Responses

Configure outcomes and flow control

Transport layer returnsettings


Align BP steps to information systems

DealerLocation Activity

DealerLocator

Map To

PurchaseRequest Activity

DealerLocator

Map To

VehicleHistory Activity

DealerLocator

DealerLocator

AvailableVehicle Activity

Map To

Map To

PurchaseApproval Activity

Map To [Business Error]

e.g., Map DealerLocation Activity to the DealerLocator Web service Business Analysts

map B2B Transactions to the services available in Back-end Service Oriented Architecture (SOA)


ContentAssemblyTemplate

Configure the Business Exchange Rules

XMLinstance

structure(s)

Business context rules

+Content Reference rules

+Data Validation rules

+External Mapping rules

Logical business transaction can have more than one structure layout

can add inline rules directly into structure

makeOptional()excludeTree()

item type="noun" name="Agency/@AgencyID" UIDReference="ukt000910"

<conditional expression="'//SupplierID' and lookup(value,'SGIRWSDL:supplierID_check')"<MapRule output="type" input="Sales/Company/Year/Qtr/Product@type"/>

Simple Declarative Statements

BPSSStep

transactiontemplate


• Context is the pervasive driver to effective engineering

• Drives dynamic process configuring and control

• Ensures accurate information capture, packaging and delivery

• Key to correct relationships between partners in a collaboration

Lack of context control mechanisms is the most prominent reason why legacy e-Business systems are difficult and complex to extend and support

Date: circa 15681 : the parts of a discourse that surround a word or passage and can throw light on its meaning2 : the interrelated conditions in which something exists or occurs

Date: circa 15681 : the parts of a discourse that surround a word or passage and can throw light on its meaning2 : the interrelated conditions in which something exists or occurs

Understanding about Context


Aligning the Concepts – Core Components

Create Long Term Contract

Forecast Component Requirements

Send Planning Document

Place Order

Ship Materials

Customer

Arrange Payment

Supplier

Domain: Matl Mgmt

Industry: Auto •Ship NoticeRegulatory: Safety

Change Lvl

Container

Serialized ID

ProdId

Part Number

Ship’d Qty

Context UBL - work on supply chain messaging using CCTS


Generating a Context Instance• Add parameter value rules and document value rules

Check a document and change a BPSS parameter

Create a rule and set a value

Configure ContextInstance header


Moving to deployment

Business agreement

Drives documentexchanges


Some extended details on each piece

ebXML component drilldownebXML component drilldown


ebXML example interchange integration

ebXML

MSH

ebXML

Process

Server

ebXML

MSH

Apps

B2B—Tradin

g Partne

r

CPA BPSS

Internet Services

ebXML

SOAP

Business Process

Collaboration

DMZ

Internal Firewall Inte

rnet

DB

Legacy

Apps

COTSApps

Legacy

Apps

Application Server(s)

Orchestration Services

BusinessApp’

Services

SO

A L

ayer

BusinessApp’

Services


Messaging Layers

CouplingTighter

Looser

SecurityLimited

Extensive

ebXML

Web Services for XML Message

Web Services for RPC

Reusable Components

SOAP/HTTP (JAX-M for ebXML)

ebXML

WS

SOAP/HTTP (JAX-RPC)

ORB (RMI/IIOP)

WS

SOAP/HTTP (JAX-M for WS-Routing)

Typical access via:

Granularity

Small A2A Integrated Apps

Homogeneous

Application

WS

Big A2A Integrated

App Families

B2B Market, Global Multi-enterprise

ebXML

Application Arena Message Services


Communication Protocol Envelope (HTTP, SMTP, etc.)

SOAP Messages with Attachments MIME Envelope

MIME Part

MIME Part

SOAP-ENV:Envelope

SOAP-ENV:Headereb:MessageHeader

eb:TraceHeaderList

Other:etc…

SOAP-ENV:Bodyeb:Manifest

eb:etc…

Other:etc…

Payload

Message Package

Header Container

Payload Container(s)

ebXML Header Information

ebXML Message Service Handler control data

ebXML Message Structure


Interchange sequence detail• A complete interchange consists of successfully:

– passed authentication/access control– sent the bits to the other end– checked the packaging– checked the header structure– checked the header data– checked the signature on a header (*)– decrypted the payload (*)– verified the signature on a payload (*)– checked the structure of a payload (*)– passed the translated payload to a backend system/application for

processing– Backend application successfully processed the payload– Receipt confirmation (*)

Note: Items denoted (*) are optional


WSDL and ebXML CPA / BPSS

WSDL provides:

Service name Service parameters Endpoint for invocation

ebXML CPA provides:

Service name and parameters Endpoint for invocation Role of an organization in the

context of a service Failure scenarios

WSDL identifies:

Business processes ebXML BP identifies

Business processes Roles an organization must play Messages being exchanged Error handling

article comparing messagingtechnologies at ebXMLForum

http://www.ebxmlforum.org/articles/ebFor_Art_20030613_01.html

http://www.ebxmlforum.org/articles/ebFor_Art_20030613_01.html


ebXML Registry - XML document management• XML Registry +

Repository • Life cycle

management features

• Query management engine

• Security features includes digital signatures, user Ids

• Classification of any type of object

• Federation of Content

Registry

Interface Life CycleManager

QueryManager

SecurityManager

PersistenceManager

Authentication

Authorization

Soap

RepositoryDatabase with RIM

RegistryObjects Organization

ExtrinsicObjects

BPSS, CPA, CC

http://registry.oasis-open.org

http://registry.oasis-open.org/


Storing the Enterprise Artifacts

Motivation Time People

Specifications Schema

Workflow

Contract

Directory Services

Collaboration PartnerProfiles - CPP

Collaboration PartnerProfiles - CPP

2

1

3

4

5

Presentation

Collaboration PartnerAgreements- CPA

Collaboration PartnerAgreements- CPA

Artifact relationships

Content Assembly Mechanism - CAM

Content Assembly Mechanism - CAM

BP SpecificationBP Specification

Data/Codes Services/Functions Network

XFormsXForms

MSH/SOAPMSH/SOAP

Source: BCM Lubash Pyramid

VerbsVerbs

MessagesMessages

RulesRules EventsEvents

ProcessProcess

RolesRoles

TransportRouting, Packaging

TransportRouting, Packaging

NounsNouns

Core Components

Core Components

WSDLWSDL


Registry Roles “A semantic registry is the key foundation block upon which global electronic business exchanges will be built”.

BusinessAnalyst

Web Interface

InformationProfiles

Distribution

Administration

Program LevelSemantics

Information Engine

Industry Business StandardsRegistry Protocol StandardsebXML, ISO11179, OASIS,

OAGi, RosettaNet, UBL, UDEF

XML

Software Developers

Interchange


Capturing Noun Semantics• Draft layout for

storing noun details in registry

See: OASIS Registry Semantic Content Management sub-committee work (SCM SC)

Can use DesignerTools to automatically generate from XSD model

http://visualscript.com/index.htm


Automating Trading Partner Setup Example

ebXML Server

ERP PO XML PO

ERP XMLPurchase Order

ebXML Registry

ebXML ServiceLayer

Custom LOB

Custom Invoice

ERPSystem

Accounting System

ebXML Server

ERP to Accounting PO

Trading Partner Map

Custom XML Invoice

Schema& Map

Exchange Profiles to quickly configure relationship


Summary• Enhanced ebXML allows business users to logically

decompose the problem and express it coherently and reliably

• Templates capture the business scenarios and rules

• Templates derived to ebXML artifacts – CPA, BPSS, CAM, WSDL, plus context parameters as needed

• Deployment environment driven by software templates

• Industry groups create catalogues of re-usable solutions


Toward a complete end-to-end solution including services

http://eprforum.org

What’s next?

Front-Office EPR work

What’s next?

Front-Office EPR work


EPR Uses Workcards as a GUI Metaphor

Participant and ContextBased Architecture

Participant can be:1. Traditional User2. Machine or Device acting

as a Proxy for a User

Environmental Context dynamically modifies Declarative Display Metaphor


EPR Folder’s Core ComponentsObject Models Organizing and Managing Tasks

Service Portals SERVICE PART

EPR Folder Container:

DokumentkortStyrer tilgang til blankett- og

dokumentmaler samt arkiverte Dokumenter.









Document cardHandles all the

Documents in the folder.WS linking

Steering Card functions

Workflow cardSupport to adm. working

process in the business logic.(Often RuleControlled ProcessFlow)











Job card (Service card)

Def. of physical Instructions in a working process.

Includes inspection and reports.

Steering Cards:

Arbeidsmappe( Opprettes når ny bruker eller ny process )Arbeidsmappe

( Opprettes når ny bruker eller ny process )

Working FolderContain everything a user needs in work. All Working Folders are divided into phases Related to progress.

Role Service +

UserID phase

Steering card

Single Sign-On (PKI) portal:

(Security Domains)


Networked devices

Workcards adapt to user environment

http://www.nokia.com/nokia/0,6771,47550,00.html

http://www.nokia.com/nokia/0,,33210,00.html


Template Driven Application Infrastructure

• EPR – Electronic Processes• Instead of using UML to craft solution model – the

application infrastructure is provided already with task-centric focus - erpAPL

• Business rules, scripts, workcards and templates in XML are used to configure the solution environment to the target domain - eprXML

• erpAPL is modular – so a lightweight solution is possible – that can be extended to a full-featured deployment as needs grow

• Deployment in-front of legacy applications with transaction exchanges as interface


Solution Architecture

Templates - Capture Business

Process Context details

Reference – Domain Ontology and

Semantic Information

References

Generate – XML artifacts that drive the

implementation components

Creates

Technology – Implementation

components

Runs

Processes – state management,

linking and switchingIntegration – legacy system interactions

Tracks

Portal – user interfacedynamically configured

Enables


eHealthcareeprApl

eGovernmenteprApl

CAM processor

Legacy systems

General epr

templates

Public systems

XML documents(content)

Communication infrastructures

eprXML engine

eHealth epr

templates

eGov epr

templates

BCM switch/link

Blue: ePROBEYellow: others

Web services + ebXML

Integrating EPR applications together

XML SOA - Process and

Exchange rules


Next Steps

• Work needed: – Formal Publication of OASIS Specification on EPR

– Continue development of EPR application (eprAPL)

– Library of EPR templates by industry

– Integration with OASIS Registry semantics

– Integration with BPSS and ebMS

– Publishing of initial open source implementation


Vendors Products

ebXML in the marketplaceebXML in the marketplace


Vendors Products• Full list available from

http://ebxml.org/implementations • 12 vendors certified for interoperable ebMS

solutions• Implementations from: Adobe, Sun, Fujitsu,

Sybase, BCEmergis, BEA, Cyclone Commerce, Sterling Commerce, bTrade, webMethods, TIE Commerce, Smartdraw.com and more

• Open source solutions – http://freebXML.com for messaging and registry

http://ebxml.org/implementations

http://freebxml.com/


Selection of Commercial and Government adoptions

ebXML ProjectsebXML Projects


Selected ebXML Projects• Automotive Industry moving to adopt ebXML - Feb 2004• ebXML underpins new Korean Bank and Insurance service

s - Feb 2004• US Gov DOD EMall

Embraces ebXML Messaging - Jan 2004• US Center for Disease Control (CDC) ebXML implementati

on - October, 2003

• e-Invoice system for major Metro operator - September, 2003

• ebXML Asia interoperability testing - August, 2003 • Bangkok, Thailand Project - SMEs & Nectec

- August, 2003 • ebXML and Energy Utilities Market- July, 2003

http://www.informationweek.com/story/showArticle.jhtml?articleID=18201098

http://www.ebxmlforum.org/articles/ebFor_20040201.html

http://www.ebxmlforum.org/articles/ebFor_20040201.html

http://gcn.com/23_1/news/24582-1.html



http://www.ebxml.org/case_studies/documents/casestudy_cdc_phinms.pdf

http://www.ebxml.org/case_studies/documents/casestudy_cdc_phinms.pdf

http://www.kanetti.fi/~juslem/docs/Bridging%20the%20gap.pdf










Resources

SummarySummary


Get involved in ebXML• Download the specs from www.ebxml.org• Open source resources www.freebxml.com • News and Events www.ebxmlForum.com • Join OASIS • Subscribe to ebXML-DEV mail list (link @ ebXML.org) • Review public archives of OASIS ebXML TC

work• Encourage your industry group to adopt ebXML

specifications for their standards• Specify ebXML-compliance from providers

http://www.ebxml.org/

http://www.freebxml.com/

http://www.ebxmlforum.com/


Books on ebXML

• Kotok and Webber, ebXML: the New Global Standard, New Riders, Aug 2001, http://www.ebxmlbook.com/

• Nickull, et al., Professional ebXML Foundations, Wrox Press, Nov. 2001

• Chiu, ebXML Simplified, John Wiley & Sons, June 2002

• Gibb and Damodaran, ebXML Concepts and Application, John Wiley & Sons, Nov. 2002


Acknowledgements

• This presentation would not be possible without the unstinting efforts of the OASIS BCM team members, the OASIS BPSS team and support from the EPRforum members and the ebXML community.

• These slides are a culmination of materials from over a dozen presentations and sources representing many hundreds of hours of work.

• The momentum now building is exciting and we look forward to realizing the vision here to enable better societies through the exploitation of electronic network technologies.


www.ebxml.org

Copyright OASIS, 2004 David RR Webber XML eBusiness USA [email protected] ebXML Update Toward a SOA...

Documents

Transcript of Copyright OASIS, 2004 David RR Webber XML eBusiness USA [email protected] ebXML Update Toward a SOA...