Transcript ebXML Update, August 2004

ebXML Update
Toward a SOA Paradigm
Presentation, August 2004
NIST
Gaithersburg
Maryland
Copyright OASIS, 2004
David RR Webber
XML eBusiness
USA
[email protected]
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
Copyright OASIS, 2004
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
Copyright OASIS, 2004
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
Phase 1 completed May 2001 by
4500 participants representing
2000 organizations in 150
countries from all major
continents
• World’s largest
independent, nonprofit organization
dedicated to the
standardization of
XML applications
• More than 400
members in 26
countries
Copyright OASIS, 2004
ebXML Adoption - 2004
China –
11,000 ebMS
servers
EU – Formal
Adoption
USA – DOD
EMALL
Comparison of ebXML adoption by region, number / size / scope of projects as of December 22, 2003
Copyright OASIS, 2004
Backed by Industry Groups
The Open Healthcare Group
Copyright OASIS, 2004
A New Approach to Software Engineering
Developers
Conventional
models
Analysis
Specification
Design
Test
Maintenance
Coding
Installation
Business
Users
Procurement
Adaptation,
integration
Use
Requirements
Needs
Interactive
models
Copyright OASIS, 2004
Paradigm Shift
• 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
Copyright OASIS, 2004
Business Process Evolution
Cross-Enterprise
Service Centric
Digitization
Transaction Centric
Digitization of Simple
Task & Processes
Process
Re-Engineering
Value Co-Creation
via Customer Centric
Collaboration
Extreme Mobility
Infrastructure
Occasionally
Connected Application
Wearable Computing
Process Improvement
Copyright OASIS, 2004
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
Copyright OASIS, 2004
Deployment 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
Copyright OASIS, 2004
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?
Copyright OASIS, 2004
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?
Copyright OASIS, 2004
The Challenge of Change
• 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.
Copyright OASIS, 2004
Business Challenges
• In determining operational needs there are four
levels and areas to include:
1
– The first level is the overall operational approach to
solving large enterprise level interactions,
2
– then enterprise to small business interactions,
3
– small business to small business interactions
4
– and service solution to customer.
Copyright OASIS, 2004
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.
Copyright OASIS, 2004
How do you put this all together?
Where / Who
Where / Who
Action
How
Information
What
Action
How
Information
What
Where / Who
Event
When
Rule
Why
Event
When
Action
How
Information
What
Event
When
Rule
Why
Rule
Why
Copyright OASIS, 2004
Classic ebXML
How the pieces fit together
Copyright OASIS, 2004
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
Copyright OASIS, 2004
Initial Pieces – Defining the Interaction
Dealer
<<BinaryCollaboration>>
Bulk Buying
Collaboration
Agreement
(CPA)
Specifies
Supplier
Business
Process
Specifications
(BPSS)
Contains
Business
Transactions
Bulk Buying
Business Process
Check Product Availability
Dealer Location
Product Requirements
Submit Purchase Order
Contains
XML Messages Schema definitions (XSD) +
content processing templates
Grammars
Copyright OASIS, 2004
Classic Two-Role Business Process
• Requestor / Responder interaction model
Copyright OASIS, 2004
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)
Copyright OASIS, 2004
ebXML CPA / CPP component
PARTNER A
A GREEMENT DA TE:
Year: 2003
CPP
Month: 06
ebXML
Time: 01:01:00
Day: 09
(propose d / acce pte d/
pe nding)
CPA Status: proposed
Party Name: C ompany A
Web site: http://ourwebsite.com
Party ID: 123456
ID type: DUNS
Alias: AAA
Role: initiator
Contact EMail: [email protected]
Agreement Ref: autotech-bods-01
Preferred standard:
Reference URL: http://ourwebsite.com/cpa/
OAG BODs
Participant
Information
Until: 2004
Process Name: Automotive assembly supply
Process Script URL: http://mywebsite.com/bpss/autoasm01.xml
Description: This is an Automotive Supplier Agreement
using OAG BOD messages
MESSAGE HANDLING CONFIGURATION:
SR
Service Mode: systemtest
End Point URL: http://127.0.0.1:8080/ebMS-MS/msh
Signature Keyname: Initiator
Message handling
Configurations
Library
MSH
ACK
ALL
NO ACK
Place the
interchange
configuration
youMSG
want right
here
PER
SSL
SIGN
RESPND
Messaging
preferences
and
configuration
SEND
SEND
Item Name: default
SEND
Item Name: Sending Message
Shortname: Msg_Out
Action Send Msg: Out_XML
Collaboration
Details
Action Respond Msg:
Rspd_XML
Message
exchange
details
RECEIVE
RECEIVE
Item Name: default
RECEIVE
Item Name: Received Message
Shortname: Msg_In
Action Respond Msg:
C onfirm_XML
Action Recv Msg: In_XML
Copyright OASIS, 2004
Classic ebXML example
BPSS implicit
from exchange flow
Each partner
has ebMS
exchange
system
SENDING
RECEIVING
Partner A
Partner B
SOAP
messaging
INTERNET
Requester
Documents
3
re
ebXM L
enveloping
and
delivery
Exchange
Transactions
ig
u
Exchange
Transactions
nf
re s
ebXML
ebMS
ebXML
ebMS
4
2
XML schem a
n fi
gu
Delivery
Queue
Partner A 5
Business
Application(s)
Partner
CPA(s)
co
1
Partner
CPA(s)
s
6
6
co
4
Delivery
Queue
Partner B
Business
Application(s)
1
Responder
Documents
2
5
XML schem a
3
Copyright OASIS, 2004
Classic ebXML example + Registry
Registry
provides
common
reference
point
User Profiles
CPA lookup
Docum ent Definitions
Schem a XSD
ebXML
Registry
(optional)
BPSS implicit
from exchange flow
Client User
Interface
3
SENDING
RECEIVING
Partner A
Partner B
SOAP
messaging
INTERNET
Requester
Documents
re
Exchange
Transactions
ig
u
ebXM L
enveloping
and
delivery
nf
Exchange
Transactions
ebXML
ebMS
ebXML
ebMS
4
2
XML schem a
re s
4
Delivery
Queue
Delivery
Queue
Partner A
Business
Application(s)
5
Partner
CPA(s)
co
1
Partner
CPA(s)
n fi
gu
s
6
6
co
Partner B
Business
Application(s)
1
Responder
Documents
2
5
XML schem a
Copyright OASIS, 2004
Enhanced ebXML
Extending the core architecture
Copyright OASIS, 2004
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 C
Partner A
Partner B
co
c o m pl
l l a ete
b o sc
ra
t io enar
i
n
oo
Partner D
Partner F
Partner G
Partner F
f
Partner E
Partner G
1
ebXML
BPSS
Model and
Scenario
Copyright OASIS, 2004
Success
RespondCreditStatus
conditio
n
OK
Action
To Role
Action
Action
RequestPriceQuote
buyer
To Role
Failure
noSellersResponded
condition
invalid
Success
respondPriceQuotes
conditio
n
OK
Marketplace
Buying Agent
To Role
Action
To Role
Action
To Role
Action
To Role
Producer
invalid
RequestPriceQuote
trading service
Success
respondPriceQuote
conditio
n
OK
DrawDownCredit
trading service
AcceptPriceQuote
trading service
ignorePriceQuote
trading service
ReplenishCredit
trading service
Seller Credit Service
creditStatusUnknown
Winning Producer
Failure
condition
Multiparty Model
with BPSS
Losing
Producers
buyer
Seller Credit Service
checkBuyersCredit
Credit Bureau
Action
To Role
Copyright OASIS, 2004
Implementation Through Component Layers
Business Agreement
Languages (RINs)
Collaboration Profile
Agreement (CPA)
Choreography &
Coordination Lang.
(BPSS)
Context Driven
Information
Exchanges (CAM)
Semantic Registry
Copyright OASIS, 2004
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)
Copyright OASIS, 2004
Enhanced ebXML
1
ebXML
BPSS
Model and
Scenario
EXCHANGE
PACKAGES
Client User
Interface
User Profiles
CPA details
Docum ent Definitions
Schem a XSD
CAM tem plates
Context Instances
ebXML
Registry
(optional)
BPSS script
2
Partner
CPAs
1
BPSS
Script
Context
Variables /
Rules
Complete Collaboration
Details Drive each ebMS
4
3
Content
Management
Services
Vocabulary
Management
Services
XML schem a
Participating
Documents
CAM
templates
5
Exchange
Transactions
ebXML
ebMS
Each
partner
has
exchange
system
jCAM
7
Partner
Business
Application(s)
Exchange
Transactions
ebXM L
enveloping and
delivery
9
Web service
(optional)
8
6
Delivery
Queue
WSDL
interface(s)
INTERNET
SOAP
messaging
context + rules
templates
Copyright OASIS, 2004
Modelling the Business Process
• from the model –generates actual BPSS as XML instructions
Copyright OASIS, 2004
Deterministic linking of BPM to layers
• Each step consists of deterministic action and outcomes
Group
Possible
Responses
Transport
layer
return
settings
Configure outcomes
and flow control
Select associated responding document
Copyright OASIS, 2004
Align BP steps to information systems
DealerLocator
DealerLocator
Map To
AvailableVehicle Activity
Map To
DealerLocation Activity
DealerLocator
e.g., Map DealerLocation
Activity to the DealerLocator
Web service
Map To
VehicleHistory Activity
PurchaseRequest Activity
Map To
PurchaseApproval Activity
DealerLocator
Map To
Business Analysts
map B2B
Transactions to the
services available in
Back-end Service
Oriented
Architecture (SOA)
[Business Error]
Copyright OASIS, 2004
Configure the Business Exchange Rules
Logical business transaction can have more than one structure layout
BPSS
Step
transaction
XML
instance
structure(s)
template
Content
Assembly
Template
can add inline rules directly
into structure
Simple Declarative Statements
Business context rules
+
Content Reference rules
+
Data Validation rules
+
External Mapping rules
makeOptional()
excludeTree()
item type="noun"
name="Agency/@AgencyID"
UIDReference="ukt000910"
<conditional
expression="'//SupplierID' and
lookup(value,'SGIRWSDL:supp
lierID_check')"
<MapRule output="type"
input="Sales/Company/Year
/Qtr/Product@type"/>
Copyright OASIS, 2004
Understanding about Context
• 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 1568
1 : the parts of a discourse that surround a word or passage and can throw light on its meaning
2 : the interrelated conditions in which something exists or occurs
Copyright OASIS, 2004
Aligning the Concepts – Core Components
UBL - work on supply chain messaging using CCTS
Context
Domain: Matl Mgmt
Industry: Auto
Regulatory: Safety
Create Long Term
Contract
•Ship Notice
ProdId
Change Lvl
Forecast Component
Requirements
Part Number
Send Planning Document
Customer
Container
Supplier
Place Order
Ship Materials
Serialized ID
Ship’d Qty
Arrange Payment
Copyright OASIS, 2004
Generating a Context Instance
• Add parameter value rules and document value rules
Configure Context
Instance header
Create a rule and
set a value
Check a document
and change a BPSS
parameter
Copyright OASIS, 2004
Moving to deployment
Business
agreement
Drives
document
exchanges
Copyright OASIS, 2004
ebXML component drilldown
Some extended details on each piece
Copyright OASIS, 2004
ebXML example interchange integration
Apps
ebXML
SOAP
ebXML
MSH
Internet
Services
CPA
ebXML
Proces
s
Server
Business
Process
Collaboratio
n
Legac
y
Apps
Business
App’
Services
Internal
Firewall
SOA Layer
ebXML
MSH
DMZ
Internet
B2B—
Tradin
g
Partne
r
Business
App’
Services
DB
Orchestration Services
Application
Server(s)
COTS
Apps
Legac
y
Apps
BPSS
Copyright OASIS, 2004
Messaging Layers
Message Services
Application Arena
ebXML
B2B Market, Global
Multi-enterprise
Big A2A
Integrated App
Families
Typical access via:
ebXML
SOAP/HTTP
(JAX-M for ebXML)
ebXML
SOAP/HTTP
(JAX-M for WS-Routing)
Web Services
for XML Message
Web Services
WS
Small A2A
for RPC
Integrated Apps
Homogeneou
s Application
Reusable
Components
Tighte
rLimited
SOAP/HTTP
(JAX-RPC)
WS
ORB
(RMI/IIOP)
WS
Granularity
Coupling
Security
Looser
Extensive
Copyright OASIS, 2004
ebXML Message Structure
Communication Protocol Envelope (HTTP, SMTP, etc.)
SOAP Messages with Attachments MIME Envelope
MIME Part
Message Package
Header Container
SOAP-ENV:Envelope
SOAP-ENV:Header
eb:MessageHeader
ebXML Header
Information
eb:TraceHeaderList
Other:etc…
SOAP-ENV:Body
eb:Manifest
eb:etc…
ebXML Message
Service Handler
control data
Other:etc…
MIME Part
Payload
Payload
Container(s)
Copyright OASIS, 2004
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
Copyright OASIS, 2004
WSDL and ebXML CPA / BPSS
WSDL provides:
 Service name
 Service parameters
 Endpoint for invocation
WSDL identifies:
 Business processes
article comparing messaging
technologies at ebXMLForum
ebXML CPA provides:
 Service name and parameters
 Endpoint for invocation
 Role of an organization in the
context of a service
 Failure scenarios
ebXML BP identifies




Business processes
Roles an organization must play
Messages being exchanged
Error handling
Copyright OASIS, 2004
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
Soap
Life Cycle
Manager
Query
Manager
Authentication Security
Persistence
Manager
Authorization Manager
Repository
Database with RIM
Registry Organization Extrinsic
Objects
Objects
BPSS, CPA, CC
http://registry.oasis-open.org
Copyright OASIS, 2004
Storing the Enterprise Artifacts
Collaboration Partner
Agreements- CPA
Collaboration Partner
Profiles - CPP
5
Contract
4
BP Specification
Workflow
Process
XForms
3
Specifications
Schema
Messages
Content Assembly
Mechanism - CAM
2
Motivation
Rules
1
Data/Codes
Nouns
Core
Components
Source: BCM Lubash Pyramid
Time
Events
Services/Functions
Verbs
People
Roles
Network
MSH/SOAP
Transport
Routing, Packaging
WSDL
Copyright OASIS, 2004
Registry Roles
“A semantic registry is the key foundation
block upon which global electronic
business exchanges will be built”.
Information Engine
Business
Analyst
Administration
Distribution
Web Interface
Interchange
Program Level
Semantics
Software
Developers
XML
Information
Profiles
Industry Business Standards
Registry Protocol Standards
ebXML, ISO11179, OASIS,
OAGi, RosettaNet, UBL, UDEF
Copyright OASIS, 2004
Capturing Noun Semantics
Can use Designer
Tools to automatically
generate from XSD model
• Draft layout for
storing noun
details in registry
See: OASIS Registry Semantic Content
Management sub-committee work (SCM SC)
Copyright OASIS, 2004
Automating Trading Partner Setup Example
ERP
System
ebXML Registry
ERP to
Accounting PO
Trading
Partner Map
Schema
& Map
ERP PO
Accounting
System
XML PO
ERP XML
Purchase Order
ebXML Server
ebXML Server
Custom
XML Invoice
Exchange Profiles to
quickly configure relationship
ebXML Service
Layer
Custom Invoice
Custom LOB
Copyright OASIS, 2004
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
Copyright OASIS, 2004
What’s next?
Front-Office EPR work
Toward a complete end-to-end solution
including services
http://eprforum.org
Copyright OASIS, 2004
EPR Uses Workcards as a GUI Metaphor
Participant and
Context
Based
Architecture
Participant can be:
1. Traditional User
2. Machine or Device acting
as a Proxy for a User
Environmental Context dynamically modifies
Declarative Display Metaphor
Copyright OASIS, 2004
EPR Folder’s Core Components
Service Portals
SERVICE PART
Object Models Organizing and Managing Tasks
Single Sign-On (PKI)
portal:
(Security Domains)
Role
Service
+
UserID
EPR Folder Container:
Arbeidsmappe
Working
Folder
Arbeidsmappe
( Opprettes når ny bruker eller ny process )
Contain( everything
a user
needs in
work.
Opprettes når
ny bruker
eller
ny process )
All Working Folders are divided into phases
Related to progress.
Steering card
phase
Steering Cards:
Dokumentkort
Dokumentkort
Dokumentkort
Dokumentkort
Styrertilgang
tilgangtiltil
blankett-ogog Workflow card
Document
card
Dokumentkort
Styrer
blankettStyrer
tilgang
til
blankettog
dokumentmaler samt arkiverte
Styrer
tilgangtil
tilblankettblankettdokumentmaler
samtarkiverte
arkiverte
Handles
all
the
Support to adm. working
Styrer
tilgang
ogog
dokumentmaler
samt
Dokumenter.
dokumentmaler
samt
arkiverte
Dokumenter.
DocumentsDokumenter.
in samt
the folder.
process in the business logic.
dokumentmaler
arkiverte
Dokumenter.
(Often
RuleControlled ProcessFlow)
WS
linking
Dokumenter.
Dokumentkort
Dokumentkort
Dokumentkort
Dokumentkort
Styrertilgang
tilgang
tilblankettblankett-ogog
Job
card
Dokumentkort
Styrer
tilblankettStyrer
tilgang
til
dokumentmaler
samt arkiverte
Styrer
tilgang til blankettogog
dokumentmaler
samtarkiverte
arkiverte
(Service
Styrer
tilgang tilcard)
blankettog
dokumentmaler
samt
Dokumenter.
dokumentmaler
samt
arkiverte
Dokumenter.
dokumentmaler
samt arkiverte
Def.
of physical
Instructions
Dokumenter.
Dokumenter.
Dokumenter.
in a working
process.
Includes inspection and reports.
Steering Card functions
Copyright OASIS, 2004
Workcards adapt to user environment
Networked devices
Copyright OASIS, 2004
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
Copyright OASIS, 2004
Solution Architecture
Templates Capture Business
Process Context details
References
Creates
Generate – XML artifacts
that drive the
implementation components
Portal – user interface
dynamically configured
Runs
Reference – Domain
Ontology and
Semantic Information
Technology –
Implementation
components
Tracks
Integration – legacy
system interactions
Enables
Processes – state
management,
linking and switching
Copyright OASIS, 2004
Integrating EPR applications together
eHealth
epr
templates
eHealthcare
eprApl
eGovernment
eprApl
eGov
epr
templates
eprXML engine
General
epr
templates
Web services
Legacy systems
BCM switch/link
CAM processor
+ ebXML
Public systems
Communication
infrastructures
XML
documents
(content)
XML
SOA - Process and
Exchange
rules
Blue: ePROBE
Yellow: others
Copyright OASIS, 2004
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
Copyright OASIS, 2004
ebXML in the marketplace
Vendors Products
Copyright OASIS, 2004
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
Copyright OASIS, 2004
ebXML Projects
Selection of Commercial and
Government adoptions
Copyright OASIS, 2004
Selected ebXML Projects
• Automotive Industry moving to adopt ebXML - Feb 2004
• ebXML underpins new Korean Bank and Insurance
services - Feb 2004
• US Gov DOD EMall Embraces ebXML Messaging - Jan
2004
• US Center for Disease Control (CDC) ebXML
implementation - 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
Copyright OASIS, 2004
Summary
Resources
Copyright OASIS, 2004
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
Copyright OASIS, 2004
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
Copyright OASIS, 2004
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.
Copyright OASIS, 2004
www.ebxml.org
Copyright OASIS, 2004