© Michael C. Rawlins Is XML Ready for Prime Time? When to use XML for Electronic Transactions for Your Business Michael C. Rawlins Rawlins EC Consulting
© Michael C. Rawlins Overview Organization types Factors –Standards –Tools –Complexity Conclusions
© Michael C. Rawlins Organization Types Early Adopters Second Wave Mainstream
© Michael C. Rawlins Early Adopters Large to medium enterprises XML programmers on staff High risk tolerance New applications Small trading communities
© Michael C. Rawlins Second Wave Primarily large to medium enterprises, but some small Hubs and first tier suppliers Programmers or technical support on staff Moderate risk tolerance New and existing applications Moderate size trading communities
© Michael C. Rawlins Mainstream All sizes, including small enterprises Small or nonexistent technical staff Low risk tolerance Core applications Large trading communities
© Michael C. Rawlins Factors
© Michael C. Rawlins Factors Why XML? Base XML Specifications XML Tools XML Business Standards Application Support On-line Marketplaces Complexity Market Timing
© Michael C. Rawlins Why: One Source, Many Uses XML Document XSL Stylesheet XSL Stylesheet DTD Printed Document Web Page Business Application
© Michael C. Rawlins XML Selling Points Separate content from presentation Applicable to many types of problems Generic tools Simplicity SME penetration
© Michael C. Rawlins XML : A Family of Specifications XML Feb 1998 –Base language –Document Type Definition (DTD) XSLT for Transformations - 11/1999 XHTML HTML in XML - 1/2000 XSL for Display - In Progress Schema for Data Definition - In Progress Several Others
© Michael C. Rawlins XML Tools Browsers –IE 5 implements draft XSL –Netscape 6.0 pre-release uses CSS with XML Parsers and Utilities –Microsoft, Sun, IBM, many others Authoring Tools - few mainstream
© Michael C. Rawlins XML Specifications and Tools Impact Specifications not yet mature Tools depend on specifications Application developers depend on tools Conclusion: –Early adopters only –Not ready for mainstream or second wave
© Michael C. Rawlins Factors: Business Standards for XML
© Michael C. Rawlins Why Business Standards? 1) JOHN SMITH 2) SMITH JOHN 3) SMITH JOHN
© Michael C. Rawlins Business Standards for using XML Frameworks –ebXML –BizTalk Cross Industry –No voluntary standards (X12, EDIFACT) yet –Proprietary - cXML, xCBL Many Vertical Industries
© Michael C. Rawlins Application Support for Business Standards Ideally built-in, off-the-shelf Currently limited to: –Proprietary approaches –Vertical industry standards Impact: Necessary for second wave and mainstream
© Michael C. Rawlins Factors: On-line Marketplaces Will impact bilateral exchanges No common business or technology profiles Issues: –Viability of ASP outsourcing –Business models –Cut out the middleman? Kill rip & read EDI Delay XML adoption?
© Michael C. Rawlins Factors: Complexity XML Internet or HTTP
© Michael C. Rawlins Complexity XML Internet XSL XSLT Schemas Xpath XLink HTTPFTP Security Packaging Internal Routing UML Meta-model Core Components Business Schema BP Model Registry & Repository
© Michael C. Rawlins XML Implementation: Naïve
© Michael C. Rawlins XML Implementation: Realistic Business Application Sender Receiver Business Application Internet XML Management, Transformation, Messaging XML
© Michael C. Rawlins Systems Complexity over Time Time Complexity
© Michael C. Rawlins Complexity of a Single Technology vs. Adoption Complexity Adoption
© Michael C. Rawlins Factors: Market Timing
© Michael C. Rawlins OSI: The Apocalypse of the Two Elephants Time Activity Research Standards Billion dollar investments Source: Dr. David Clark, head of Advanced Network Architecture research group, MITs Laboratory for Computer Science
© Michael C. Rawlins Elephants & XML Business Standards Time Activity Foundation XML Specifications XML business standards Billion dollar investments
© Michael C. Rawlins Elephants & XML? Time Activity B2B over the Internet XML Billion dollar investments
© Michael C. Rawlins Conclusions
© Michael C. Rawlins Effects on EDI Implementations Early Adopters –Phase out EDI Second Wave –Keep existing EDI –Few new applications Mainstream –Kill rip & read EDI
© Michael C. Rawlins Near Term Strategies Procurement - Prepare for migration to Marketplaces Other Applications –Retain existing EDI –3 - 5 year ROI probably OK Experiment with XML
© Michael C. Rawlins Summary by Organization Type Early Adopters –Ready for Prime Time Go Forth and XML! Second Wave –Keep them on Saturday Night Wait for standards and major trading partners Mainstream –Cable Community Access Channel Wait for shrink-wrapped XML support
© Michael C. Rawlins For More Information Mike Rawlins, Rawlins EC Consulting –XML and Emerging Approaches pages