888-745-3748

 XML Background
 XML/EDI
 XML/EDI Initiatives
 XML/EDI Tools
 XML/EDI Vision
 Next Steps

Background
 Proprietary Markup Languages
 Word Processors
 Standard Generalized Markup Language (SGML)
 ISO 8879 - defines a generic document definition and data markup language
 Separate structure & content
 Hypertext Markup Language (HTML)
 Application of SGML (HTML DTD)
 Predefined set of tags
 Defines the format of a document

Background
 Extensible Markup Language (XML)
 Describes a class of data objects called XML documents which are stored on computers & partially describes the behavior of programs which process these objects
 Restricted Form of SGML
– 80% of functionality
– 20% of complexity
 XML provides a mechanism to impose constraints on the storage layout & logical structure of documents

Background
 Create your own tags to describe content
 Easy to create structured documents
 To describe, deliver, & exchange structured data between applications
 Hardware/software independent
 More powerful than HTML
 Less complicated than SGML

Background
 More meaningful searches
 Separation of content and format
 Development of flexible web applications
 Open standards
 Flexible format for different use
 Wire format for web delivery
 Transfer format for sharing data
 Persistent data format for disk storage

Background
 XML family of standards
 XML
 XML Link Language (XLL)
 XML Stylesheet Language (XSL)
 Document Object Model (DOM)
 XML Query Language (XML-QL/XQL)
 Namespaces
 Document Content Description (DCD)
 XML Repositories

Background
 Presentation-Oriented Publishing (POP)
 POP documents are chiefly written by humans for other humans to read
 Browser - Browser
 Message-Oriented Middleware
 MOM documents are documents mainly generated from computer systems for use by other computer systems
 Application to Application
 Application to Human/Human to Application

Background
 Consist of character data and markup
 Allowed markup
 Elements
 Entity references
 Comments
 Processing instructions
 Marked sections
 Document type declarations

Background
Prolog
Document Type Declaration
Root Element
Element
Element
Epilog

Background
Well Formed
XML Documents
Valid XML Documents

Background
<?xml version=“1.0”>
<!-- Purchase Order Example -->
<PurchaseOrder>
<Header>
<PONumber>123456</PONumber)
<PODate>12/3/1998</PODate>
</Header>
<Detail>
<POLine>………..</POLine>
<POLine>………..</POLine>
</Detail>
<Summary>…………</Summary>
</PurchaseOrder>

Background
 Intelligent agents
 Structured records
 Objects with methods and data
 Metacontent for Web sites
 Query results
 Graphical user interface
 Persistent storage formats
 Online procedures documentation
 Interactive parts catalogs
 Electronic service manuals
 Electronic Data Interchange

XML/EDI
 To deliver unambiguous and durable business transactions via electronic means
 Utilize existing systems and processes
 Protect investment in traditional EC/EDI
 Provide a migration path to next generation
XML/EDI systems
 Use existing business processes as implemented
 Facilitate direct interoperation in an open environment

XML/EDI

XML/EDI

XML/EDI

XML/EDI
Your
Customer
Purchasing
Receiving
Financial
Request for Quote (840)
Technical Specifications (841)
Response to RFQ (843)
Purchase Order (850)
You
P.O. Acknowledgment (855)
Purchase Order Change (860)
P.O. Change Acknowledgment (865)
Invoice (810)/Advance Ship Notice (856)
Sales
Order
Entry
FRT Bill (210)
Receiving Advice (861)
Shipping
Payment Order/Remittance Advice (820)
Financial
Electronic Funds Transfer

XML/EDI
 Data Entry/Data Collection
 Application Extract
 Outbound EDI Processing
 Communications Processing
 Inbound EDI Processing
 Application Import
 Error Handling

XML/EDI
 Company A extracts PO data from purchasing system
 UDF
 XML Document(s)/XML Objects
 Map extracted PO data to XML/EDI or EDI format
 Validate XML/EDI against repository DTD/DCD IC
 Transmit XML/EDI to Company B
 Via VAN
 Via Internet
– http, ftp, smtp

XML/EDI
 Company B receives/retrieves XML/EDI PO
 Access repository
 Appropriate XSL stylesheet(s) for processing
 DTD
 DCD
 Process XML/EDI PO
 Import into order entry system
 Print order

XML/EDI
 XML bridges the gap between traditional EDI &
Web-based applications
 Most of software industry has embraced XML
 Microsoft, IBM, Netscape, Oracle, SAP, etc.
 XML could make EC/EDI more available to SMEs
& other non-traditional EDI users

XML/EDI
 Data Typing
 Currently XML has no facility to show data types
 Exposed Semantics
 Currently XML has no method to show relationships between data elements & other structures
 Repeat Counts
 Currently XML has no method to designate segment or loop counts
 Minimum/Maximum Lengths
 Currently XML has no method to specify minimum and maximum lengths

XML/EDI
N1*SH*ABC Systems*1*1234567*07*SH
<N1>
<EntityIDCode>SH</EntityIDCode>
<Name>ABC Systems</Name>
<IDCodeQual>1</IDCodeQual>
<IDCode>1234567</IDCode>
<EntityRelationCode>07</EntityRelationCode>
<EntityIDCode>SH</EntityIDCode>
</N1>

XML/EDI
N1*SH*ABC Systems*1*1234567*07*SH
<N1>
<N101>SH</N101>
<N102>ABC Systems</N102>
<N103>1</N103>
<N104>1234567</N104>
<N105>07</N105>
<N106>SH</N106>
</N1>

XML/EDI
N1*SH*ABC Systems*1*1234567*07*SH
<N1>
<X0098>SH</X0098>
<X0093>ABC Systems</X0093>
<X0066>1</X0066>
<X0067>1234567</X0067>
<X0706>07</X0706>
<X0098>SH</X0098>
</N1>

XML/EDI
N1*SH*ABC Systems*1*1234567*07*SH
<Set850-1-310>
<SegN1-01>SH</SegN1-01>
<SegN1-02>ABC Systems</SegN1-02>
<SegN1-03>1</SegN1-03>
<SegN1-04>1234567</SegN1-04>
<SegN1-05>07</SegN1-05>
<SegN1-06>SH</SegN1-06>
</Set850-1-310>

XML/EDI
N1*SH*ABC Systems*1*1234567*07*SH
<N1 EntityID=“SH”>
<Name>ABC Systems</Name>
<IDCode Qual=“1”>1234567</IDCode>
<EntityIDCode Relation=“07>SH</EntityIDCode>
</N1>

XML/EDI Initiatives
 ANSI ASC X12
 UN/EDIFACT
 XML/EDI Group
 CommerceNet
 W3C
 Graphics Communications Association (GCA)
 Software Vendors

XML/EDI Initiatives

“ASC X12 on the Brink of Completing X12
Technical Report” - 3/11/99
 Final stages of X12-XML methodology
 X12C Approval June 99/Publication in October 99
 Goals
 Define a method to expose the semantic content of
X12 standards as well-formed XML documents
 Ensure X12/XML is interoperable with native X12 syntax
 Future Efforts
 Validation, Acknowledgments, & Error Handling

XML/EDI Initiatives
 2/98 Meeting - Los Angeles
 Informational Session on XML/EDI
 6/98 Meeting - Columbus
 Ad Hoc XML/EDI Committee
 8/98
 Preliminary Findings & Recommendations on the
Representation of X12 Data Elements and Structures in XML
 10/98 Meeting - Miami
 Near & Long Term Goals
 X12C TG3

XML/EDI Initiatives
 2/99 Meeting - Dallas
 Development of X12/XML Matrix
 Objectives for Technical Report
 Proposals
 Approach Proposals
 Freeform Attribute Identified
 Discrete Field Group by Semantic Relationship
 Promotional Multi-Part
 Freeform Attribute Identified REFID Tags
 A Methodology for Semantic Tags

XML/EDI Initiatives
 European XML/EDI Pilot Project
 Will test XML for EDI between business & other organizations
 SIMPL-EDI DTDs
– Orders
– Invoices
– Despatch Advices
– Value Chain Planning & Performance Reports
– International Payment Orders
– Order Responses
 http://www.cenorm.be/isss/workshop/ec/xmledi/Isssxml.html

XML/EDI Initiatives
 XML/EDI Repository Proposal
 Global repository for XML tags
 Functionality of Repository
– Creating/Requesting Tags
– Browsing/Searching for Tags
– Downloading a subset of repository
– Automatic Update by Subscription

XML/EDI Initiatives
 eCo Framework Project
 Goal is to develop a common framework for interoperability among XML-based application standards and key EC environments
 Focus Areas
– Architectural Framework
– Interoperable Transaction Framework
– Content Names and Definitions
– Common Software Framework
– eRegistry Submission Process

XML/EDI Initiatives
 The Center for the Study of EC in the Daniel's
College of Business at the University of Denver
 Formed a research team to prototype an XML/EDI operating environment in order to explore it’s feasibility
 RosettaNet
 Investigating the use of XML as an alternative to EDI
 Catalog Information Specification
 EDIFECS Commerce
 Guideline XML (gXML)

XML/EDI Tools
 XML Editors - XML/EDI Editors
 XML Parsers - XML/EDI Parsers
 Browsers - XML/EDI Aware Browsers
 DTD Editors/Tools - XML/EDI DTD Editors/Tools
 APIs - XML/EDI specific APIs
 XLink/XPointer Tools - TBD
 XSL Editors - XML/EDI XSL Forms
 Transaction/Publishing Systems/Databases
 Conversion Tools
 Specialized XML Software

XML/EDI Tools
 EDI Software Vendors
 TSI
 GEIS
 Sterling
 St. Paul Software
 Harbinger
 IBM
 IPNet
 PaperFree

XML/EDI Vision
Trading
Partner
Trading
Partner
Service
Providers
XML
Repository
Trading
Partner
Internet
NGI
NII
GII
Extranet
POTS
VANs
Trading
Partner

Next Steps
 Formalized Business Case
 Standardization
 Approach
 Naming Conventions
 Infrastructure
 Repository Development
 Usage Guidelines
 XML Version 1.0 Extensions
 XML/EDI Software Tools
 Industry Adoption

??
??
?
?
??
?
?
??