"??? Question for the group. Could you build a webservice, API (whatecer you

want to call it) for your application, which might receive EDI messages to 
be transformed to XML for application integration? Do I make sense? i know 
what I mean, just not sure if I use the right words."

Sounds like MS Biztalk...definately stuff like that going on...

Stace

-----Original Message-----
From: Eric Dawson [mailto:[EMAIL PROTECTED]] 
Sent: Monday, June 10, 2002 3:07 PM
To: CF-Talk
Subject: Re: Help with EDI formats


I offer no help. just curious. I did do a little EDI work for a cargo 
airline, we were a startup and built our network to support cargoimp 
messages for booking space on the aircraft and tracking cargo shipments etc.

What's the application?

What types of EDI communications are you going to receive?

I would imagine you would start at the top and work your way down, 
developing, testing and implementing each message type that you might 
send/receive.

How are you going to receive the EDI requests?

Is there an industry standard message definition?

Is this to support a traditional component of client support? (meaning are 
they already sending/receiving EDI messages?) Do they have an internal 
legacy system that communicates using EDI?

??? Question for the group. Could you build a webservice, API (whatecer you 
want to call it) for your application, which might receive EDI messages to 
be transformed to XML for application integration? Do I make sense? i know 
what I mean, just not sure if I use the right words.

ie you expose your application with a basic XML based API. defining 
inputs/outputs. Publish your API. Next step to define how the EDI messages 
map/transform to your API. I think this way, since it seems the current 
method of "interchange" would be viw web services, or some sort of web based

XML API (not sure if the two are synonomous). EDI generically is legacy 
method of handling interchange between systems. Once you've defined an API, 
you could easily create some sort of EDI catcher which translated for the 
API.

Just curious and thinking aloud, hoping to learn more,
Eric

From: Tony Schreiber <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: CF-Talk <[EMAIL PROTECTED]>
Subject: Help with EDI formats
Date: Mon, 10 Jun 2002 14:28:21 -0400 (EDT)

Ok, I have a requirement to add some EDI functionalilty into a system we
already use (and that I built), but after receiving the EDI specs from the 
vendor, I'm afraid I don't know what EDI means...

The specs talk about loops and HL loops and whatnot. WTF??? Any pointers or
primers? I had thought it was just text files. Now I don't know... Positions
and Segments, oh my.

Tony Schreiber, Senior Partner                  Man and Machine, Limited
mailto:[EMAIL PROTECTED]                   http://www.technocraft.com

http://www.simplemessageboard.com ___Free Forum Software for Cold Fusion
http://www.is300.net ___________The Enthusiast's Home of the Lexus IS300
http://www.digitacamera.com ______________DigitA Camera Scripts and Tips
http://www.linklabexchange.com _____________Miata Link ECU Data Exchange


______________________________________________________________________
Signup for the Fusion Authority news alert and keep up with the latest news in 
ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to