Rachel,
A minor typo on the xml web URL, should be a space between stdlist and will, will is not part of the URL. Most of the
schema postings are from the W3C. Rosettanet is always pointed to as an XML success which it arguably is but I would keep
in mind Rosettanet has a paid staff compared to most industry trade assoc that are volunteer. As you know setting standards
is a lot of slow, hard work.
Dave Frenkel
Principal Consultant
Cap Gemini Ernst & Young
425-260-5030
[EMAIL PROTECTED]
-----Original Message-----
From: Rachel Foerster [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 31, 2001 1:04 PM
To: [EMAIL PROTECTED]
Subject: Re: XML Article Question
David,
Your wish is being fulfilled, but perhaps not exactly as you describe it
below. There are literally hundreds of various organizations, consorta,
etc., (RosettaNet being one of the most visible) that are and have been
describing XML tags and their meaning for either vertical industries or
business functions. When you have the time, a visit to http://www.xml.com or
more directly, http://www.xml.com/pub/q/stdlistwill expose you to some of
these efforts.
I personally believe this makes sense, since it's in these
organizations/consorta that the business knowledge resides and where the
parties that will be implementing XML-based information exchanges play.
If the world wanted and could/would use a single standard business message,
say for example, a purchase order, then we wouldn't have thousands of
variations on the X12 850. Thus, a single common standard for any given
business message, is in my opinion, not only not achievable, but totally
unrealistic.
Rachel
It is interesting to see the Listserv explode with opinions on various =
subjects like XML. Whatever the transport
method (EDI, XML, 'ABC') they all have similar business issues that have =
traditionally inflated the cost of implementing these technologies and =
XML is no different. What I believe needs to happen is the same =
organizations that helped standardize vertical EDI transactions (UCC, =
CIDX, PIDX, TCIF, HEDIC, WEDI, X12N, etc) need to establish business =
dictionaries as to what an XML tag means. For example is the 'ship =
date' the date the product is packaged, put on the dock, loaded on a =
truck, when the truck left the dock, or when the truck left the company
lot. Almost every company/industry has its 'jargon' that is a barrier =
to EDI or XML.
Dave Frenkel =20
----- Original Message -----=20
From: Susan Carley Oliver=20
To: [EMAIL PROTECTED]=20
Sent: Wednesday, January 31, 2001 9:56 AM
Subject: XML Article Question
I'm curious -=20
=20
"There really is no way to validate the =
data tags until you try to part them, if you
can," says Steven Dobson, a software =
engineer for Ironside Technologies
=20
Should that have read "until you try to **parse** them"?
Susan Carley Oliver
1500 SW Park Avenue, #229
Portland, OR 97201
503.243.5553
[EMAIL PROTECTED]
------=_NextPart_000_009A_01C08B70.8A65CFA0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>It is interesting to see the Listserv explode with opinions on =
various=20
subjects like XML. Whatever the transport</DIV>
<DIV>method (EDI, XML, 'ABC') they all have similar business issues that =
have=20
traditionally inflated the cost of implementing these technologies and =
XML is no=20
different. What I believe needs to happen is the same =
organizations=20
that helped standardize vertical EDI transactions (UCC, CIDX, PIDX, =
TCIF, HEDIC,=20
WEDI, X12N, etc) need to establish business dictionaries as to what an =
XML tag=20
means. For example is the 'ship date' the date the product is =
packaged,=20
put on the dock, loaded on a truck, when the truck left the dock, =
or when=20
the truck left the company</DIV>
<DIV>lot. Almost every company/industry has its 'jargon' that =
is=20
a barrier to EDI or XML.</DIV>
<DIV>Dave Frenkel </DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A href=3D"mailto:[EMAIL PROTECTED]"=20
[EMAIL PROTECTED]>Susan Carley =
Oliver</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
href=3D"mailto:[EMAIL PROTECTED]"=20
[EMAIL PROTECTED]>[EMAIL PROTECTED]</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, January 31, =
2001 9:56=20
AM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> XML Article =
Question</DIV>
<DIV><BR></DIV>
<DIV><SPAN class=3D20135617-31012001><FONT color=3D#000000 =
face=3DArial size=3D2>I'm=20
curious - </FONT></SPAN></DIV>
<DIV><SPAN class=3D20135617-31012001><FONT color=3D#000000 =
face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><FONT=20
=
size=3D2><BR> =
&=
nbsp; =20
"There really is no way to validate the data tags until you try to =
part them,=20
if=20
=
you<BR> =
&=
nbsp; =20
can," says Steven Dobson, a software engineer for Ironside=20
Technologies</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><SPAN class=3D20135617-31012001><FONT color=3D#000000 =
face=3DArial=20
size=3D2>Should that have read "until you try to **parse**=20
them"?</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Susan Carley Oliver</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>1500 SW Park Avenue, =
#229</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Portland, OR 97201</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>503.243.5553</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A=20
=
href=3D"mailto:[EMAIL PROTECTED]">susan.carley.oli=
[EMAIL PROTECTED]</A></FONT></DIV>
<DIV> </DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_009A_01C08B70.8A65CFA0--
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
