[EDI-L Mailing List Archive Home] [Message List] [Reply To This Message]

Re: Fw: PLEASE 'splain a DTD's purpose

From: "ldcat1" <ldcat1@...>
Date: Sat Nov 2, 2002  1:52 am
Subject: Re: [EDI-L] Fw: PLEASE 'splain a DTD's purpose
There are two issues here-

1) Delivery of the DTD with the XML document should ensure that it can be
read, using the rules applied to the document. This is something that has
been tried in plain old EDI- giving the guide to read the document along
with the document itself. The receiver should be able to bring the DTD into
their parser and interpret the document.

However,

2) The real issue behind EDI (EDIFACT and ANSI) is the data dictionary and
consistency in the data dictionary used. In other words do we mean the same
thing in both the content and the segment names or tags. The process of
developing a standard is more about content and meaning then the actual
syntax- apologies to TAS, etc. Although I too have participated in lengthy
discussions about proper syntax and desirable semantics, I spent most of my
time in standards organizations talking about content and getting agreement
to what content should be included and what we should call it.

Item 2 is the real challenge faced by the plethora of XML standards
organizations. When they are highly focused- a single industry or a single
application for the message, gaining consensus is easier. As their
missions/audience/participants broaden, the process of gaining consensus on
content and meaning also grow.

Anyway- my perspective straddling the existing EDI and the new XML EDI.

Len


----- Original Message -----
From: "Michael Mattias" < To: "EDI-L Yahoogroups" < Sent: Friday, November 01, 2002 3:52 PM
Subject: [EDI-L] Fw: PLEASE 'splain a DTD's purpose


> For those of you who think XML is going to replace ANSI and EDIFACT EDI,
and wonder why some of us old flatii have our doubts due
> to lack of standards for business transactions, I thought I would share
this posting from the Usenet newsgroup microsoft.public.xml
> from a new member of the "one of your own" club......
>
> Out of the mouths of babes....
>
> (In context, 'babes' means 'children.' So don't go accusing me of sexism.
OK, sweetheart?)
>
> Michael Mattias
> Tal Systems, Inc.
> Racine WI
> >
> ----- Original Message -----
> From: "xmEllen" < > Newsgroups: microsoft.public.xml
> Sent: Friday, November 01, 2002 2:03 PM
> Subject: PLEASE 'splain a DTD's purpose
>
>
> > Hi,
> >
> > I've been taking a class in XML where we have written DTD's and
> > Schemas as part of our coursework.
> >
> > The class material says that DTDs and Schemas are recommended to
> > ensure document conformity especially in Business-To-Business
> > transactions where XML documents are being exchanged.
> >
> > OK, so I work for Company A. I write an XML document and also write a
> > DTD to go with it. I send my XML document and DTD to company B. My
> > DTD says that my XML document must have element X which must have
> > exactly 3 specified child elements, and 2 specified attributes and
> > so forth.
> >
> > While I am writing my XML document, I can use the DTD to validate the
> > XML document to make sure that I've followed my own rules.
> >
> > But what's the point beyond insuring that I have followed my own
> > rules? When company B gets my XML file, what does it matter to them
> > that I followed my own rules for how the XML document should be? And
> > what if the DTD referenced in my xml doc somehow gets changed by
> > someone at Company B? Then what?
> >
> > IE has it's own DTD built inside which allows us to write and look at
> > other people's html docs. But we cannot change this DTD - it is built
> > into IE. We do have the ability to change and use any DTD we want?
> > Wouldn't this spell confusion?
> >
> > I guess my question is what is the point of a DTD and Schema beyond
> > insuring that xml writers follow their own rules.
> >
> > Thanks,
> > xmEllen
>
>
>
> To unsubscribe from this group, send an email to:
> > Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
<OFF-TOPIC>
> Access the list online at: http://groups.yahoo.com/group/EDI-L
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>





 
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools Simplify EDI Data Integration with Stylus Studio XML Enterprise Suite - Free Download!
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2007 All Rights Reserved.