Subject: RE: initial draft of CPP-CPA Specification
Stefano,
I mostly agree with everything in this email. I have embedded a couple of
comments below.
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
*************************************************************************************
Stefano POGLIANI <stefano.pogliani@sun.com> on 01/19/2001 05:57:00 PM
To: Martin W Sachs/Watson/IBM@IBMUS
cc: ebxml-tp@lists.ebxml.org, ebxml-ta-security@lists.ebxml.org
Subject: RE: initial draft of CPP-CPA Specification
Marty
here are my comments to your comments...Thanks a lot for and best
regard
/Stefano
Line 83:
I agree with your note.
Line 88:
I agree (I think that in my comment I meant CPP instead that
CollaborationProtocol...
apologies)
Line 100:
Yes I am meaning "interacting".
But the goal of this comment is to "introduce the idea of the CPA
serving
as
a configuration tool".
Line 119:
I agree. I just wanted to say that if TPP is used, it should be put as
a
background...
Line 334:
are you meaning that, in your wording, "business application
functions" is
the
merge of the ebXML-middleware (which is aware of the collaboration)
and of
the actual back-end systems (the legacy applications currently used by
the
customer) ?
If this is true, I have the following comments:
"The Collaboration-Protocol layer is the interface between the
CPA-defined business transactions and the business-application
functions
that actually perform the business transactions"
The "business transactions" are actually performed by the legacy
applications,
aren't they?
MWS: True. However there will be new applications defined by the BP model
and those
won't need any bridge between the collaboration function and the higher
level application
function.
The "CPA-defined business transactions" are the choreography
of the actual business transactions that are executed by the legacy,
am I
wrong?
MWS: This is what the Specification Schema will provide, so I agree.
So, I interpreted the "Collaboration-Protocol layer" as the layer
which is
in
charge of "instructing" the legacy about which business transaction
should
be executed. In my interpretation, this layer is dinstinct from the
legacy.
MWS: I agree for legacy applications. The bridge to the legacy is where
the
choreography will be executed.
Line 542:
Ok.
I would have preferred "..is THE combination of A TLayer ...", but I
do not
have any objection to "...is A combination of A TLayer..."
Line 542 and 543:
I agree with you, but I posted the comment since communication
addresses
and
security are immediately mentioned at line 549 as a way to
differentiate
delivery channels.
Line 650 to 660.
I am not convinced on the second comment on multipurpose.
I think that the "allPurpose" is different that "request + response".
I think that an example would make it clearer.
MWS: I agree about an example. My point was only that architecturally,
omitting
the type attribute declares that the endpoint does not have a specific
function.
"allPurpose" is only an innocuous character stream put into the DTD to
satisfy
the XML architecture with regard to omitting the attribute. (You must
declare a
default to be able to omit the attribute.)
» -----Original Message-----
» From: Martin W Sachs [mailto:mwsachs@us.ibm.com]
» Sent: 19 January 2001 23:16
» To: Stefano POGLIANI
» Cc: ebxml-tp@lists.ebxml.org; ebxml-ta-security@lists.ebxml.org
» Subject: RE: initial draft of CPP-CPA Specification
»
»
»
»
» Stefano,
»
» Thank you very much for your comment set. If I do not reply to a
» particular comment, it means that I agree. Responses are embedded in
this
» copy of your comment set.
»
» My replies are embedded in the attached copy of your comments.
»
» To all: most comments that you supplied so far will be processed AFTER I
» complete and distribute the initial draft of the CPA chapter.
»
» Regards,
» Marty
»
»
» (See attached file: response-stefano.html)
»
» ******************************************************************
» *******************
»
» 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
» ******************************************************************
» *******************
»
»
»
» Stefano POGLIANI <stefano.pogliani@sun.com> on 01/17/2001 09:37:58 AM
»
» To: ebxml-tp@lists.ebxml.org, ebxml-ta-security@lists.ebxml.org
» cc:
» Subject: RE: initial draft of CPP-CPA Specification
»
»
»
» Please disregard the previous mail since the attachment was poorly
» formatted!
» ==================================================================
» ==========
»
» ==
» Attached you will find my comments on the document.
» Please do not hesitate to contact me for clarifications on my comments.
»
» Best regards and congratulations for the excellent job!
»
» /Stefano
»
» » -----Original Message-----
» » From: Martin W Sachs [mailto:mwsachs@us.ibm.com]
» » Sent: 15 January 2001 23:11
» » To: ebxml-tp@lists.ebxml.org; ebxml-ta-security@lists.ebxml.org
» » Subject: initial draft of CPP-CPA Specification
» »
» »
» » I have attached the initial version of the CPP-CPA specification. As
» » previously indicated to the TP team, this copy has the CPP chapter but
» not
» » the CPA chapter. Please review the CPP chapter while I am
» completing the
» » CPA chapter. Please post comments and be prepared to discuss at
» » Wednesday's conference call.
» »
» » Regards,
» » Marty
» »
» » (See attached file: cpa-cpp-spec-0.1-interim.pdf)
» »
» » ******************************************************************
» » *******************
» »
» » 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
» » ******************************************************************
» » *******************
» »
»
»
»
»
Powered by
eList eXpress LLC