At 02:18 PM 8/2/2005 -0700, Ricardo Johnson wrote:

>Not only is the idea of 'certification' by a private consultant/group 
>completely absurd, but the whole ASx standard itself is highly 
>questionable: Why would you want to wrap EDI envelopes with MIME 
>envelopes, secure them with S/MIME (thus encryting EDI IDs and 
>qualifiers), and acknowledge receipt of MIME evelopes (disrigarding their 
>EDI content), when you can accomplish all that and much more with EDI 
>security (X12.58 or EDIFACT) and acknowledgements. EDI security allows for 
>fully secured and acknowledged exchanges (acknowledging EDI content and 
>conformance) regardles of the communications media and protocol (because 
>EDI IDs and qualifiers are left unencrypted).

I don't think we're going to get anywhere in this if we try to broaden the 
issues very much.  Many of the major hubs have already signed on to EDIINT 
AS2 or AS3.  Trying to get them to budge off of that, rather than just drop 
the onerous certification requirements, is a much steeper hill to climb.


>I don't know whether Drummond has any international acceptance or 
>compliance (other than Wal-Mart). But EDI security is used extensively in 
>Finance, Customs, and Invoicing in Canada, Latin America, Australia, 
>Europe and Asia. Even most US Banks have been using X12.58 for years. EDI 
>security has no cost for 'certification' and the technology is better 
>suited for EDI transactions. Perhaps volume and competition could make it 
>much less expensive than ASx.

I wouldn't hold my breath.  X12.58 has been out there, but is used very 
little.  In addition, I don't think anyone is going to be very interested 
in using it for UN/EDIFACT.

>So, why re-invent the wheel only to come up with a less efficient version? 
>You may want to ask the Drummond Group. You may also want to ask them why 
>the $60K initial + $25K/year fees ?

To pay for Rik's boat slip?

At the very least, I'm glad to see that the work is finally progressing 
through IETF.  It looks as if AS2 has finally reached RFC status (see 
http://www.ietf.org/rfc/rfc4130.txt).  Maybe after becoming a *real* IETF 
standard the concern about certification will diminish.

Mike


---------------------------------------------------------------
Michael C. Rawlins, Rawlins EC Consulting
www.rawlinsecconsulting.com
Using XML with Legacy Business Applications (Addison-Wesley, 2003)
www.awprofessional.com/titles/0321154940



------------------------ Yahoo! Groups Sponsor --------------------~--> 
<font face=arial size=-1><a 
href="http://us.ard.yahoo.com/SIG=12h5k4h3g/M=362131.6882499.7825260.1510227/D=groups/S=1705005582:TM/Y=YAHOO/EXP=1123176556/A=2889191/R=0/SIG=10r90krvo/*http://www.thebeehive.org
">Get Bzzzy! (real tools to help you find a job) Welcome to the Sweet Life 
- brought to you by One Economy</a>.</font>
--------------------------------------------------------------------~-> 

.  
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Access the list online at:  http://groups.yahoo.com/group/EDI-L
 
Yahoo! Groups Links

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

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