Dale, the ebXML MS vs. EDI-INT issue has been discussed on the WEDI SNIP Security Workgroup List - not here on the Transactions Workgroup List. The Security listserve is where you proffered your opinion on the relative merits of ebXML MS, at http://www.mail-archive.com/wedi-security%40lists.wedi.org/msg00147.html
I still don't know how you reach your "unavoidable conclusion" - or even really what that conclusion is. More goes into the decision (which to use) than merely the technical superiority of ebXML MS over that of EDI-INT - especially current market penetration. I welcome you to further illuminate us by continuing the discussion on the WEDI SNIP Routing Subworkgroup List. Please go to http://subscribe.wedi.org/ and subscribe to the WEDI SNIP Routing Subworkgroup List. Archives for the ID & Routing mailing list reside at http://www.mail-archive.com/wedi-routing%40lists.wedi.org/; older archives (before WEDI switched over to the new listserves) are at http://www.mail-archive.com/routing%40wedi.org/. William J. Kammerer Novannet, LLC. Columbus, US-OH 43221-3859 +1 (614) 487-0320 ----- Original Message ----- From: "dale pocklington" <[EMAIL PROTECTED]> To: "WEDI SNIP Transactions Workgroup List" <[EMAIL PROTECTED]> Sent: Saturday, 08 March, 2003 01:11 AM Subject: Re: EDIINT best practices workgroup I have followed this from day 1. (on this listserv) I find the facts as they really exist point to an unavoidable conclusion. I strongly suggest that anyone out there that is considering a movement forward in technology just do your own objective research, won't take much...and decide for yourself. Dale W. Pocklington, MS, MHA, CISSP, CDIA, CCA ----- Original Message ----- From: "William J. Kammerer" <[EMAIL PROTECTED]> To: "WEDI SNIP Transactions Workgroup List" <[EMAIL PROTECTED]> Sent: Friday, 07 March, 2003 08:14 AM Subject: Re: EDIINT best practices workgroup Tony, there has been no "debate" on the WEDI SNIP Transactions Workgroup List about ebXML [MSH] vs. EDI-INT AS2. Discussions on transport protocols belong on the WEDI SNIP Routing Subworkgroup List, or perhaps on the WEDI SNIP Security Workgroup List where the ebXML vs. EDIINT "debate" actually took place. The ebXML MSH and EDI-INT AS2 specifications are not security protocols, per se. They are interoperable standards for the exchange of business documents, which happen to support payloads that can be encrypted and authenticated. "Interoperation" is key: any program implementing either of these standards can "talk" via the Internet to any other vendor's program which supports the same standard. Both partners, the sender and the receiver, can be authenticated using X.509 digital certificates. Both standards provide elaborate acknowledgement processes so either end can be assured that the message was successfully transported and decrypted. I suppose the "debate" centered around the "push" of AS2 vs. the "push-pull" of ebXML MSH. This may be a rather fine point; any entity that can support AS2 is ahead in the game anyway in that they can support real-time EDI over the Internet in a standard, interoperable fashion. The ebXML MSH standard may be "better" - but it's probably only a matter of time when most vendors' AS2 offerings also support ebXML MS. This would make the "debate" moot: if the sender's program detects the trading partner can support the more robust transport protocol, it can automatically select the "better" method for that exchange. Obviously, the advantage of interoperable standards is that they can be easily implemented in an automated, "lights-out" operation. This is difficult - if not impossible - to do with your SSL HTTP/S upload function, for example. Each payer could potentially have a different way of authenticating the sender and doing the upload. An automated "screen-scraper" would have to "learn" each payer's way of doing the submission - akin to the drag Direct Data Entry (DDE) puts on Administrative Simplification. Combining the HIPAA X12 and NCPDP standards with interoperable real-time protocols for transport, packaging and security, like EDI-INT AS2 and ebXML MSH, will go a long ways in ushering in an era of frictionless e-commerce. William J. Kammerer Novannet, LLC. Columbus, US-OH 43221-3859 +1 (614) 487-0320 --- The WEDI SNIP listserv to which you are subscribed is not moderated. The discussions on this listserv therefore represent the views of the individual participants, and do not necessarily represent the views of the WEDI Board of Directors nor WEDI SNIP. If you wish to receive an official opinion, post your question to the WEDI SNIP Issues Database at http://snip.wedi.org/tracking/. These listservs should not be used for commercial marketing purposes or discussion of specific vendor products and services. They also are not intended to be used as a forum for personal disagreements or unprofessional communication at any time. You are currently subscribed to wedi-transactions as: [EMAIL PROTECTED] To unsubscribe from this list, go to the Subscribe/Unsubscribe form at http://subscribe.wedi.org or send a blank email to [EMAIL PROTECTED] If you need to unsubscribe but your current email address is not the same as the address subscribed to the list, please use the Subscribe/Unsubscribe form at http://subscribe.wedi.org
