Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 May 2005 15:14:50 -0400
From:      "fbsd_user" <fbsd_user@a1poweruser.com>
To:        "Vizion" <vizion@vizion.occoxmail.com>, "Ian G" <iang@systemics.com>
Cc:        freebsd-java@freebsd.org, freebsd-questions@freebsd.org, dev@openoffice.org
Subject:   RE: [dev] Re: XML/EDI questions
Message-ID:  <MIEPLLIBMLEEABPDBIEGMEKMHFAA.fbsd_user@a1poweruser.com>
In-Reply-To: <200505250937.01060.vizion@vizion.occoxmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

EDI  stands for  electric data interchange.  It been in use by
mainframe systems for over 30 years now. Basically its an
international standard record format for exchanging purchase orders
and shipping information and the like between the suppliers and
manufactures in house proprietary applications. Wallmart/Sams stores
runs their complete business using it. Other big users is the rubber
tire industry and the automobile manufactures Ford, GM, for
just-in-time delivery of raw material, as well as the after market
auto suppliers. The EDI records format is available to any one who
wants to purchase the book from the non-profit organization who
maintains the standard. Like $35.00.  There are EDI software
providers like GE and Gentran who market mainframe applications that
convert the user's proprietary in-house record format to EDI format.
In the last 10 years these vendors have rewritten their mainframe
EDI application to run on ms/windows PCs. But you are correct in
that as far as I know there is no Unix flavored EDI applications out
there. EDI is not an server based type of application or for that
matter an internet transport user either. EDI utilizes dedicated
leased lines for maximum security. Cloning the functionality of one
of the ms/windows EDI desktop variety for an FreeBSD desktop version
should not be an big task. EDI is a specialized nitch market that
demands 24/7 technical support from the vendor as EDI in most cases
is mission critical to the company using it. This in its self makes
the case for an open source Unix flavored verson a hard sell to the
community who may want to use it.

Just my 2 cents


-----Original Message-----
From: owner-freebsd-questions@freebsd.org
[mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Vizion
Sent: Wednesday, May 25, 2005 12:37 PM
To: Ian G
Cc: freebsd-questions@freebsd.org; dev@openoffice.org;
freebsd-java@freebsd.org
Subject: Re: [dev] Re: XML/EDI questions


On Wednesday 25 May 2005 09:11,  the author Ian G contributed to the
dialogue
on Re: [dev] Re: XML/EDI questions:
& On Wednesday 25 May 2005 17:00, Vizion wrote:
& &
& > Oh there are now over 300 schemas for EDI's used extensively by
large
& > corporations for interchange. For example a major disk drive
manufacturer
& > used it for exchange between both supopliers and distributoes.
It used by
& > governement and hundreds if not thousands of large corporations.
The
& > oproblem is you have to pay thousands of dollars to get the
information
& > and/or off shelve software to benefit from this technology.
&
& Ah!  That explains why I've never come across it.  I
& stand corrected!  Thanks :)
&
Yep and the thing that really ****** me off is that there is a
standard for
these things and the only way you can get a copy is by paying $
(namny) for
it. My idea is there should be an open standard for these things
which could
be accessible by anyone and be used as a basis for exchange between
individuals and small businesses. Perhaps OpenSchemas.org!!

david


--
40 yrs navigating and computing in blue waters.
English Owner & Captain of British Registered 60' bluewater Ketch
S/V Taurus.
 Currently in San Diego, CA. Sailing May bound for Europe via Panama
Canal.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?MIEPLLIBMLEEABPDBIEGMEKMHFAA.fbsd_user>