Re: [ebxml-dev] Re: [EDI-L] Announce - Latest Article on ebXML

[Martin W Sachs <mwsachs@us.ibm.com>]

Mike,

Regarding: "is covered by the BPSS, which is only pointed to by the CPA/CPP
and is
not an integral part of the CPA or the CPP." The CPP and CPA contain what
amounts to a normative reference to a BPSS instance document. That makes
the BPSS instance document just as integral a part of the CPP/CPA as the
element in the CPP/CPA that points to it.  The BPSS instance document has
the job of defining the choreography of the message exchanges.  Without it,
we would have had to invent one to embed in the CPA (or to use the
choreography that came with tpaML).

Regards,
Marty

*************************************************************************************

Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287;  IBM tie line 863-7287
Notes address:  Martin W Sachs/Watson/IBM
Internet address:  mwsachs @ us.ibm.com
*************************************************************************************



Mike Rawlins <mike@rawlinsecconsulting.com> on 11/26/2001 11:05:32 PM

Please respond to mike@rawlinsecconsulting.com

To:    "William J. Kammerer" <wkammerer@novannet.com>
cc:    edi-l Yahoo List <EDI-L@yahoogroups.com>, ebxml-dev
       <ebxml-dev@lists.ebxml.org>
Subject:    [ebxml-dev] Re: [EDI-L] Announce - Latest Article on ebXML



Thanks for the kind comments, William.  A few replies inserted below.

"William J. Kammerer" wrote <snipped>:

>
> If SOAP is not a
> direct competitor to ebXML MS, maybe W3C's nascent XML Protocol -
> described at http://www.w3.org/2000/xp/ -  could be.  In any event,
> something like ebXML Messaging services will be needed to provide the
> business messaging transport framework for the "digital dial tone" Mike
> mentions.  My alternate prediction is that either one or the other
> (ebXML MS or XML Protocol) will have a Gartneresque probability of
> achieving critical mass of .8.

Perhaps I generalize too much  in identifying SOAP with W3C's XML Protocol
work, but
if you review the public work on the cited page you can certainly come away
with that
impression.  I agree with William's assessment of .8 for one or the other,
I just
think it's much more likely to be the W3C product.

>
> But there are lots of occasions for two known trading partners to want
> to automate mundane agreements.  For example, on the EDI-L list in just
> the last few weeks we've heard people asking what the ISA14 was for, and
> it ends up it has nothing to do with the X12 997 functional
> acknowledgement whose use depends on out-of-band Trading Partner
> agreement(s).  And we had the issue of the business response to a
> UN/EDIFACT INVOIC message: wouldn't it be nice if one could advertise
> (in the CPP) their ability to automate remittance advices, so their
> trading partners could automatically ask for one if they were capable of
> handling it?   The rough analog of all this - and more - is built into
> the ebXML CPP/CPA specification!  Mike gives the CPP/CPA spec a
> probability of achieving critical mass of .2;  I'll say it's closer to
> .5 or .6.

A few clarifications:  In the ebXMLBinding element there are rough
analogues to the
ability to request a 997 or TA1.  However, the issue of a business response
to the
INVOIC message is covered by the BPSS, which is only pointed to by the
CPA/CPP and is
not an integral part of the CPA or the CPP.

>
> This is why
> Rachel and I have to sit in the corner all alone, wearing our dunce hats
> with gum on our noses.
>

Let me publicly go on the record here as saying that although I've seen
both Rachel
and William sitting in corners alone, I have *never* seen them wearing
dunce hats or
with gum on their noses!  (or did I miss that party?  You guys in RegRep
must have had
a lot more fun than we did in Requirements...)

--
Michael C. Rawlins, Rawlins EC Consulting
www.rawlinsecconsulting.com



----------------------------------------------------------------
The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.ebxml.org/ob/adm.pl>