<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-503554439506827322</id><updated>2012-01-12T00:00:07.018Z</updated><category term='paper'/><category term='story'/><category term='comms'/><category term='embedded'/><category term='transactions'/><category term='finance'/><category term='ean-ucc'/><category term='history'/><category term='standards'/><category term='dilbert'/><category term='formats'/><category term='pigeon'/><category term='catalogue'/><category term='all'/><category term='film'/><category term='mapping'/><category term='gov'/><category term='programs'/><category term='orders'/><title type='text'>My EDI Blog</title><subtitle type='html'>A blog about Electronic Data Interchange
&lt;br&gt;
EDIFACT EANCOM X12 TRADACOM ODETTE EBIZ XML HTML PDF CSV TXT JSON
&lt;br&gt;
FTP HTTP AS2 SMTP POP3 Dial-up Point-2-Point SOAP Pigeon</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://myediblog.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>34</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-7126660462599927688</id><published>2012-01-11T23:42:00.004Z</published><updated>2012-01-11T23:48:54.655Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='formats'/><category scheme='http://www.blogger.com/atom/ns#' term='standards'/><title type='text'>Green Coffee XML - Revisited</title><summary type='text'>I wrote before about my frustration at EDI Standards Proliferation. I also said if there was anything more fustrating than EDI Standards Proliferation, it was EDI Standards Secrecy.Well done to the Green Coffee Organisation. I can now find reference material for Green Coffee XML on the internet for free. This link leads you to a 124 page PDF document, Contract Terms &amp; Conditions. There listed in </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/7126660462599927688'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/7126660462599927688'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2012/01/green-coffee-xml-revisited.html' title='Green Coffee XML - Revisited'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-4391869104779462376</id><published>2012-01-05T23:03:00.006Z</published><updated>2012-01-05T23:23:54.895Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='catalogue'/><category scheme='http://www.blogger.com/atom/ns#' term='story'/><category scheme='http://www.blogger.com/atom/ns#' term='orders'/><title type='text'>The Limits of the Catalogue</title><summary type='text'>I have a problem. I don't normally like to talk about it, but you may share the same problem and if we get it out in the open, then maybe we can all cope with it better. The problem with this problem, is it doesn't have an obvious name. So while no one likes to be labeled, without a label it is hard to communicate easily. How to describe it? Where to begin?The problem stems from the nature of the</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/4391869104779462376'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/4391869104779462376'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2012/01/limits-of-catalogue.html' title='The Limits of the Catalogue'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-4524326145730655323</id><published>2010-04-21T23:05:00.005+01:00</published><updated>2010-04-21T23:31:48.819+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='standards'/><category scheme='http://www.blogger.com/atom/ns#' term='story'/><category scheme='http://www.blogger.com/atom/ns#' term='film'/><title type='text'>It is an Ill wind that blows nobody any good - from Berlin to Haiti</title><summary type='text'>For as long as I can remember I have been reading the phrase "EDI has its beginnings in the Berlin Airlift in 1948". The next bit of history usually jumps to the 1960's American Transport industry. I read this again recently and for once it got me wondering. What electronic communication was there in 1948? What message was it and in what format, and how was it delivered? How was it developed and </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/4524326145730655323'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/4524326145730655323'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2010/04/it-is-ill-wind-that-blows-nobody-any.html' title='It is an Ill wind that blows nobody any good - from Berlin to Haiti'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-3100447277013505248</id><published>2009-11-25T00:18:00.003Z</published><updated>2009-11-25T00:36:32.263Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='standards'/><title type='text'>When do Standards become Standards ?</title><summary type='text'>I want to promote good sense when I read it. Adam Bosworth has a very good article on standards. He is not talking about EDI standards, but technical and software standards in general. Yet everything he  says I feel is applicable to EDI.In summary, standards should be simple, readable, focused, precise, implemented, forgiving and free.Adam's standards background is ODBC, AJAX and XML. These </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/3100447277013505248'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/3100447277013505248'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2009/11/when-do-standards-become-standards.html' title='When do Standards become Standards ?'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-1692854690762445311</id><published>2009-11-23T00:22:00.005Z</published><updated>2009-11-23T01:03:01.500Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='programs'/><category scheme='http://www.blogger.com/atom/ns#' term='comms'/><title type='text'>Creating an FTP Script</title><summary type='text'>In the last post I discussed using a web FTP service as an alternative EDI service, so I thourght I should also provide some help with FTP scripts. You can use a graphical tool like windows explorer for example by typing  ftp://someserver.net  in the address box. However to eliminate the work of the human operator as far as possible, scripts are needed.That said the best first step to achieve </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/1692854690762445311'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/1692854690762445311'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2009/11/creating-ftp-script.html' title='Creating an FTP Script'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-2281208167714535444</id><published>2009-11-15T23:13:00.003Z</published><updated>2009-11-15T23:27:51.120Z</updated><title type='text'>How to use an FTP Host as an Alternative EDI Network</title><summary type='text'>Web site hosting services are very competative now. Easy to use and ever cheaper for both individuals and companies. These servers and systems can also easily provide FTP connections. Dozens of user logins and Giga bytes of storage can be had for an annual cost of less than the purchase price of a desktop computer. With the aid of some relatively simple scripts your computer system can reach out </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/2281208167714535444'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/2281208167714535444'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2009/11/how-to-use-ftp-host-as-alternative-edi.html' title='How to use an FTP Host as an Alternative EDI Network'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-4109375716309029518</id><published>2009-08-03T23:54:00.004+01:00</published><updated>2009-08-04T00:08:36.321+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='embedded'/><category scheme='http://www.blogger.com/atom/ns#' term='standards'/><category scheme='http://www.blogger.com/atom/ns#' term='comms'/><title type='text'>Embedded EDI</title><summary type='text'>I have just come across the phrase Embedded EDI. I think it fits quite nicely as a label for what I have been trying to articulate.Some highlights..."Are a CEO’s email or Text Messages more or less important than an X12 Shipping notice?""Why is EDI not subject to universal addressing via DNS or URI name-spaces?""CEO’s and children expect email to reach it’s destination, but Supply chain managers </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/4109375716309029518'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/4109375716309029518'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2009/08/embedded-edi.html' title='Embedded EDI'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-6798798214398114131</id><published>2009-08-02T00:02:00.001+01:00</published><updated>2009-08-02T00:05:01.884+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><title type='text'>I am Eddy</title><summary type='text'>Eddy (fluid dynamics): The swirling of a fluid and the reverse current created when the fluid flows past an obstacle.</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/6798798214398114131'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/6798798214398114131'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2009/08/i-am-eddy.html' title='I am Eddy'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-6533558716964720979</id><published>2009-07-23T00:32:00.003+01:00</published><updated>2009-07-23T00:41:14.908+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='dilbert'/><title type='text'>I am not Eddy</title><summary type='text'>I am not angry with every idiot.</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/6533558716964720979'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/6533558716964720979'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2009/07/i-am-not-eddy.html' title='I am not Eddy'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-4404641148855927692</id><published>2009-05-28T00:16:00.014+01:00</published><updated>2009-05-28T00:52:59.449+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='formats'/><category scheme='http://www.blogger.com/atom/ns#' term='standards'/><category scheme='http://www.blogger.com/atom/ns#' term='story'/><category scheme='http://www.blogger.com/atom/ns#' term='orders'/><title type='text'>When Lost, it helps to remember where you want to go</title><summary type='text'>I have the occasional high school student pass through my office on work experience. They do the rounds going to each department. When they come to me they have already spent time in the Sales and Purchasing departments. I am expected to give them a 30 minute overview of EDI (I don't just do EDI, but no one else understands it, or wants to understand it, so that is what they ask me to do). Then </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/4404641148855927692'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/4404641148855927692'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2009/05/when-lost-it-helps-to-remember-where.html' title='When Lost, it helps to remember where you want to go'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-3595581111367037928</id><published>2009-04-17T23:24:00.004+01:00</published><updated>2009-04-17T23:45:28.929+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='formats'/><category scheme='http://www.blogger.com/atom/ns#' term='ean-ucc'/><category scheme='http://www.blogger.com/atom/ns#' term='standards'/><category scheme='http://www.blogger.com/atom/ns#' term='mapping'/><title type='text'>What if EAN/UCC numbers didn't exist?</title><summary type='text'>I was in the process of setting up a mapping for a new EDI (Electronic Data Interchange) customer. One of the first things I had to do was to take the senders ID from the message envelope and create a look-up link to the customers account on our ERP system. Now just lately I have become obsessed by leaner, simpler EDI. So I looked at this "simple" process with new eyes.The senders ID, and by </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/3595581111367037928'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/3595581111367037928'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2009/04/what-if-eanucc-numbers-didnt-exist.html' title='What if EAN/UCC numbers didn&apos;t exist?'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-9120322728537256360</id><published>2009-02-02T23:42:00.004Z</published><updated>2009-02-03T00:57:24.485Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='transactions'/><category scheme='http://www.blogger.com/atom/ns#' term='finance'/><category scheme='http://www.blogger.com/atom/ns#' term='film'/><title type='text'>Million Dollar Traders, Nickel &amp; Dime EDI</title><summary type='text'>They don't seem to do "Documentaries" any more. It is all "Reality TV" these days, and I have mostly had enough of them. I wish shows like "The Apprentice" would show more details of the problem solving, less of the problem personalities. But such is the rarity of Business related material I gave this new show a go.Million Dollar Traders - the premise: take some ordinary people who show some </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/9120322728537256360'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/9120322728537256360'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2009/02/million-dollar-traders-nickel-dime-edi.html' title='Million Dollar Traders, Nickel &amp; Dime EDI'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-5355088339249477933</id><published>2008-11-04T21:42:00.005Z</published><updated>2008-11-04T22:00:30.290Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='formats'/><category scheme='http://www.blogger.com/atom/ns#' term='standards'/><category scheme='http://www.blogger.com/atom/ns#' term='comms'/><category scheme='http://www.blogger.com/atom/ns#' term='paper'/><category scheme='http://www.blogger.com/atom/ns#' term='mapping'/><title type='text'>Electronic Data Interchange Needs Electronic Paper</title><summary type='text'>There is probably a word for it. You know, when you are struggling to express an idea and try several times without being satisfied that you are getting your point across. Or indeed not sure what your point is. Then someone else hits the nail on the head. Then you feel the ping of recognition, the swell of confirmed pride and the annoying jealousy of "I wish I had said that".I want EDI to be </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/5355088339249477933'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/5355088339249477933'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2008/11/electronic-data-interchange-needs.html' title='Electronic Data Interchange Needs Electronic Paper'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-2273228975366002616</id><published>2008-08-15T00:17:00.004+01:00</published><updated>2008-08-15T00:53:43.374+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='formats'/><category scheme='http://www.blogger.com/atom/ns#' term='standards'/><category scheme='http://www.blogger.com/atom/ns#' term='film'/><category scheme='http://www.blogger.com/atom/ns#' term='history'/><title type='text'>Freedom !</title><summary type='text'>I have just read Craig's post on EDITalk and was motivated to leave a long comment. So I have decided to re-post it here.Quoting Braveheart is like a red rag to a bull to me. I have got to respond.I am going to go on a bit about history here, but bear with me. I will come back to EDI (Electronic Data Interchange) at the end.For the average Joe, the freedom Wallace (and Mel Gibson) was fighting </summary><link rel='related' href='http://editalk.com/articles/2008/08/08/its-all-for-nothing-if-you-dont-have-freedom/' title='Freedom !'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/2273228975366002616'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/2273228975366002616'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2008/08/freedom.html' title='Freedom !'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-8160493128215835085</id><published>2008-08-11T23:42:00.004+01:00</published><updated>2008-08-15T00:54:10.582+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='formats'/><category scheme='http://www.blogger.com/atom/ns#' term='story'/><title type='text'>CSVML - Accept No Compromise</title><summary type='text'>Can't decide between XML and CSV? I have the answer, and it is not JSON as I previously thought.I have seen the light.The answer is here. Hilarious! (well it is hilarious if you are a geek).In a future post I shall show how the future of EDI (Electronic Data Interchange) is a merger of Edifact, X12 &amp; Tradacom by using Facsimile technology...</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/8160493128215835085'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/8160493128215835085'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2008/08/csvml-accept-no-compromise.html' title='CSVML - Accept No Compromise'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-4122028047814828044</id><published>2008-07-20T22:45:00.012+01:00</published><updated>2008-11-06T23:52:34.648Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='transactions'/><category scheme='http://www.blogger.com/atom/ns#' term='formats'/><category scheme='http://www.blogger.com/atom/ns#' term='standards'/><title type='text'>Alternative EDI Formats Part II – JSON &amp; Protocol Buffers</title><summary type='text'>In the previous post I wrote how a large amount of EDI (that is Electronic Data Interchangein the widest sense) is done, without using a strict formalised standard, using CSV formats. Now Google has released details of how they execute server-to-server/program-to-program message interchange using Protocol Buffers. You won’t see the term EDI any where on Google but then the term doesn’t have a </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/4122028047814828044'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/4122028047814828044'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2008/07/alternative-edi-formats-part-ii-json.html' title='Alternative EDI Formats Part II – JSON &amp; Protocol Buffers'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-4631819480405938402</id><published>2008-07-17T23:46:00.007+01:00</published><updated>2008-07-20T22:25:04.988+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='formats'/><category scheme='http://www.blogger.com/atom/ns#' term='standards'/><title type='text'>Alternative EDI Formats Part I – CSV &amp; JSON</title><summary type='text'>I have been meaning to make this post for a long time, then Google came along with Protocol Buffers and the world moves on. So in this post I am going to outline how CSV files are used and how I thought JSON would be an improvement. In another post I will write about what I think can be learnt from Protocol Buffers.A lot of data is communicated from machine to machine by CSV file format. It might</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/4631819480405938402'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/4631819480405938402'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2008/07/alternative-edi-formats-part-i-csv-json.html' title='Alternative EDI Formats Part I – CSV &amp; JSON'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-314895496203324556</id><published>2008-07-09T22:59:00.005+01:00</published><updated>2012-01-11T23:37:23.904Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='formats'/><category scheme='http://www.blogger.com/atom/ns#' term='story'/><category scheme='http://www.blogger.com/atom/ns#' term='orders'/><title type='text'>Green Coffee XML</title><summary type='text'>I am not kidding (pdf). Some might think this is great. Some might think is shows how wonderful XML is. I don't. To me it represents a lot of what is mixed up about EDI (Electronic Data Interchange). I want to make 2 points...What is so special about Green Coffee that it needs it's own schema?Well reading the docs it seems coffee dealers are a bit fussy about defining when ownership of the </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/314895496203324556'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/314895496203324556'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2008/07/green-coffee-xml.html' title='Green Coffee XML'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-6574741744490829167</id><published>2008-06-28T16:26:00.005+01:00</published><updated>2008-06-28T16:50:50.404+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='pigeon'/><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='gov'/><category scheme='http://www.blogger.com/atom/ns#' term='story'/><title type='text'>Is this what hm.gov.uk thinks is EDI? - Revisited</title><summary type='text'>2 CDs with 7 million names addresses of children and parents, some with bank details, are put in the post and go missing. When I heard about this story I worried about the little guy. Well now the UK Independent Police Complaints Commission have investigated and released their report.  It is well worth a read (pdf). All 61 pages and 282 paragraphs.At the time the Minister was quick to publicly </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/6574741744490829167'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/6574741744490829167'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2008/06/is-this-what-hmgovuk-thinks-is-edi.html' title='Is this what hm.gov.uk thinks is EDI? - Revisited'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-8408455311961917745</id><published>2008-04-02T20:51:00.009+01:00</published><updated>2008-08-15T00:56:24.474+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='formats'/><category scheme='http://www.blogger.com/atom/ns#' term='standards'/><category scheme='http://www.blogger.com/atom/ns#' term='mapping'/><category scheme='http://www.blogger.com/atom/ns#' term='orders'/><title type='text'>Why isn't EDI easier? Part I - One Standard to Rule Them All</title><summary type='text'>EDI (Electronic Data Interchange) really should be less difficult than it is. If I am a start-up company and I want to purchase timber, metal, paper, widgets or some other commodity item, EDI is just too hard.The overhead on establishing a relationship, agreeing a standard, and testing communications is huge. EDI is supposed to reduce cost but if it results in a supplier tie-in then it will </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/8408455311961917745'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/8408455311961917745'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2008/04/why-isnt-edi-easier-part-i-one-standard.html' title='Why isn&apos;t EDI easier? Part I - One Standard to Rule Them All'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-3614990414924769032</id><published>2008-03-31T23:29:00.007+01:00</published><updated>2008-08-15T00:56:47.839+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='formats'/><category scheme='http://www.blogger.com/atom/ns#' term='standards'/><title type='text'>When did XML become a good Idea?</title><summary type='text'>It is so easy to list what is wrong with XML for EDI (Electronic Data Interchange).It produces large filesIt is very processor intensive to parseNeeds another new standardOr can be used/abused without a standardIt isn't even very human readable (despite what some say)And yet... a lot of people find it very compelling.To understand why, imagine you are talking to a developer who knows nothing </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/3614990414924769032'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/3614990414924769032'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2008/03/when-did-xml-become-good-idea.html' title='When did XML become a good Idea?'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-767472327766392430</id><published>2008-03-09T22:49:00.003Z</published><updated>2008-07-22T00:14:21.305+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='transactions'/><category scheme='http://www.blogger.com/atom/ns#' term='formats'/><category scheme='http://www.blogger.com/atom/ns#' term='comms'/><category scheme='http://www.blogger.com/atom/ns#' term='mapping'/><category scheme='http://www.blogger.com/atom/ns#' term='orders'/><title type='text'>EDI System Design - Overview</title><summary type='text'>Part I - Message ControlPart II - Export MappingPart III - Import MappingPart IV - Transaction Processing</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/767472327766392430'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/767472327766392430'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2008/03/edi-system-design-part-overview.html' title='EDI System Design - Overview'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-7214332607884656746</id><published>2007-12-21T00:00:00.001Z</published><updated>2008-03-09T22:55:33.291Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='formats'/><category scheme='http://www.blogger.com/atom/ns#' term='comms'/><title type='text'>EDI Overview</title><summary type='text'>Part I - FormatsPart II - CommunicationPart III - Why</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/7214332607884656746'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/7214332607884656746'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2007/12/edi-overview.html' title='EDI Overview'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-6559191526838061780</id><published>2007-12-09T23:52:00.001Z</published><updated>2008-08-15T00:58:45.926+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='transactions'/><title type='text'>EDI System Design Part IV - Transaction Processing</title><summary type='text'>I have mentioned before that this is the "Elephant in the room" no one likes to talk about. It is hard to talk in abstract terms about something so involved so I am going to take a specific example and use that of a customer sending their Purchase Order. We would want to turn this into a Sales Order.So we get hold of a copy of the message format definition (Edifact, X12, Tradacom etc.),  blow off</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/6559191526838061780'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/6559191526838061780'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2007/12/edi-system-design-part-iv-transaction.html' title='EDI System Design Part IV - Transaction Processing'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-3516935484080710550</id><published>2007-12-03T23:38:00.001Z</published><updated>2008-08-15T00:58:15.185+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='mapping'/><title type='text'>EDI System Design Part III - Import Mapping</title><summary type='text'>OK, I know I've missed something out. Between EDI (Electronic Data Interchange) Exporting and EDI Importing is Communicating. But to understand that, it's best to first have an understanding of both the inputs and outputs. Besides, it's my Blog.What are we going to do with these EDI messages? Possibilities include,Print them out in human readable formCovert them into an email alertStore them for </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/3516935484080710550'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/3516935484080710550'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2007/12/edi-system-design-part-iii-import.html' title='EDI System Design Part III - Import Mapping'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-3647692969765453225</id><published>2007-11-27T23:34:00.000Z</published><updated>2007-11-27T23:46:40.027Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='pigeon'/><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='gov'/><category scheme='http://www.blogger.com/atom/ns#' term='story'/><title type='text'>Is this what hm.gov.uk thinks is EDI?</title><summary type='text'>Electronic Data transfer in the news. I think it is called pigeon protocol.No, you can't ridicule it because it is too serious. Unfortunately I suspect this "behind the mailbox" infrastructure is all too common.I hope the little I.T. guy archives his email.</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/3647692969765453225'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/3647692969765453225'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2007/11/is-this-what-hmgovuk-thinks-is-edi.html' title='Is this what hm.gov.uk thinks is EDI?'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-4807117774716030343</id><published>2007-11-17T08:22:00.001Z</published><updated>2008-08-15T00:57:51.831+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='mapping'/><title type='text'>EDI System Design Part II - Export Mapping</title><summary type='text'>I'm not going to go into the details of creating the text of EDI (Electronic Data Interchange) messages in certain formats. Well not in this post anyway. It is a big subject and the last post was long enough. What I am trying to do is lay out the System Design and APIs.So you have a routine in your ERP system that created a document or a transaction e.g. a Sales Invoice. The options you have are,</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/4807117774716030343'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/4807117774716030343'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2007/11/edi-system-design-part-ii-export.html' title='EDI System Design Part II - Export Mapping'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-2457749836668551705</id><published>2007-11-13T23:40:00.001Z</published><updated>2008-08-15T00:59:17.265+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='transactions'/><title type='text'>EDI System Design Part I - Message Control</title><summary type='text'>Assuming you have an ERP system that processes sales orders, invoices, remittances, stock balances etc. how do add EDI (Electronic Data Interchange) capabilities? The first thing we need is to decide what is going to whom, in what format, by what means.Let us suppose we want to start sending Sales Invoices to a key customer. The routine that will create the EDI invoice could be called from the </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/2457749836668551705'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/2457749836668551705'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2007/11/edi-system-design-part-i-message.html' title='EDI System Design Part I - Message Control'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-1500641927468028517</id><published>2007-11-08T21:50:00.001Z</published><updated>2008-08-15T00:59:39.145+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='story'/><title type='text'>EDI Assumptions</title><summary type='text'>I was starting to sketch out my next post. It was going to be on EDI (Electronic Data Interchange) System design and I started with "Assuming you have an ERP system that processes sales orders, invoices, remittances, stock balances etc. how do add EDI capabilities?"Then I thought wait!!! Important EDI life experience lesson - assume nothing!!!EDI has a wide reach. It is used in all sorts of areas</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/1500641927468028517'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/1500641927468028517'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2007/11/edi-assumptions.html' title='EDI Assumptions'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-1449093275732891155</id><published>2007-11-07T20:46:00.001Z</published><updated>2008-08-15T00:59:58.134+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='story'/><category scheme='http://www.blogger.com/atom/ns#' term='orders'/><title type='text'>Story from the Trenches</title><summary type='text'>I'm working at this company. No one wanted to be responsible for EDI (Electronic Data Interchange). It was seen as a problem (not a solution), so it gets dumped on the new guy - me.With a lot of patience and time I slowly train myself and begin to understand. I had inherited a third party communication and translation software. It used 1 of only 2 modems in the entire company - it was along time </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/1449093275732891155'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/1449093275732891155'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2007/11/story-from-trenches.html' title='Story from the Trenches'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-1250574440913191235</id><published>2007-11-06T21:26:00.001Z</published><updated>2008-08-15T01:00:18.764+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='transactions'/><title type='text'>Overview Part III - Why EDI? (or, What to do with EDI Messages)</title><summary type='text'>How is all this beneficial? How is it better than faxing or emailing a word attachment? In a human sense it isn't. The EDI (Electronic Data Interchange) formats are often not human readable (e.g. Edifact, Tradacom). The point is, it is meant to be machine readable.Eh? So what? These days we have grown used to unstructured information but it wasn't always the way. The triumph of HTML (and the </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/1250574440913191235'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/1250574440913191235'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2007/11/overview-part-iii-why-edi-or-what-to-do.html' title='Overview Part III - Why EDI? (or, What to do with EDI Messages)'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-1589986928788331753</id><published>2007-11-05T23:43:00.001Z</published><updated>2008-08-15T01:00:45.255+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='comms'/><title type='text'>Overview Part II - Communication</title><summary type='text'>Communicating... sending and receiving electronic messages... ummm... sounds like email!We all understand email and are familiar and comfortable with the concept of email. Then why is EDI (Electronic Data Interchange) more complicated? Well I think part of the answer lies in its age. EDI has been in wide spread use in business longer than email. The other reason may be down to security concerns, </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/1589986928788331753'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/1589986928788331753'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2007/11/overview-part-ii.html' title='Overview Part II - Communication'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-2491012923126127765</id><published>2007-11-04T23:46:00.001Z</published><updated>2008-08-15T01:01:14.501+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><category scheme='http://www.blogger.com/atom/ns#' term='formats'/><title type='text'>Overview Part I - Formats</title><summary type='text'>There are 4 elements to EDI (Electronic Data Interchange).Composing a message Sending a message Receiving a message Processing a messageSteps 1 &amp; 4 are sometimes refered to as "translating" or "mapping". Steps 2 &amp; 3 are the communication.By translating you take a document on your computer system, say an order or an invoice, and convert it into another format. Or you take a document that someone </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/2491012923126127765'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/2491012923126127765'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2007/11/there-are-4-elements-to-edi.html' title='Overview Part I - Formats'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-503554439506827322.post-8816822564361672240</id><published>2007-11-04T23:43:00.001Z</published><updated>2007-11-10T09:05:23.800Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='all'/><title type='text'>Welcome</title><summary type='text'>EDI - Electronic Data Interchange. Do those letters fill you with dread? They seem to frighten a lot of people I know and they really shouldn't. After too long learning much more than I ever wanted, I now realise what I wish I'd known at the start. However the information just wasn't out there. I am going to try and bring things together on this site.I hope you find it informative.</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/8816822564361672240'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/503554439506827322/posts/default/8816822564361672240'/><link rel='alternate' type='text/html' href='http://myediblog.blogspot.com/2007/11/welcome.html' title='Welcome'/><author><name>EDI Eddy</name><uri>http://www.blogger.com/profile/10667733779073828630</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry></feed>
