[HN Gopher] Introducing UN/EDIFACT
       ___________________________________________________________________
        
       Introducing UN/EDIFACT
        
       Author : throwawaybutwhy
       Score  : 9 points
       Date   : 2021-05-23 08:11 UTC (14 hours ago)
        
 (HTM) web link (unece.org)
 (TXT) w3m dump (unece.org)
        
       | achoice wrote:
       | 15 years ago I worked with integrating services via IBM WebSphere
       | Message Broker. Big companies needed help mapping EDIFACT
       | messages to/from other formats. Interesting at first, mapping
       | hell after a while. Quite interesting format, see
       | https://en.m.wikipedia.org/wiki/EDIFACT And message specs
       | https://service.unece.org/trade/untdid/d20b/trmd/trmdi2.htm
       | 
       | USA use X12, similar thing.
        
       | i386 wrote:
       | I worked with this interchange format for a few years developing
       | customs brokerage and logistics software. There's like 50
       | different versions of the language when you count up official
       | EDIFACT revisions and some poorly implemented versions of it per
       | countries customs system. At one point there was even a XML
       | version but I don't think it caught on.
       | 
       | I once unintentionally broke a particular countries customs
       | system by sending the maximum number of messages in a single
       | interchange envelope. System was out for 3 days whilst shipping
       | containers couldn't be moved out of their major seaport. Still
       | amazed they had Christmas that year!
        
         | jiehong wrote:
         | In the airline industry, the xml version is still used and
         | alive!
         | 
         | Modern programming languages tend to have better libs to handle
         | xml than edifact, so that helps.
        
       ___________________________________________________________________
       (page generated 2021-05-23 23:01 UTC)