XML/EDI Overview XML/EDI Overview West Chester Electronic West Chester Electronic Commerce Resource Commerce Resource Center (ECRC) Center (ECRC) 888-745-3748
Jan 26, 2016
XML/EDI OverviewXML/EDI Overview
West Chester Electronic West Chester Electronic Commerce Resource Center Commerce Resource Center
(ECRC)(ECRC)
888-745-3748
TopicsTopics
XML Background XML/EDI XML/EDI Initiatives XML/EDI Tools XML/EDI Vision Next Steps
Background
BackgroundBackground
Proprietary Markup LanguagesWord Processors
Standard Generalized Markup Language (SGML) ISO 8879 - defines a generic document definition and
data markup languageSeparate structure & content
Hypertext Markup Language (HTML)Application of SGML (HTML DTD)Predefined set of tagsDefines the format of a document
Background
Background (cont’d)Background (cont’d)
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
Why Use XML?Why Use XML?
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
XML BenefitsXML Benefits
More meaningful searches Separation of content and format Development of flexible web applications Open standards Flexible format for different use
Wire format for web deliveryTransfer format for sharing dataPersistent data format for disk storage
Background
Background
XML ComponentsXML Components
XML family of standardsXMLXML Link Language (XLL)XML Stylesheet Language (XSL) Document Object Model (DOM)XML Query Language (XML-QL/XQL)NamespacesDocument Content Description (DCD)XML Repositories
Background
XML UsageXML Usage
Presentation-Oriented Publishing (POP)POP documents are chiefly written by humans for
other humans to readBrowser - Browser
Message-Oriented MiddlewareMOM documents are documents mainly generated
from computer systems for use by other computer systems
Application to ApplicationApplication to Human/Human to Application
Background
XML DocumentsXML Documents
Consist of character data and markup Allowed markup
ElementsEntity referencesCommentsProcessing instructionsMarked sectionsDocument type declarations
Prolog
Document Type Declaration
Root Element
Element
Element
Epilog
Background
XML Document StructureXML Document Structure
Two Classes of XML Two Classes of XML DocumentsDocuments
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>
Example XML DocumentExample XML DocumentBackground
Background
What’s on the Horizon for What’s on the Horizon for XMLXML
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
XML/EDI GoalsXML/EDI Goals
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
The Five Technologies 0f The Five Technologies 0f XML/EDIXML/EDI
XML/EDI
Layers of an XML/EDI Layers of an XML/EDI SystemSystem
XML/EDI
Future Based on XML/EDIFuture Based on XML/EDI
XML/EDI
Typical EDI ScenarioTypical EDI Scenario
Request for Quote (840)
Response to RFQ (843)
Purchase Order (850)
P.O. Acknowledgment (855)
Purchase Order Change (860)
P.O. Change Acknowledgment (865)
Invoice (810)/Advance Ship Notice (856)
FRT Bill (210)
Receiving Advice (861)
Payment Order/Remittance Advice (820)
Electronic Funds Transfer
Your Customer
Purchasing
Receiving
Financial
You
Sales
Order Entry
Shipping
Financial
Technical Specifications (841)
XML/EDI
EDI ProcessesEDI Processes
Data Entry/Data Collection Application Extract Outbound EDI Processing Communications Processing Inbound EDI Processing Application Import Error Handling
XML/EDI
XML/EDI ScenarioXML/EDI Scenario
Company A extracts PO data from purchasing systemUDFXML Document(s)/XML Objects
Map extracted PO data to XML/EDI or EDI formatValidate XML/EDI against repository DTD/DCD IC
Transmit XML/EDI to Company BVia VANVia Internet
– http, ftp, smtp
XML/EDI
XML/EDI Scenario (cont’d)XML/EDI Scenario (cont’d)
Company B receives/retrieves XML/EDI PO Access repository
Appropriate XSL stylesheet(s) for processingDTDDCD
Process XML/EDI PO Import into order entry system Print order
XML/EDI
Why Use XML for EDI?Why Use XML for EDI?
XML bridges the gap between traditional EDI & Web-based applications
Most of software industry has embraced XMLMicrosoft, IBM, Netscape, Oracle, SAP, etc.
XML could make EC/EDI more available to SMEs & other non-traditional EDI users
XML/EDI
Problems using XML for Problems using XML for EDIEDI
Data TypingCurrently XML has no facility to show data types
Exposed SemanticsCurrently 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 LengthsCurrently XML has no method to specify minimum
and maximum lengths
XML/EDI
XML/EDI Example 1XML/EDI Example 1
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
XML/EDI Example 2XML/EDI Example 2
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
XML/EDI Example 3XML/EDI Example 3
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
XML/EDI Example 4XML/EDI Example 4
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
XML/EDI Example 5XML/EDI Example 5
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
XML/EDI PlayersXML/EDI Players
ANSI ASC X12 UN/EDIFACT XML/EDI Group CommerceNet W3C Graphics Communications Association (GCA) Software Vendors
XML/EDI Initiatives
ANSI ASC X12ANSI ASC X12
“ASC X12 on the Brink of Completing X12 Technical Report” - 3/11/99Final stages of X12-XML methodologyX12C Approval June 99/Publication in October 99
GoalsDefine a method to expose the semantic content of
X12 standards as well-formed XML documentsEnsure X12/XML is interoperable with native X12
syntax Future Efforts
Validation, Acknowledgments, & Error Handling
XML/EDI Initiatives
ANSI ASC X12 (cont’d)ANSI ASC X12 (cont’d)
2/98 Meeting - Los Angeles Informational Session on XML/EDI
6/98 Meeting - ColumbusAd Hoc XML/EDI Committee
8/98Preliminary Findings & Recommendations on the
Representation of X12 Data Elements and Structures in XML
10/98 Meeting - MiamiNear & Long Term GoalsX12C TG3
XML/EDI Initiatives
ANSI ASC X12 (cont’d)ANSI ASC X12 (cont’d)
2/99 Meeting - DallasDevelopment of X12/XML MatrixObjectives for Technical ReportProposals
Approach ProposalsFreeform Attribute IdentifiedDiscrete Field Group by Semantic RelationshipPromotional Multi-PartFreeform Attribute Identified REFID TagsA Methodology for Semantic Tags
XML/EDI Initiatives
UN/EDIFACTUN/EDIFACT
European XML/EDI Pilot ProjectWill test XML for EDI between business & other
organizationsSIMPL-EDI DTDs
– Orders– Invoices– Despatch Advices– Value Chain Planning & Performance Reports– International Payment Orders– Order Responses
http://www.cenorm.be/isss/workshop/ec/xmledi/Isss-xml.html
XML/EDI Initiatives
UN/EDIFACT (cont’d)UN/EDIFACT (cont’d)
XML/EDI Repository ProposalGlobal repository for XML tagsFunctionality of Repository
– Creating/Requesting Tags– Browsing/Searching for Tags– Downloading a subset of repository– Automatic Update by Subscription
XML/EDI Initiatives
CommerceNetCommerceNet
eCo Framework ProjectGoal 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
Other InitiativesOther Initiatives
The Center for the Study of EC in the Daniel's College of Business at the University of DenverFormed 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 EDICatalog Information Specification
EDIFECS CommerceGuideline XML (gXML)
XML ToolsXML 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
XML/EDI Tools
XML/EDI ToolsXML/EDI Tools
EDI Software VendorsTSIGEISSterlingSt. Paul SoftwareHarbinger IBM IPNetPaperFree
XML/EDI VisionXML/EDI Vision
Internet
NGI
NII
GII
Extranet
POTS
XMLRepository
Trading Partner
ServiceProviders
VANs
Trading Partner
Trading Partner
Trading Partner
Trading Partner
Trading Partner
XML/EDI Vision
Next Steps
Next StepsNext Steps
Formalized Business Case Standardization
ApproachNaming Conventions
InfrastructureRepository DevelopmentUsage Guidelines
XML Version 1.0 Extensions XML/EDI Software Tools Industry Adoption
QuestionsQuestions
??
??
??
??
??
??