XML A Platform for E-Business

1
XML A Platform for E-Business
XML

• XML Business Solutions World
• Madrid, 20 May 2003
• Dale Waldt
• OASIS, Program Development / XML.org
• dale.waldt_at_oasis-open.org
• aXtive Minds, Inc., Senior Consultant
• dale_at_aXtiveminds.com

2
Who am I?

• Currently
• aXtive Minds, Inc., President / Senior Consultant
• OASIS, Program Development / XML.org
• Previously
• RIA / Thomson Publishing, VP Product Technology

3
Agenda

• Problems with content data
• What is XML?
• XML-based e-business platforms
• XML-enabled e-business case studies

4
Problems with Content Data

• Information Silos
• Information locked in on user application
• Multiple Data Interchange formats
• Systems / departments / partners can't share data
  easily
• Diverse Data Source Formats
• Cost of collecting / integrating data high
• Content Management Reuse
• Cost of new products / uses / delivery channels
  high
• System Integration Challenges
• Requires expensive middle-ware / data
  manipulation
• Longevity of Data
• Legacy systems hard / expensive to integrate /
  replace

5
What is XML?

• A way of making data
• Portable reusable
• Structured unambiguous
• Long lasting valuable
• W3C Specification based on SGML (itself an ISO
  Standards)
• Language to describe rules for enforce document
  structure
• Separates Structure from Presentation
• Language for defining application-specific
  vocabularies

6
Information May Consist of 3 Things
7
XML tells us "What" not "How"

• XML describes what data "is" not what you want
  done to it
• Separates "structure naming" from "processing
  format"

lttable border'1'gt lttrgt lttdgtMakelt/tdgt
lttdgtHPlt/tdgt lt/trgt lttrgt lttdgtModellt/tdgt
lttdgtVectralt/tdgt lt/trgt lttrgt
lttdgtMemorylt/tdgtlttdgt256 Mblt/tdgt lt/trgt lttrgt
lttdgtNetworkinglt/tdgt lttdgtEthernet
10/100lt/tdgt lt/trgt lt/tablegt
ltcomputer make'HP' model'Vectra'gt ltmemory
megabytes'256'/gt ltnetworkgt ltethernet
type'ISA' speed'10/100' /gt lt/networkgt lt/comput
ergt
XML
HTML
8
...Then Transforming as Needed

• Transformation of content using XSLT Rules
• How to get from source format to delivery format

DTD / Schema
XML Doc
External Delivery Data Format - HTML
Internal Source Data Format - XML
9
Major Benefits of XML

• Information is described in a way understood by
  different types of systems
• Documents messages exchanged regardless of
  different environments
• Leverages investment in legacy systems
• Data easily reorganized transformed into
  different delivery formats
• Metadata can be included with content
• Re-keying effort errors are reduced
• Business process changes enabled with less impact

10
The Complete XML Application Picture
HORIZONTAL WEB SERVICES
PROCESS/CORE COMPONENTS
MESSAGING (e.g. SOAP, ebXML TRP)
FOUNDATION (e.g. XML, Schema, XSLT)
CORE (e.g. TCP/IP, HTTP)
11
Industry Standards Vocabularies

• Rosetta Net Computer supply chain
• DocBook - Computer documentation
• XBRL Financial records reporting
• LegalXML
• E-Gov
• HR-XML
• Tax XML
• Many more

http//www.xml.org
12
So, What is a Document?

• Content Management / Publishing
• Articles, treatises, announcements, manuals,
  laws, etc.
• Data Interchange / Information Supply Chain
• Product data, price lists, directories, purchase
  orders, etc.
• Localized Software Integration / APIs
• Records, state info, commands, etc.
• Enterprise Application Integration (EAI)
• Records, RPC, content, directories, etc.
• Web Services / e-Business
• Messages, transactions, requests, RPCs, etc.
• Knowledge Management
• Artifacts, actions, agent info, etc.

13
Classic XML Publishing / CMS Process

• Data created once can be reused or repurposed in
  multiple delivery formats
• Avoids re-keying / ongoing conversion costs
  errors
• Requires transformation process to feed each
  delivery channel
• Enables adoption of new delivery technology
• Frees delivery channels from schedule dependency
  constraints

14
Emerging Web/SW Integration Process
15
The eBusiness Tidal Wave
Internet Based Content Delivery

16
The eBusiness Technologies
Sales and Distribution B2B iMarketPlaces /
Hubs ASPs (Application Service Provider)
XML
B2C Integration
Information Mining
Web Services
Directory Services
17
Web-Based E-Business Platforms

• First there was EDI (Electronic data Interchange)
• Facilitates global electronic trade
• ANSI X12 standards used in North America
• UN EDIFACT (EDI for Administration, Commerce
  Transport) used in Europe and elsewhere outside
  North America
• Purchase orders, invoices, wire transfers,
  receipts, etc.
• Long-term, high volume trade between established
  partners
• Expensive technology with high cost-of-entry
• Inconsistent formats
• Only practical for large organizations

Fortune 1000
Small to Medium Enterprises (SMEs)
95
2
18
Web-Based E-Business Platforms

• Then Came Basic Web e-Business
• SSL with encryption
• Standard Web protocols
• Low cost interface
• Expensive custom or proprietary
• application platforms
• Human initiated events

19
Web-Based E-Business Platforms

• Now We Have Web Services

• Today
• Simple
• Integrating software
• Point-to-point
• Non-transactional
• Session-less, no roles, no context
• Minimal security
• Not developmentally scalable

• Tomorrow
• Complex
• Address integration processes
• Conversation / message based
• Transactional
• Session based, personalized, impacts other steps
• Sophisticated security
• Scalable

20
Web-Based E-Business Platforms

• Today's Web Services Standards
• Small Object Access Protocol (SOAP)
• XML-base lightweight protocol for information
  exchange
• W3C XML Protocol WG SOAP v1.2
• Still in process
• Web Services Description Language (WSDL)
• XML Format for describing Web Services as end
  points acting on messages containing either
  documents or procedural calls
• WSDL v1.1 (IBM MS) W3C Note Mar. 2001
• W3C WS Description WG started Jan. 2002
• Universal Description, Discovery Integration
  (UDDI)
• Facilitates Describing/Discovering Services
  Business
• Registration of Business Identity Information
• UDDI.org v2.0 specification June 2001
• OASIS Member Section August 2002
• XML
• HTTP, DNS MIME

21
Web-Based E-Business Platforms

• Tomorrow's Web Services
• ebXML (electronic business XML)
• Open framework for global e-commerce
• Replaces (but is compatible with) EDI Web
  Services
• Ratified May 2001 / Proof of Concept
  Demonstration conducted with more than 20
  participating organizations
• Built on XML and other open standards
• XML
• UDDI
• WSDL
• SOAP
• HTTP, MIME.
• Extends with New Specifications
• Business Process
• Enhanced Registry Model Services
• Trading Partner Collaboration (CPPA)
• Enhanced Messaging Services

22
Example Scenario
23
ebXML Standards Open Adopted
Traction
Proprietary
JCV
Consortia
SDO
Sanction
24
UDDI ebXML Registry Spec

• UDDI
• Publish and discover web services
• Basic identification
• Industry classification
• Technical capabilities

• ebXML Registry Spec
• Publish and discover web services
• Basic identification
• Industry classification
• Technical capabilities
• Search capability
• Retrieval of business process, business document,
  and business profile objects in repositories

25
SOAP ebXML Messaging Services spec

• SOAP
• Flexible message payloads
• Point-to-point messaging
• Basic security
• Basic reliability
• Depends on proprietary functions

• ebXML MS Spec
• Flexible message payloads
• P2P conversational / transactional messaging
• Sophisticated security
• Sophisticated reliability
• Integrated with open security, authentication,
  process, and related standards / functions

26
WSDL ebXML CPP/CPA Spec

• WSDL
• Describe the web service
• Information about service name and parameters,
  and how to invoke

• ebXML CPP/CPA Spec
• Describe the web service
• Information about service name and parameters,
  and how to invoke
• Information about organizations role in service
  context
• Error handling and failure scenarios

27
E-Business Platforms Compared
28
So, what doesnt ebXML include?

• DTDs or schemas for specific business documents
  (e.g. invoices, POs)
• Company-specific or industry-specific
  implementations

29
Support for ebXML is Growing

30
Continuing ebXML Work

• Infrastructure work continuing at OASIS
  www.oasis-open.org
• Messaging
• Collaborative Partner
• Registry Repository
• Interoperability, Implementation, Conformance
• http//oasis-open.org
• http//xml.org
• Content-related work continuing at UN/CEFACT
• Business Process
• Core Components
• http//ebxml.org

31
Case Study 1 MegaCorpDescription
MegaCorp

• Large manufacturing company
• Plants offices all over the world
• Executed a growth plan involving acquisitions
• CEO stated a new goal for the year to reduce
  overall IT costs
• Eliminate / integrate diverse legacy systems
• Consolidate Payroll Benefits Information
  Systems
• Commercial software products
• Will satisfy regional requirements
• Don't operate or store data consistently
• Don't interoperate as well as needed

32
Case Study 1 - MegaCorpCurrent Systems
MegaCorp
Megacorp Steel Seoul
Megacorp Electronics Singapore
Megacorp Main Office San Francisco
Payroll
Payroll
HR
HR
Checks
Checks
Checks
Taxes
Megacorp Transport Memphis
Megacorp Air Cargo Seattle
Payroll
Keying
HR
Payroll
HR
Payroll
HR
Checks
Checks
Checks
Taxes
Megacorp Oil Kuala Lumpur
Megacorp Cement Sydney
Megacorp Fishing Anchorage
Payroll
HR
Payroll
Payroll
HR
HR
Checks
Checks
Checks
Taxes
Taxes
Taxes
33
Case Study 1 - MegaCorpNew Systems
MegaCorp
34
Case Study 1 - MegaCorpObservations
MegaCorp

• Benefits from XML-Enabled Process
• Reduced time / cost related to data exchange
  reuse
• Reduced time / cost for payroll reports
  payments
• Reduction in platform support maintenance costs
• Obstacles to Implementation
• Changes to subsidiary systems business
  processes
• Elimination of roles in some subsidiaries
• Different business sectors have different
• Processes
• Regulations Outside Requirements
• Cultures
• Difficult to transition live system

35
Case Study 2 Clicks MortarDescription
CM

• Retailer with regional franchise retail outlets
• CEO wants a Web-based direct selling channel to
  expand into other markets
• Manufacturing, inventory fulfillment is
  outsourced
• Integrated product database requirements
• Product information with technical specs from
  manufacturers
• Marketing pricing "tear sheets" from the
  marketing department
• Feeds "Featured Products" area on the Web site
• Feeds email service that pushes information to
  customers

36
Case Study 2 Clicks MortarCurrent Process
CM
37
Case Study 2 Clicks MortarNew Process
CM
38
Case Study 2 Clicks Mortar Observations
CM

• Benefits from XML-Enabled Process
• Reduced time / cost related to supply chain info
• Reduced time / cost to produce catalog
• May also be applied to order entry / fulfillment
  systems
• Obstacles to Implementation
• Requires changes to suppliers systems
• Catalog Department may resist changes that affect
  their processes

39
Summary

• XML enables efficient business solutions
• XML-based e-business platforms enable efficient
  e-business solutions
• Web Services exist today and are becoming more
  sophisticated to meet business challenges