Transcript OASIS & ebXML: The Building Blocks for eBusiness Web Services
ebXML: The Foundation for eBusiness Web Services
ebXML Day May 23, 2002 Patrick Gannon President & CEO, OASIS Copyright OASIS, 2002
Role of Standards
Copyright OASIS, 2002
Industry Group’s Role in Standards
• Major user
Purchasing power
• Major developer
Domain Expertise
• Major driver
Authority to strongly influence standards development Copyright OASIS, 2002
To Drive Standards Effectively, Industry Groups Need to...
1. Define Business Requirements 2. Interface with Voluntary Standards Development Organizations (VSDO) 3. Endorse standards developed through open process with market adoption Copyright OASIS, 2002
Traction SOAP v1.1
WSDL v1.1
XML W3C SOAP v1.2
W3C WSDL WG UDDI v2 UDDI.org
W3C eb MS v2 OASIS eb Reg v2 OASIS SGML ISO Proprietary JCV Consortia SDO Sanction Open Standardization Copyright OASIS, 2002
ebXML
The Global Standard for Electronic Business Copyright OASIS, 2002
ebXML Provides a Standard Way to:
• Exchange business messages • Conduct trading relationships • Communicate data in common terms • Define and register business
processes Copyright OASIS, 2002
ebXML History
• Begun as 18-month initiative in
November 1999
• Specifications delivered on schedule
in May 2001
• Developed in an open process by
more than 4500 participants representing 2000 organizations in 150 countries on virtually every continent Copyright OASIS, 2002
What does ebXML do?
• Lowers the cost/complexity of electronic business • Facilitates global trade and puts SMEs and developing nations in the picture • Expands electronic business to new and existing trading partners • Converges current and emerging XML efforts • Eliminates dependence by supporting any language, any payload, any transport
Copyright OASIS, 2002
Main ebXML concepts
• Business Processes – Defined as models, Expressed
in XML
• Business Messages – Expressed in XML • Trading Partner Agreement – Specifies parameters for
businesses to interface with each other – Expressed in XML
• Business Service Interface – Implements Trading
Partner Agreement – Expressed in XML
• Transport and Routing Layer – Moves the actual XML
data between trading partners
• Registry/Repository - Provides a “container” for
process models, vocabularies, and partner profiles.
Copyright OASIS, 2002
• 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 200
member companies plus individuals Copyright OASIS, 2002
“ebXML is our only chance this decade to establish an international e-commerce standard.”
Copyright OASIS, 2002
“ebXML provides a platform on which to build standards ... that are developed faster and yet supported by a rich set of software tools.” Copyright OASIS, 2002
“It is clear that ebXML will soon become the standard for all global trade. By implementing ebXML, GCI takes advantage of the excellent work that’s being accomplished to streamline many EDI processes and remove waste and redundancy from supply chains.” Copyright OASIS, 2002
Continuing ebXML Work
• Specifications completed May 2001; available at
www.ebxml.org
• Infrastructure work continuing at OASIS – Messaging – Collaborative Partner – Registry & Repository – Interoperability, Implementation, Conformance • Process-related work continuing at UN/CEFACT – Business Process – Core Components
Copyright OASIS, 2002
ebWS
E-Business Web Services
Copyright OASIS, 2002
What is a Web Service?
• Application to application requests and
responses over the web stack
– SSL – HTTP/SMTP/... – XML – SOAP – ebXML/UDDI • Registry • RPC and Business Messaging • all loosely coupled...
Copyright OASIS, 2002
Types of Web Services
• Simple – No side effects – Non-transactional – Context free – Sessionless, no roles – Minimal security – Call-response model – Point-to-point – Not developmentally
scalable
• Complex, e-Business – Impacts other steps – Transactional – Context sensitive conversions,
ordering of steps
– Session based, personalized – Exactly once semantics – Sophisticated security – Messaging based – Scalable
Copyright OASIS, 2002
Remote Procedure Call (RPC) based Web Services
• Implemented using a stateless session EJB. • Appears as a remote object to the client
application.
• The interaction centers around a service-
specific interface.
• Tightly coupled and resemble traditional
distributed object paradigms, such as RMI or DCOM.
• Synchronous, meaning that when a client
sends a request, it waits for a response before doing anything else. Copyright OASIS, 2002
Protocols for RPC-based Web Services
• Simple Object Access Protocol (SOAP) – W3C XML Protocol WG – SOAP v1.2 – Still in process • Web Services Description Language (WSDL) – WSDL v1.1 (IBM & MS) W3C Note Mar. 2001 – W3C WS Description WG started Jan. 2002 • Universal Description, Discovery and
Integration (UDDI)
– UDDI.org v2.0 specification June 2001
Copyright OASIS, 2002
Conversational or Message-Based Web Services
• Loosely coupled and document-driven • Client invokes a message-based Web Service
by sending it an entire document, such as a purchase order, rather than a discrete set of parameters.
• The Web Service accepts the entire document,
processes it, and may or may not return a result message.
• Promotes a looser coupling between client and
server and provide additional benefits beyond RPC-based Web Services Copyright OASIS, 2002
How does this relate to ebXML?
• Exchanges, e-markets, supply chains, etc.
need combinations of web services
– Auction, pricing, tax computation, customs,
RFP, RFQ, order management, content management
– No two exchanges will use the same
combination of services and service packages
– Custom combinations require a framework
approach
• ebXML provides the framework and many
pieces Copyright OASIS, 2002
Web Services
• Step 1: Description – WSDL – ebXML CPP Spec and ebXML Business Process Spec • Step 2: Publication and Discovery – UDDI – ebXML Registry Spec • Step 3: Invocation – SOAP over HTTP – ebXML Messaging Spec integrating SOAP, HTTP
Copyright OASIS, 2002
An Important Distinction
SOAP, UDDI, WSDL
• Developed by a
small group of vendor companies ebXML
• Developed in an
open process by more than 4500 participants representing 2000 organizations in 150 countries on virtually every continent Copyright OASIS, 2002
Continuing ebXML Work
• Specifications completed May 2001; available at
www.ebxml.org
• Infrastructure work continuing at OASIS – Messaging – Collaborative Partner – Interoperability, Implementation, Conformance – Registry & Repository • Content-related work continuing at UN/CEFACT – Business Process – Core Components
Copyright OASIS, 2002
Future Adoption of ebXML
• Manufacturing, Financial, Retail, +++ • Global Trading Web eMarketplaces • Multi-Lingual Global Transactions • Business-to-Government • Government-to-Government • …
Copyright OASIS, 2002
For more information...
•
www.ebxml.org
• www.oasis-open.org • www.ebtwg.org
Patrick Gannon President & CEO [email protected]
+1.978.667.5115 x201 (office) +1.408.242.1018 (mobile)
Copyright OASIS, 2002