XML - Beyond the Hype Everything you must know to succeed in implementing XML

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

2. Topics • XML in a Nutshell • XML for Electronic Transactions • Standards work on XML for e-Transactions • What should you do?

3. XML in a Nutshell

4. 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

5. 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

6. The Vision of XML Printed Document XSL Stylesheet XML Document Web Page XSL Stylesheet DTD Business Application

7. XML for e-Transactionsand impact on Architecture

8. 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

9. Traditional EDI Architecture

10. An XML e-Transaction Architecture

11. 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

12. What XML is NOT

13. No Content! • No organizational infrastructure • No established standards development • Industries, companies, and software vendors running in all directions at once

14. 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>

15. EDI + XMLA match made in heaven?

16. Long Tags Vs. Short Tags

17. 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

18. 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?

19. X12 Tag Length Resolution • Core Issue – Semantic Intent?

20. EDI Semantic Resources • Data Hierarchy • Table location • Loop container • Loop hierarchy • Segment • Composite • Syntax & Semantic Notes • Implementation Guide • Implied context

21. 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

22. ebXML

23. 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

24. What works in EDI? • Modularity • Grouping based on shared physical structure 50% • Groupings based purpose in message 50% • Business Document level Messaging 70%

25. What doesn’t work in EDI • Dependence on Implementation guides • “Implied” Business Process • Content and Presentation Intertwined • One size fits all philosophy

26. Where are we trying to get?

27. Core Data

28. Core Business Process

29. Content, identified in terms of “function” or “role” in message Subclassing a base business process, for a Sector application Business Sector Specific Content for each BP “function” Sector Business Process Core Data Core Business Process ebXML Illustrated:Context impact on Core Components

30. Where do you go from here?

31. Implementation Check List • Trading Partner Readiness/Request • Mature W3C Specifications • Tools to support W3C specifications • XML Business Standards • Technical Infrastructure • Standards Bodies • Product Support

32. 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

33. 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?

34. 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

35. Contact Information • Lisa Shreve, Syscom Strategies, Inc. • lms@wwnet.com • Mike Rawlins, Rawlins EDI Consulting • rawlins@metronet.com • www.metronet.com/~rawlins