From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: * X-Spam-Status: No, score=1.6 required=5.0 tests=BAYES_05,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,89a7c6bc348eba8a,start X-Google-Attributes: gid103376,public From: Marin David Condic Subject: UN/EDIFACT Communication standard. Date: 1999/03/24 Message-ID: <36F9104E.3CFB1230@pwfl.com>#1/1 X-Deja-AN: 458427399 Content-Transfer-Encoding: 7bit Sender: condicma@bogon.pwfl.com Content-Type: text/plain; charset=us-ascii Organization: Pratt & Whitney Mime-Version: 1.0 Reply-To: diespammer@pwfl.com Newsgroups: comp.lang.ada Date: 1999-03-24T00:00:00+00:00 List-Id: I sort of stumbled on this communication standard called EDIFACT and I'm wondering if anybody has any experience with it? http://www.unece.org/trade/untdid/welcom1.htm My curiosity is along these lines: 1) Is this standard in some way in wide usage or are there more widely accepted standards? 2) Has anybody implemented record types, packages or other subsystems that provide any level of reusable implementation of this standard (or parts of it)? 3) The on-line document is - to say the least - confusing. Is there any sort of simplified, distilled, "EDIFACT For Dummies" document that might do something like show a simple record layout? (After glancing at some of the message definitions, I couldn't seem to get to the point where someone was saying something like "A date field will occupy 8 bytes - four bytes for year, two bytes for month, two bytes for day...." The info may be in there somewhere, but I got tired of digging.) MDC -- Marin David Condic Real Time & Embedded Systems, Propulsion Systems Analysis United Technologies, Pratt & Whitney, Large Military Engines M/S 731-95, P.O.B. 109600, West Palm Beach, FL, 33410-9600 ***To reply, remove "bogon" from the domain name.***