XML Lessons for Master eBuilders

1

• XML Lessons for Master eBuilders
• Using XML Effectively in E-Business Architectures
• Ron Bodkin
• Chief Technology Officer
• C-bridge Internet Solutions, Inc.
• rjbodkin_at_c-bridge.com
• February 29, 2000

2
Agenda

• Background
• Sample Applications
• Organizational Impact
• Architectural Impact
• Summary
• QA

3
(No Transcript)
4
Agenda

• Background
• Sample Applications
• Organizational Impact
• Architectural Impact
• Summary
• QA

5
Chevron Retailer Alliance

• Convert XML to/from objects

• Primary data model
• Traditional layout

Database
Retailers
App Server
Web Server

• XML/HTTPS
• Application protocol
• for reliable messaging
• Extend best-fit DTD

HTTPS
Other Data
Suppliers
HTTPS
6
B2B Portal

• Schemas primary data model

• Access via XML services
• XML in database
• XML index rows

Portal
Database
Users
Web Server
App Server

• XML/HTTP
• Application protocol
• for messaging
• Standard Schemas

HTTP(S)
Directory
Partners
Web Services
7
B2B Portal Application Architecture
Business Logic
Data
Presentation
Application Services
UI Controllers
Directory
Tech Interfaces
Data Access
Display Driver
Database
Community Services
Packaged Components

• XML Interfaces
• Dynamic XML Insertion
• XSLT
• Java, JavaScript

• XML Interfaces
• Java, JavaScript

8
Agenda

• Background
• Sample Applications
• Organizational Impact
• Architectural Impact
• Summary
• QA

9
Skills

• XML logical data modeling
• Separation of Skills
• Creative design
• Scripting and transformation
• Objects for heavy lifting
• Services Packaging
• Data
• Directory
• New database approaches, skills
• Testing non-visual, variability

10
Web Services
Organization
Partner
Web Services Directory
Get Quote
XML
Internet
XML
HTTP(S) (SOAP? other?)

• Assemble and tailor capabilities quickly
• Dynamic business relationships
• Continued Expansion of Infrastructure (Bowstreet)

11
B2B Coordination

• Broad platform support
• Interest, but lack of experience
• Starter kits
• Propose and extend standards
• Quality of Experience crucial
• First efforts require close coordination

12
Agenda

• Background
• Sample Applications
• Organizational Impact
• Architectural Impact
• Summary
• QA

13
Data Schemas

• Logical Model in Schema, not ER diagram
• Rapid shift to XML Schema (XSD)
• Use of small, cooperating and competing schemas
• Co-opetition

SOAP
Meta-Frameworks (eCo, BizTalk, ...)
cXML
TIP
DSIG
Technical
ebXML
DSML
vCard
Horizontal
RosettaNet
FpML
IFX
Acord
OpenMLS
Domain
14
Data Tier
Order
Location
RootElement
ltOrdergt ltIDgt25lt/IDgt ltItemListgt ltItemgt
ltQtygt2lt/Qtygt . . .
Order ID
Date
Loc. ID
Root ID
Schema ID
Order Item
100
Schema
Order ID
Seq. No.
Qty
Prod. ID
Element
Root ID
Seq. No.
Path
Value
Product

• Alternatives
• Object/Relational
• Non-Relational

• Services
• Adapters (MoM)
• Content

Order/ID
15
Functionality OO development

• Objects encapsulate XML data (via parsers)
• Appropriate for significant computation (e.g.,
  iterating over collection)
• CRA all OO
• Portal OO for significant calculations,
  algorithms

• Mapping
• Typically simple elements all attributes -gt
  object attributes
• Typically complex elements -gt objects
• Complexity in associations
• Implementation Options
• Manual mapping (vs. binding)
• Direct construction (vs. factory or
  parameterized)
• Disassemble XML (vs. wrapper)

16
Functionality Data-oriented development

• Benefits data-centric (message conversions,
  display formatting)
• Portal primarly data-oriented
• Several Approaches to Transformation
• XSLT to convert formats (but not for everything)
• Code to manipulate XML as XML (e.g., DOM)
• Mappings and Bindings
• Rules (e.g., validation)
• Tool benefits of 4GL productivity with principled
  back-end, not just table rows

17
Presentation

• Not targeting client-side XML
• Transport mechanism of HTTP/HTTPS
• CRA incorporate objects into scripting (JSP,
  etc.)
• Portal transform and insert internal XML for
  presentation XML
• Bowstreet technology leverages XML metadata to
  support highly customized presentation and work
  flow (uniform interface to data)

18
Agenda

• Background
• Sample Applications
• Organizational Impact
• Architectural Impact
• Summary
• QA

19
Challenges

• Evolving standards
• New tools
• Vocabulary shifts
• Deeper integration
• Linking vocabularies

20
Summary

• Different Degrees of XML Use
• Impacts throughout architecture, and organization
• Provides design options
• Object-oriented
• Data-oriented
• More parameterized applications
• Standardized data
• Integration -gt Web services

21
Q A

• Email rjbodkin_at_c-bridge.com

22
Handling schema evolution and overlap

• Object-Oriented
• Dynamic (subset) interfaces
• Flexible binding from schema to object
• Methods to encapsulate data
• Parameterized objects

• Data-Oriented
• Internal representation
• XML metadata
• Filters
• Rules
• Transformations
• Bindings
• Parameterized schemas