XML - Beyond the Hype Everything you must know to succeed in implementing XML Lisa Shreve - Syscom Strategies Mike Rawlins - Rawlins EDI Consulting.

XML - Beyond the HypeEverything you must know to succeed in implementing XML

Lisa Shreve - Syscom Strategies

Mike Rawlins - Rawlins EDI Consulting

Topics

• XML in a Nutshell

• XML for Electronic Transactions

• Standards work on XML for e-Transactions

• What should you do?

XML in a Nutshell

What is XML?

• Extensible Markup Language

• A “markup” language:<i>This is Italic</i> becomes This is Italic

• Subset of ISO SGML

• More Features than HTML - Extensible

• A meta-language

XML - A Family of Recommendations

• XML 1.0 - Feb 1998– Base language– Document Type Definition (DTD)

• XSL for Display - In Progress

• XSLT 1.0 - Transformations - 11/1999

• XHTML 1.0 - HTML in XML - 1/2000

• Schema for Data Definition - In Progress

The Vision of XML

XMLDocument

XSLStylesheet

XSLStylesheet

DTD

PrintedDocument

WebPage

BusinessApplication

XML for e-Transactionsand impact on Architecture

Why XML for e-Transactions?

• Define tags for data<NAME_LAST>Rawlins</NAME_LAST>

• Many tools for software developers

• Can use mature file-oriented technologies

• XML Based Architecture

Traditional EDI Architecture

BusinessApplication

Sender Receiver

X12Translator

X12BusinessApplication

VAN

X12EXP IMP

X12Translator

An XML e-Transaction Architecture

BusinessApplication

Sender Receiver

BusinessApplication

Internet

XML XMLTransformation

XML

XML e-Transaction Conclusions

• In contrast to traditional EDI:– More pervasive– More modular– Simpler

• Transformations will still be required

• Subsystem integration via XML

• Business standards will be needed

What XML is NOT

No Content!

• No organizational infrastructure

• No established standards development

• Industries, companies, and software vendors running in all directions at once

Infinite Possibilities

1) <BUYER_NAME> JOHN SMITH </BUYER_NAME>

2) <BUYER_NAME>

<LAST> SMITH </LAST>

<FIRST> JOHN </FIRST>

</BUYER_NAME>

3) <NAME type=”BUYER">

<SURNAME BSR_CODE=”NAM-01"> SMITH </SURNAME>

<GIVEN BSR_CODE=”NAM-01"> JOHN </GIVEN>

</NAME>

EDI + XMLA match made in heaven?

Long Tags Vs. Short Tags

X12 Analysis: Short Tag Names

• Target – application-to-application interactions

• Expectation – Short tag names require less communications bandwidth

• Issue – The shorter the tag, the more cryptic, and still need a source from which to derive semantic intent

X12 Analysis: Long Tag Names

• Target - application-to-human interactions

• Expectation - with long enough tag names, user will “understand” what is expected

• Issue - How long must the tag be to describe semantic intent?

X12 Tag Length Resolution

• Core Issue – Semantic Intent?

EDI Semantic Resources

– Data Hierarchy• Table location• Loop container• Loop hierarchy• Segment• Composite• Syntax & Semantic Notes

– Implementation Guide– Implied context

X12 Conclusions

• Mechanical generation of XML tag names not a desirable solution

• Semantic tags would require considerable effort

• Many issues remain the same

• Contribute to and support the ebXML efforts

ebXML

ebXML Approach

• Adopt existing specifications where appropriate

• Utilize what worked in EDI

• Understand underlying reasons for failure in EDI

• Bridge needs for application-to-application versus application-to-human

What works in EDI?

• Modularity

• Grouping based on shared physical structure 50%

• Groupings based purpose in message 50%

• Business Document level Messaging 70%

What doesn’t work in EDI

• Dependence on Implementation guides

• “Implied” Business Process

• Content and Presentation Intertwined

• One size fits all philosophy

Where are we trying to get?

Core Data

Core Business Process

Core Business Process

Bus

ines

s S

ecto

r S

peci

fic

Con

tent

fo

r ea

ch B

P “

func

tion

”

Subclassi

ng a base

business

process, f

or a Sect

or applic

ation

Sector Business Process

Con

tent

, ide

ntif

ied

in te

rms

of

“fun

ctio

n” o

r “r

ole”

in m

essa

ge

ebXML Illustrated:

Context impact on

Core Components

Core Data

Where do you go from here?

Implementation Check List

� Trading Partner Readiness/Request

� Mature W3C Specifications

� Tools to support W3C specifications

� XML Business Standards� Technical Infrastructure� Standards Bodies

� Product Support

Near Term Strategies

• X12 still more appropriate for some things• Applications with existing standards

– Don’t wait for XML, use current EDI– 3 - 5 yr. ROI probably OK, depending on app.

• New applications may start with XML• Preparation for XML

– Target non-EDI partners– Start modeling

Web Exchanges - The Wild Card

• Mostly for procurement

• Few are integrated with business applications

• Could replace “rip & read EDI”

• What kinds of data will be exchanged?

• Will business models really change?

Summary

• You don’t get something for nothing!– Shortcutting standards increases

implementation costs– Win-win and not just cost transfer

• XML technology not ready for prime time, but rapidly evolving

Contact Information

• Lisa Shreve, Syscom Strategies, Inc.– lms@wwnet.com

• Mike Rawlins, Rawlins EDI Consulting– rawlins@metronet.com– www.metronet.com/~rawlins