Peter Ogden and Dale Moberg

Nov. 28, 2001

Attendees

Marty Sachs (IBM)

N Kartha (Sterling)

Jean Zheng (Vitria)

Kevin Liu (SAP)

Dale Moberg (Cyclone)

Peter Ogden (Cyclone)

Heiko Ludwig (IBM)

Bob Kearney (IBM)

Marty stated that we should only publish minutes of conference calls to the Negotiation list. Kartha will tentatively host conf calls for December. No calls on 12/12 or 12/26 due to conflicts (Marty and holidays).

Nov 6 whitepaper review, continued:

1.1, bullet 1: Marty reiterated that partner discovery is outside scope of this group. Negotiation begins, minimally with a CPA template from one of the parties.

1.1, bullet 2: Marty reiterated that we previously agreed that bootstrapping was doable, and mentioned that someone (Bernd Eckenfels [b.eckenfels@seeburger.de]) posted to CPPA group today with a pointer to a RegRep draft. Draft is about CPA bootstrap apparently.

1.1, line 70: Auto composition will be addressed.

1.1, line 73: Negotiation process will be defined. This will include both the BPSS process which expresses/defines the choreography of the negotiation process, and the messaging required to implement it. Marty suggested writing out the flow in text and bullets, then use some tool to generate the actual BPSS.

1.1, line 74: Agreed that we need to define what functions are normative, and what are optional.

1.1, line 76: Agreed we need to do the analysis regarding criteria for "easy" CPA negotiation.

1.1, line 79: WRT functions to be left to vendors as value-add, Marty suggested that, based on our lack of understanding of this requirement (not sure what "complex CPPs" are, etc.), it should be deleted, the group agreed.

1.1, line 83: For now, there will probably be only one negotiation business process. Dale pointed out that if we agree to use SOAP, SOAP faults could be used by either party to indicate that a particular negotiation capability is not supported. Also agreed that this requirement is covered under the "bootstrappable" one.

1.1, line 94: Agreed that Saito’s diagram is worth keeping/embellishing in the introduction. Dale raised a concern that the presence of an NCPA in this diagram may violate our requirement for bootstrapability. Kartha pointed out that negotiating the NCPA is an issue for the bootstrapping process, and we need to make sure we make it clear that the NCPA is "special" in that it doesn’t really have to be negotiated. Marty put these points about NCPA under the bootstrap section.

Marty renamed the Related Information section to References and moved it to the end of the document.

3.1 line 119: "Human still in the loop" means that protocol is reasonably complete, but allows for human interaction where necessary. Acknowledges that there is still some discomfort with letting non-humans do everything.

3.1 line 122-124 removed – out of scope for 1.0, and covered in the introduction as a future.

3.1 line 128: Add mention of UDDI.

3.1 line 129-135: Drop these lines – unneeded.