The real reason that XML is used is for readability...to the layperson.  
The rest of us learned how to read X12
at an early age.  And the first thing we usually do is rip the data 
elements out and throw away the rest - either
as a translation step or a database load.  You don't see the XML tags in 
Oracle, do you?  Compared to legacy
flat files and idocs, XML is a kinder, gentler 
<underline>normalized</end of underline> format.

Daniel L. Mehlhorn wrote:
> Group,
>
>  
>
>             A factor of 10 is conservative.  I really don't have the
> words to express the bloat in document size when a 3rd party
> "translates" documents into XML EDI for companies.  It is a horror show.
>
>  
>
> Dan Mehlhorn
>
> System Programmer/EDI Administrator
>
> Crescent Electric Supply Co.
>
>  
>
> ________________________________
>
> From: James Hatcher
> Brian is correct, the legacy investment makes X12 (and EDIFACT overseas)
> the most prevalent EDI formats. This isn't changing anytime soon. Be
> sure you aren't being influenced by a solution vendor who can do XML but
> doesn't have a strong X12 capability. 
>
> General Question: 
> Isn't one of the challenges of XML vs. X12 is that X12 is actually more
> efficient for file size in transmission? Since VAN's always charged per
> KB and it wasn't cheap X12 does a good job of compacting messages vs.
> XML tagging which can increase the size of the same message by more than
> a factor of 10. VAN or internet you still want to have minimum data
> volumes during transmission. XML is great for tagging content within web
> pages for search and reference but when you already have a structured
> message format with defined fields it doesn't add much value. Converting
> the data to HTML after transmission is easy as it has structure. 
>
> J Hatcher
>
>
>
>
>
>
>
>
> The information contained in this communication is 
> confidential, private, proprietary, or otherwise privileged
> and is intended only for the use of the addressee. 
> Unauthorized use, disclosure, distribution or copying is 
> strictly prohibited and may be unlawful. 
> If you have received this communication in error, 
> please notify the sender immediately.
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ...
> 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
>
>
>
>
>   

-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Brian Lehrhoff, EA ([EMAIL PROTECTED])
Messaging Consultant  201-913-4506

Upgrade your Quickbooks for 20% off at http://ea.brianlehrhoff.com
Circular 230 Notice is located at http://ea.brianlehrhoff.com/230notice.html
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%



...
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