It seems clear from the comments provided that Cyclone Software (represented
by Dale Moberg and Gary Crough) and Rik Drummond oppose a single AS2
standard for exchanging EDI/XML data.
On the other hand we've heard from Andrew Strickland, Mike Costa, Steve
Lowery, Wayne Mackintosh, and myself who appear in favor of developing a
single AS2 standard for exchanging EDI/XML data.
I believe we must resolve this issue before we can move on and address the
deeper technical issues.
Based on the comments provided thus far, there appears to be more support
behind developing a single AS2 standard. However we've only heard from a
relatively small subset of the EDIINT community.
I believe more community input is needed to help the EDIINT workgroup decide
how to proceed - should the group develop one standard or multiple
standards to exchange EDI/XML data over HTTP?
Your opinions are important, please give the group the help it needs to make
the proper decision going forward.
Thanks,
Dick Brooks
Systrends, Inc
7855 South River Parkway, Suite 111
Tempe, Arizona 85284
Web: www.systrends.com <http://www.systrends.com>
Phone:480.756.6777,Mobile:602-684-1484,eFax:240-352-0714
-----Original Message-----
From: owner-ietf-ediint@xxxxxxxxxxxx
[mailto:owner-ietf-ediint@xxxxxxxxxxxx]On Behalf Of Gary Crough
Sent: Thursday, January 16, 2003 1:09 PM
To: ietf-ediint@xxxxxxx
Subject: Split within EDIINT: Multiple versions of AS2
All,
For some time now EDIINT has been split into AS1 and AS2. These
"subsets"
did not upset anyone. Why the uproar over a suggestion to create another
subset?
When UCC companies demand trading partners use EDIINT AS2 (and many do)
they mean the EDIINT "AS2" subset certified by the UCC ... AS2 using S/MIME
and compression options. But within the energy industry "AS2" means
PGP/MIME not S/MIME.
AS2 subsets already exist. The Energy industry (> 100 installations)
uses
one subset of EDIINT AS2 and the packaged goods, healthcare, financial, high
technology and transportation industries (> 1000 installations) uses
another; currently the two AS2 subsets are incompatible. Pretending
otherwise is creating considerable confusion in the user community.
Using Dale Moberg's proposed terms ...AS1, AS2 (UCC certified) and ASx
(PGP
version): there is no reason a vendor can't support EDIINT AS1, AS2 and ASx.
Such a vendor could claim to support all major subsets of EDIINT. Further,
such a vendor would create convergence ... enabling trading between
industries which standardized on different subsets.
With clear subsets within the EDIINT specification, there is no
requirement
for a small company like iSoft, the WalMart AS2 vendor, to support AS1 or
ASx since WalMart dictates UCC-certified AS2 interfaces.
Gary Crough
Cyclone Commerce, Inc.
8388 E. Hartford Drive, Scottsdale, AZ 85255
Office: 480-627-8780 Cell: 602-885-9010
|
