Comments on: EDI vs. XML - how readable is XML? http://editalk.com/edi-news/2008/03/25/edi-vs-xml-how-readable-is-xml/ An EDI and Vendor Compliance Blog, Forum and Support Center. Thu, 04 Dec 2008 00:33:36 +0000 http://wordpress.org/?v=2.6.2 By: EDI 101-B - Standards and Syntax | EDI Talk - Vendor Compliance and Electronic Data Interchange http://editalk.com/edi-news/2008/03/25/edi-vs-xml-how-readable-is-xml/#comment-341 EDI 101-B - Standards and Syntax | EDI Talk - Vendor Compliance and Electronic Data Interchange Wed, 24 Sep 2008 18:55:27 +0000 http://editalk.com/edi-news/2008/03/25/edi-vs-xml-how-readable-is-xml/#comment-341 [...] a previous blog, I talked about the concepts of EDI being replaced by XML; how there’s the DTD/Schema that tells [...] [...] a previous blog, I talked about the concepts of EDI being replaced by XML; how there’s the DTD/Schema that tells [...]

]]> By: Craig Dunham http://editalk.com/edi-news/2008/03/25/edi-vs-xml-how-readable-is-xml/#comment-27 Craig Dunham Thu, 03 Apr 2008 16:05:53 +0000 http://editalk.com/edi-news/2008/03/25/edi-vs-xml-how-readable-is-xml/#comment-27 I just read another blog (http://myediblog.blogspot.com/2008/03/when-did-xml-become-good-idea.html) about the concepts of XML vs EDI - another somebody that "gets it"... Take a read! I just read another blog (http://myediblog.blogspot.com/2008/03/when-did-xml-become-good-idea.html) about the concepts of XML vs EDI - another somebody that “gets it”… Take a read!

]]> By: Craig Dunham http://editalk.com/edi-news/2008/03/25/edi-vs-xml-how-readable-is-xml/#comment-13 Craig Dunham Wed, 26 Mar 2008 14:52:29 +0000 http://editalk.com/edi-news/2008/03/25/edi-vs-xml-how-readable-is-xml/#comment-13 That's pretty much My point - that there are good reasons behind XML - just like HTML - it's a pretty simple and straight-forward language to learn and use... but for order information..? John, you've seen some of our orders for your products - it can easily be a few dozen line items. And then when you send back the ASN, with all of the shipment broken down to the carton level - the document can become so big and unwieldly.... An analogy I was using yesterday on another topic seems to fit - trying to park The Titanic in a compact car space... Sure, you can make it fit - but at what costs...?!? That’s pretty much My point - that there are good reasons behind XML - just like HTML - it’s a pretty simple and straight-forward language to learn and use… but for order information..?

John, you’ve seen some of our orders for your products - it can easily be a few dozen line items. And then when you send back the ASN, with all of the shipment broken down to the carton level - the document can become so big and unwieldly…. An analogy I was using yesterday on another topic seems to fit - trying to park The Titanic in a compact car space… Sure, you can make it fit - but at what costs…?!?

]]> By: John Burmeister http://editalk.com/edi-news/2008/03/25/edi-vs-xml-how-readable-is-xml/#comment-12 John Burmeister Tue, 25 Mar 2008 18:37:56 +0000 http://editalk.com/edi-news/2008/03/25/edi-vs-xml-how-readable-is-xml/#comment-12 The major downfall, as you had mentioned in the fact that there is a HUGE overhead compaired to just using a regular EDI document. Especially when your PO's have hundreds of items. I was in a sterling commerce XML webinar the other day, and one person had mentioned one of their partners uses XML. They were getting one to fifteen meg XML files that bogged their system and translator down. The same order if EDI wouldn't be an issue. I'm a XML fan, its easy to read, easy to parse, but in this case it might not be the right solution? The major downfall, as you had mentioned in the fact that there is a HUGE overhead compaired to just using a regular EDI document. Especially when your PO’s have hundreds of items. I was in a sterling commerce XML webinar the other day, and one person had mentioned one of their partners uses XML. They were getting one to fifteen meg XML files that bogged their system and translator down. The same order if EDI wouldn’t be an issue. I’m a XML fan, its easy to read, easy to parse, but in this case it might not be the right solution?

]]>