In realty, neither EDIFACT or X12 syntax is superior to the other. Both are
compressed formats, tagged segments, delimited and positional data elements.
In general, the development philosophy for EDIFACT-based messages is one of
using generic data elements modified by codes to specify semantic meaning.
On the other hand, the X12 standards development philosophy is more a mix of
very specific semantically defined data elements **and** generic data
elements modified by codes to specify semantic meaning.

Regardless of whether EDIFACT messages or X12 transaction sets, it's darn
near impossible to implement the standard message or transaction set without
a trading partner-specific implementation guide.

So, fundamentally, it's an apples to apples comparison - just different
types of apples.

Rachel Foerster

Senior CAQH/CORE Consultant
Boundary Information Group 

Rachel Foerster & Associates Ltd.
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
www.rfa-edi.com

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of JOHN
KAESS
Sent: Thursday, September 04, 2008 1:30 PM
To: Chill; [email protected]
Subject: Re: [EDI-L] Which do you prefer, X12 or EDIFACT?

In the beginning...Prior to EDI-L...When the EDIFACT standards development
started this same discussion occurred.  The original concept was that X12
was for domestic exchange and EDIFACT was for international exchange.  It
never developed this way as X12 was used for international as well as
domestic, and EDIFACT was used for domestic and international.  The reality
is that if a trading partner requires either one the pressure is there for
you to comply with their wishes.  In the end you will possibly still be
using both types of standards for exchange of data.

        John D. Kaess


------------------------------------

...
Please use the following Message Identifiers as your subject prefix:
<SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work: <JOBS>
IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links





------------------------------------

...
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work: <JOBS> IS 
REQUIRED in the subject line as a prefix.Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/EDI-L/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/EDI-L/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[EMAIL PROTECTED] 
    mailto:[EMAIL PROTECTED]

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Reply via email to