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

RE: <ADVOCACY> Why I Don't Like XML

From: "Marlo Brooke" <mbrooke@...>
Date: Mon Feb 7, 2005  10:38 pm
Subject: RE: [EDI-L] <ADVOCACY> Why I Don't Like XML

William,

You are correct. XML is the data format standard for communicating to and
from UCCnet, endorsed by Wal-Mart and about 4,000+ other companies including
most of the large retailers (Kroger, Home Depot, etc.). UCCnet is gaining
huge momentum at the moment. To many, data synchronization is seen as a
foundational architecture to other initiatives also pushed by the large
retailers, such as RFID and Collaborative trading activities (such as CPFR
and CTM).

Marlo Brooke
Avatar Partners
www.avatarpartners.com
-----Original Message-----
From: William J. Kammerer [mailto: Sent: Monday, February 07, 2005 2:24 PM
To: EDI-L Mailing List
Subject: Re: [EDI-L] <ADVOCACY> Why I Don't Like XML


Earl, I thought Walmart had something to do with the EAN.UCC standards
and UCCNET for data synchronization. I could swear XML had something to
do with this stuff. Isn't this going anywhere?

William J. Kammerer
Novannet
Columbus, OH 43221-3859 . USA
+1 (614) 487-0320

----- Original Message -----
From: "Earl Wertheimer" < To: < Sent: Monday, 07 February, 2005 09:43 AM
Subject: Re: [EDI-L] <ADVOCACY> Why I Don't Like XML



William

> Earl, don't look to the 800-lb. gorillas to initiate revolutions. It's
> unlikely a gorilla would exclusively mandate a gussied-up UML-modeled
> core-componentized ISO 11179 compliant XML based e-business standard.


I agree, but the 800 lb gorilla (Walmart) had a lot of force in the
marketplace.

When Walmart pushed Bisynch modems, their trading partners had no
choice. When Walmart pushed AS2, again the trading partners had no
choice.

They make these decisions because they are better economically FOR THEM,
not to advance the technology.

Any new technology must show good economic benefits, or it will be
delegated to some niche.

I don't see those benefits with XML or any of the other acronyms being
thrown around recently.

Show us the benefits... You'll see the converts ;-)


> Medicare is another case in point. That's why HIPAA's TCS Rule
> strictly
> mandates - for the most part - crusty, old X12 EDI for claims,
> payments
> and whatnot. Is that why Martin Morrison is stuck with abominations
> like
> 300 megabyte 837 Healthcare Claim transactions? And to this day, 9
> years
> after HIPAA was promulgated, Medicare itself still can't conform
> completely to the "standard" HIPAA EDI guidelines.

Wasn't the main culprit the government who mandated HIPAA?
In that case, the economic benefits are _not_ considerations. ;-)

Earl Wertheimer
http://www.spe-edi.com



.
Please use the following Message Identifiers as your subject prefix:
<SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L



Yahoo! Groups Sponsor
ADVERTISEMENT





----------------------------------------------------------------------------
--
Yahoo! Groups Links

a.. To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/

b.. To unsubscribe from this group, send an email to:

c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



[Non-text portions of this message have been removed]







 
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.