Re: T2 Non repudiation and MSG, CPP/A, BPSS spec alignment

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

The information that we have been discussing is not an instance of a CPP.
An instance of a CPP is how a party advertises its IT capabilities.  The
information we have been discussing is local configuration information.  It
is strictly the business of one party and is of no interest to other
parties communicating with that party.  It may exist once for all trading
relationships or perhaps once for each distinct BPSS instance document that
the party  supports.  In any case, it is local to that party and does not
go into a CPP or CPA.

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



"Martin Bryan" <mtbryan@sgml.u-net.com> on 09/07/2001 09:28:22 AM

To:   Martin W Sachs/Watson/IBM@IBMUS, "David RR Webber - XMLGlobal"
      <Gnosis_@compuserve.com>
cc:
Subject:  Re: T2 Non repudiation and MSG, CPP/A, BPSS spec alignment



Martin

>The "almost" is this:  I would not want to
> call this local configuration document an "extension to the CPP" because
> that information is internal to each party

Why isn't it an "instance of a CPP"?

Martin Bryan