OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-cppa-negot message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: [ebxml-cppa-negot] Some comments from Dale Moberg






Following are some comments from Dale Moberg

December Comments on Negotiation Draft 0.02 12/09/2002 version. Line
numbers from pdf.

Line 225 Versioning should adhere to the conventions in the CPPA as closely
as possible. Because multiple xsds are involved, however, we will need to
allow each to undergo versioning. A matrix that maintains compatibility
info may be needed relating the BPSS for negotiation, NCPA variants,
Messaging xsd, NDD xsd.

Line 358 “In order to negotiate parties have to establish NCPA”

I would prefer that we only say that parties behave as if a NCPA is in
place.
That is, the NCPA can very well be virtual. So establishing a NCPA is not
required for negotiation, and I would prefer to have this wording altered.
We should leave room for both a HTTP POST or SOAP 1.1/1.2 bindings for the
messages exchanged. We should leave room for WSDL descriptions of the
message exchanges construed as services also.
In fact, I would favor having a non-normative appendix with a WSDL for
negotiation eventually.

Line 374- 375 Exchange and deploy before sending draft CPA.

Again I would prefer to say that NCPA needs to be only virtually present.
Successful negotiation (using interoperable conventions) will normally
reflect
Obtaining the endpoint may be done out of band or by some discovery
technology such as ebXML Registry or UDDI or …


Line 574 NCPA instance document checked. Hima said some simple parts
missing. I do not think we have documented both async and sync messaging
patterns for negotiation.

Line 594 NamespaceSupported element -- omit or require issue is raised
here.

Line 603 Syncreply mode in NCPA? Very ebMS specific? We have to be careful
to allow  various messaging and transfer protocol bindings and initially
pick one as a default and others as optional. HTTP POST default? SOAP 1.1
default?

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

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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC