RE: [ebxml-dev] ebXML specifications interdendancies

["Anarkat, Dipan" <DAnarkat@uc-council.org>]

Hi all,
   Gosh .... the subject which started this email thread should have been
 "ebXML specifications Interdependancies"
   I am surprised nobody reported the typo with the last word. 

My apologies to everyone !

Regards

+ Dips

-----Original Message-----
From: Martin W Sachs
To: Dan Weinreb
Cc: Anarkat, Dipan; paechoi@earthlink.net; stefano.pogliani@sun.com;
ebxml-dev@lists.ebxml.org
Sent: 12/6/2001 3:01 PM
Subject: Re: [ebxml-dev] ebXML specifications interdendancies


There is no negotiation specification at this time. Anyone OASIS member
who
wants to join the negotiation subteam, let me know.

As to " how do I use it
without getting locked down into a propreitory messaging solution from
vendor  , until ebXML addresses it in the standard ?",
the answer is that you wait for a standard or be proactive in creating a
standard.

Extensibility means that it facilitates extension of the standard, not
that
everyone is free to add his own extensions.

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



Dan Weinreb <dlw@exceloncorp.com> on 12/06/2001 01:01:24 PM

Please respond to "Dan Weinreb" <dlw@exceloncorp.com>

To:    DAnarkat@uc-council.org
cc:    paechoi@earthlink.net, Martin W Sachs/Watson/IBM@IBMUS,
       stefano.pogliani@sun.com, ebxml-dev@lists.ebxml.org
Subject:    Re: [ebxml-dev] ebXML specifications interdendancies



   Date: Thu, 6 Dec 2001 12:52:32 -0500
   From: "Anarkat, Dipan" <DAnarkat@uc-council.org>

   The "ebCPA handler" module I assume would address CPA negotiation.

Oh, I see.  Yes, that would indeed really be a separate module.

If you then wanted to buy a CPA negotiator module from one vendor and
an MSH from another vendor, it might be that the only thing you need
for them to interoperate reasonably would be the CPA spec itself.
(You might need more if you wanted "smoother" integration,
e.g. something to automatically "pick up" the CPA produced by the
negotiator and put it where the MSH expects to find it, or something
like that.)

      Well my whole confusion is, when ebMS can be customised/extended
to
   have
   additional messaging features (using SOAP extensions), how do I use
it
   without getting locked down into a propreitory messaging solution
from
   vendor  , until ebXML addresses it in the standard ?

I'm not sure I understand properly to what extent the ebMS protocol
considers itself to be extensible like this.  I have not seen much (in
fact, not any, I think) discussion of trying to run ebMS with
extensions that are not part of the ebMS standard.

          I am trying to
   understand how our existing users (EAN.UCC members) most of which use
   EDI-INT AS2 as the TR&P protocol can use our standards along with
ebBPSS
   (
   and maybe ebCPA ) without having to use ebMS and having to break
   existing
   infrastructure.

Since AS2 is already taking care of so many things for you, you will
probably find that a good portion of what the CPA deals with isn't
relevant.  BPSS, on the other hand, I would think would be no problem.
It seems to me that BPSS is pretty much layered on top of the MS and
CPA concepts, and could be used with an alternative pretty
transparently.