201 Shannon Oaks Circle Cary, NC 27511-7610 +1-919-657-1500 voice +1-919-657-1501 fax XML for...

201 Shannon Oaks Circle Cary, NC 27511-7610 +1-919-657-1500 voice +1-919-657-1501 fax www.rtci.com

XML for E-XML for E-

CommerceCommerceR.T.Crowley

Vice President, Marketing

Internet Commerce Corporation


Using the InternetUsing the Internet

Refrigerator WebsitesRefrigerator Websites• www.smartbox.com• Secure home

delivery system• Order supplies via

the Web• Deliverer gets a one-

time security code• Only one side can be

open at a time• Perfect for shut-in

techies!


The Nature of The Nature of ChangeChange

To be involved in To be involved in

EDI is to be EDI is to be

passionatelypassionately in love in love

with change.with change. -- -- Edward A. GuilbertEdward A. Guilbert


Using XML for EDIUsing XML for EDI

Traditional EDI:Traditional EDI:• Handles fully 80% of all business information

exchange world-wide.

• Still viable among the Fortune 1000Fortune 1000 and other large companies.

• Used in some form virtually everywhere around the world today.

• Forms the basis of the business rules to be kept as we move to newer technologies.



What is XML?:What is XML?:• XML is eXXtensible MMarkup LLanguage.

• XML is a derivative of SGML (Standard Generalized Markup Language) like HTML.

• XML allows dynamic tagging of data to be shared.

• XML provides a document definition structure.

• XML provides multiple presentation options.

• Example of an XML tag:<name>Stoshu ChodkiewiczStoshu Chodkiewicz</name>



Why use XML for EDI?:Why use XML for EDI?:• XML bridges the gap between traditional EDI

and Web-based applications.

• Most of high-tech industry has espoused XML:• Virtually all new software from IBM, Microsoft,

Netscape, Oracle, and others are enabled to use XML.

• Companies are making larger cash investments in XML technology than were made in OLE and ODBC.

• XML could make EC/EDI more available to the SME and other non-traditional EDI users.


Using XML for EDIUsing XML for EDIWho Is Doing XML/EDI?:Who Is Doing XML/EDI?:• ebXML Group:ebXML Group: An international initiative

established between UN/CEFACT and OASIS to develop XML a standard XML architecture. (Further information: www.ebxml.org)

• ANSI ASC X12:ANSI ASC X12: The US national EDI standards body has created a technical report of an experimental syntax for using XML to conduct EDI. (Further information: www.disa.org)

• BizTalkBizTalk™: A: An effort from MicrosoftMicrosoft® to create a method to use XML to communicate between applications on a cross-platform basis. (Further information: www.biztalk.org)


Using XML for EDIUsing XML for EDIWho Is Doing XML/EDI?:Who Is Doing XML/EDI?:• The XML/edi Group:The XML/edi Group: This part of DISA provides

information on use of XML in graphic communication. (Further information: www.xmledi.com)

• CommerceNet:CommerceNet: This group encourages the use of the Net for commerce of all types, and as such, has a direct interest in the use of XML for conducting EDI. (Further information: www.commerce.net)

• RosettaNet: This group is developing an X12-based implementation framework like the BizTalk™ framework mentioned earlier. (Further information: www.rosettanet.org)


Using XML for EDIUsing XML for EDIWho Sets the XML Standard?:Who Sets the XML Standard?:• W3C:W3C: The World Wide Web Consortium (Further

information: www.w3c.org)

• W3C is the de facto standards body for the Internet and the World Wide Web.

• It is made up of those companies with a large stake in business via the Web, including IBM, Microsoft, Netscape, and others.

• This group developed and sets the standards for the XML language.

• Message standards will be set by other standards bodies.



Being Radical:Being Radical:• The use of EDI message standards for XML

represents probably 15% of the real benefit of XML.

• Using the old message methodologies for XML is like

going from the horse and buggy to the automobile

by keeping the buggy and motorizing the horse!

• The true benefit of XML lies in its ability to make

dissimilar databases and systems interoperable.



What’s in a name?What’s in a name?

Tarheel Systems (DUNS 2736541) is

making a shipment from one

division of the company to another.

Therefore, they need to be shown

as the “shipper” in the transaction

set or message.



The X12 EDI Version:

The N1 Segment

N1*SH*Tarheel Systems*1*2736541*07*SH



The Basis of the X12-XML Version:<N1-Name>

<EntityIDCode>SHSH</EntityIDCode>

<Name>Tarheel SystemsTarheel Systems</Name>

<IDCodeQual>11</IDCodeQual>

<IDCode>27365412736541</IDCode>

<EntityRelationCode>0707</EntityRelationCode>

<EntityIDCode>SHSH</EntityIDCode>

</N1-Name>



The Full X12-XML Version:<N1_Name X12:PROMOTEDQUAL="Shipper">

<EntityIdCode X12:ID-SEMANTIC="EntityIdCode”

X12:SYNTAXID="H020N1_01">SHSH</EntityIdCode>

<Name X12:ID-SEMANTIC="Name" X12:SYNTAXID="H020N1_02">Tarheel SystemsTarheel Systems</Name>

<Id X12:PROMOTEDQUAL="D-U-N-S Number, Dun & Bradstreet">

<IdCodeQual X12:ID-SEMANTIC="IdCodeQual"

X12:SYNTAXID="H020N1_03">11</IdCodeQual>

<IdCode X12:ID-SEMANTIC="IdCode" X12:SYNTAXID="H020N1_04">27365412736541</IdCode>

</Id>

<EntityRelationshipCode X12:ID-SEMANTIC="EntityRelationshipCode”

X12:SYNTAXID="H020N1_05">0707</EntityRelationshipCode>

<EntityIdCode X12:ID-SEMANTIC="EntityIdCode"

X12:SYNTAXID="H020N1_06">SHSH</EntityIdCode>

</N1_Name>



The BizTalkThe BizTalk™™ Method: Method:• MicrosoftMicrosoft®® has published a has published a de factode facto “standard” for XML “standard” for XML

documents as BizTalk Framework v1.0:documents as BizTalk Framework v1.0:

• The Framework lays down guidelines for encoding business

documents using XML.

• Documents must use the XML Data Reduced Subset (XDR).

• Documents described in approved schemas, pass validation

tests, and published on www.biztalk.org can be called BizTalk

Framework Documents.

• BizTalk Messages typically contain one document along with

additional information used by the application.



MicrosoftMicrosoft® BizTalk™:

<EntityID value=“SHSH”/>

<Name value=“Tarheel SystemsTarheel Systems”/>

<DUNSCode value=“27365412736541”/>

<EntityRelationCode value=“0707”/>


Using XML for EDIUsing XML for EDIThe ebXML Vision:The ebXML Vision:• Data TagsTags come from a common dictionary to ensure

all parties are able to understand them.

• The data to be shared is built up of Core ComponentsCore Components rather than cut down from a large, generic message.

• This data is placed in an XML file called a PayloadPayload.

• The PayloadPayload is appended to a HeaderHeader file containing addressing information and hash totals if necessary.

• A DTDDTD or XML:schemaXML:schema could be appended to that package if needed by the receiver.

• The PayloadPayload could be encrypted for security, leaving address information properly in the clear..


Core Component

Using XML for EDIUsing XML for EDICore Components:Core Components:

• Structured packets of related data like Name & Address or Part & Description

• Similar to segments in traditional EDI

• Not objects in the IT sense, although some may play that role

• Determined by a standards body as a part of an XML messaging standard

• Hold any related information together avoiding fragmented semantic dispersal


Core Component

Core Component

Core Component

Core Component

Core Component

DTD

or

XML:schema

or

DCD


Structure:Structure:

• DTD (XML:schema) is built from the Core Components required by the implementation.

• The structure is then used to sort the data in the message.


Using XML for EDIUsing XML for EDIThe Payload:The Payload:

• The Payload, or XML file, carries the data for the message.

• It is constructed based on the data structure in the DTD or XML:schema.

Payloador

XML File

DTD

or

XML:schema

or

DCD



Header:Header:

• The Header is a type of XML file to carry address information.

• It allows all the address data to remain clear of the Payload for clarity.

Header

Payloador

XML File

DTD

or

XML:schema

or

DCD


Using XML for EDIUsing XML for EDIComplete:Complete:

• The Style Sheet presents data to the application in the required form.

• Different Style Sheets allow for multiple types of presentation.

Style Sheet

Header

Payloador

XML File

DTD

or

XML:schema

or

DCD


Using XML for EDIUsing XML for EDIProblems in XML:Problems in XML:• Data Typing -Data Typing - Currently XML provides no

facility to indicate data types.

• Semantic Relations -Semantic Relations - Currently the official XML standard has no method to show relationships between data elements and other structures.

• Element Length Element Length - Currently all data elements in XML are assumed as infinite.

• Misunderstandings -Misunderstandings - Many seem to see XML as a panacea for all the ills of EC. It is NOTNOT!



Solutions in XML:Solutions in XML:• Data Typing -Data Typing - XML:schemaXML:schema will allow a limited

amount of data typing when approved for use.

• Semantic Relations -Semantic Relations - Standards bodies around the world are developing methods to show relationships between data elements and other structures in XML.

• Element Length Element Length - XML:schemaXML:schema will allow a limited method for sizing data elements when approved.

• Understandings -Understandings - We are building a greater base of knowledge in this and other EC technologies.


Using XML for EDIUsing XML for EDIThe Path Forward:The Path Forward:• The BizTalk™ Framework v1.0BizTalk™ Framework v1.0 was published on

20 September 1999.• X12 Technical Report: X12-XML: An X12-XML: An

Experimental Methodology for the Experimental Methodology for the Representation of X12 Semantics in XML SyntaxRepresentation of X12 Semantics in XML Syntax was approved for publication on 7 October 1999.

• The ebXML GroupebXML Group initial draft recommendations were published on 1 June 2000.

• The first XML messaging standards based upon the Core Components architecture are expected in June or July of 2001.

• This is all still VERYVERY new technology!


XML for E-CommerceXML for E-Commerce

A Presentation by:

R.T.CrowleyR.T.Crowley Vice President, MarketingVice President, Marketing Internet Commerce CorporationInternet Commerce Corporation

201 Shannon Oaks Circle201 Shannon Oaks Circle Cary, NC 27511 USACary, NC 27511 USA

Tel: 1-919-657-1500 - Fax: 1-919-657-1501Tel: 1-919-657-1500 - Fax: 1-919-657-1501 Email: [email protected] - Web: www.icc.net - Email: [email protected] - Web: www.icc.net -

www.rtci.comwww.rtci.com WWW.XMLMAGIC.COMWWW.XMLMAGIC.COM

201 Shannon Oaks Circle Cary, NC 27511-7610 +1-919-657-1500 voice +1-919-657-1501 fax XML for...

Documents

Transcript of 201 Shannon Oaks Circle Cary, NC 27511-7610 +1-919-657-1500 voice +1-919-657-1501 fax XML for...