[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ebxml-cppa-negot] negotiability of BPSS instance document.
Replies inline <gnk> </gnk> -----Original Message----- From: Martin W Sachs [mailto:mwsachs@us.ibm.com] Sent: Wednesday, November 13, 2002 8:28 AM To: Kartha, Neelakantan Cc: ebxml-cppa-negot@lists.oasis-open.org Subject: RE: [ebxml-cppa-negot] negotiability of BPSS instance document. Negotiation over version may be OK. If others want to leave that in, I would fix the words that I added to 10.2 and change 5.2 to talk only about version. We certainly understand how to negotiate over version; it's just one more of many enumerations. However, I just looked at BPSS 1.05 and could not find anyplace that defines the version of an instance document. The version attribute in the ProcessSpecification element is for the version of the BPSS specification. Negotiation over that may be of some interest but I don't think it's what we had in mid. <gnk> Interesting! Thanks for pointing this out. I agree with you that this is not what we had in mind. Maybe we can point out to the BPSS team that instance documents may also need to have a version number. </gnk> Unless I missed something, we cannot allow negotiation about a version of an instance document because no such thing is defined. A new version of what amounts to the same choreography definition would have to have a new value of the name attribute. On thinking about it, it is not clear to me why we ruled out negotiating over the choice instance document at all. The name of the instance document is also a member of an enumeration. If what I said above makes sense, I suggest changing the 3 places mentioned below to say that the partners can negotiate over which instance document to use. Shall we specify using the name attribute or the UUID attribute? <gnk> I think that is fine. Name attribute should work </gnk> Do we want to also provide for negotiating over the version of the specification? Does that require any changes to text or NDD schema? <gnk> I agree that this would not be very useful, but we need not rule it out. This will not require changes tot he schema. </gnk> The harder part is dealing with choices of instance document that differently affect the details of the CollaborationRole element. Shall we keep that out of scope for V1 and put in V1 a requirement that all choices must have the same CollaborationRole element structure? <gnk> I agree that thsese should be out of scope for V1 </gnk> 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 **************************************************************************** ********* "Kartha, Neelakantan" To: Martin W Sachs/Watson/IBM@IBMUS, <N_Kartha@stercom ebxml-cppa-negot@lists.oasis-open.org m.com> cc: Subject: RE: [ebxml-cppa-negot] negotiability of BPSS instance document. 11/12/2002 07:30 PM I would like to understand better the concern with possibility 2 before ruling that out. Is the issue that when versions change, so can aspects under CollaborationRole? Kartha -----Original Message----- From: Martin W Sachs [mailto:mwsachs@us.ibm.com] Sent: Tuesday, November 12, 2002 5:54 PM To: ebxml-cppa-negot@lists.oasis-open.org Subject: [ebxml-cppa-negot] negotiability of BPSS instance document. We have some inconsistencies with regard to what is negotiable about the BPSS instance document. In section 5.2, it states that two partners can negotiate over which BPSS instance document to use. In 10.7, it states that the version of a BPSS instance document is negotiable In section 10.2, it now says (in response to a comment on the last-distributed version of the specification): "Two prospective trading partners SHOULD agree on the same BPSS instance document and assignment of roles before beginning to negotiate the CPA." We need to resolve the inconsistency. Possibilities: 1. Put any negotiation about BPSS out beyond version 1. For this I would remove the statements in 5.2 and 10.7 and change the SHOULD to SHALL in 10.2. 2. Allow negotiation about the version of the same BPSS instance but not more general. This would require clarifying the statements in 5.2 and 10.2 to mention version but not allow negotiation of completely different BPSS instances. 3. Allow negotiation about which BPSS instance document. (not just version). I believe that we understand how to negotiate about version but not how to negotiate more generally about which BPSS instance document. However, I am not sure that we know how to negotiate about roles or, perhaps, other aspects of what is under the CollaborationRole element. Given the lateness of the hour, I suggest that (1) is the only choice for version 1. If we agree on (1), I will add something to the futures document. Comments, please. 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 **************************************************************************** ********* ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC