[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ebxml-cppa] Re: Notes from BPSS/CPPA conference call
Marty, This issue was mentioned on the call, and I believe we did agree that the BPSS instance would always have a UUID that would uniquely identity and distinguish it from other BPSS instances. David Smiley summarized this as: "Service = BPSS Unique Process Identifier (UUID) Request to make UUID a URN" If a short name is used within an agreement, its uniqueness would depend upon being scoped by the CPAId, as you and Hima note. Some issues that still have not been resolved concerning standardization of naming conventions flow from the following: 1. A BPSS instance is not guaranteed to have any "functional" unity (that is, it can consist of unrelated packages of functionality), 2. The CPA currently uses the ServiceBinding to specify similar treatment for all leaf actions under a BPSS instance (when BPSS used), and 3. CPAs may wish to make agreements only over a subset of leaf actions within a BPSS instance. Suppose 2 companies want to engage in OrderManagement, but do not wish to engage in POCancel actions or POChange actions. [This is not a far-fetched example, by the way.] If the ServiceBinding embraces all actions in the instance, they will in effect agree to bindings for actions that they do not support across the mythical BSI interface. These situations may have the following possible remedies (and I am sure there are others as well!): 1. Create ways to specify a portion of a BPSS instance as the targeted package of leaf actions. That reopens themyriad "name" attributes from which the service name could come from. May be feasible though. 2. Create ways to have Override specify a null binding for actions not agreed to. (Not wild about this one either as it seems to introduce clutter that the binding-up-actions as a group) 3. Apply Tony W's XSLT filter ideas to the BPSS instance to extract the right ones. If we use this technique, then we still should document how the service naming convention works. -----Original Message----- From: Martin W Sachs [mailto:mwsachs@us.ibm.com] Sent: Wednesday, November 21, 2001 7:34 AM To: Dale Moberg Cc: Dan Weinreb; dsmiley@mercator.com; ebtwg-bps@lists.ebtwg.org; ebxml-cppa@lists.oasis-open.org Subject: RE: [ebxml-cppa] Re: Notes from BPSS/CPPA conference call Dale, It isn't clear to me from previous discussions that when more than one application behind the same MSH uses the same BPSS instance document, the different "BPSS instances" will have unique service names. Do they all have the same UUID or unique UUIDs in this case? If the service names are the same in that case, it's OK as long as they are qualified with the CPAId. 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 ************************************************************************ ************* Dale Moberg <dmoberg@cyclonecommerce.com> on 11/20/2001 06:44:17 PM To: Dan Weinreb <dlw@exceloncorp.com>, dsmiley@mercator.com cc: ebtwg-bps@lists.ebtwg.org, ebxml-cppa@lists.oasis-open.org Subject: RE: [ebxml-cppa] Re: Notes from BPSS/CPPA conference call Dan Weinreb asked: "It seems to me that this would mean that every message sent under the control of a particular BPSS would have the same Service value. That is, all the messages sent by a given business process would all have the same value for Service. Is that what was intended?" Yes, I think that is the current proposal under consideration. This convention would be coupled with the constraint that all distinct actions within the BPSS instance would have distinct names (both the short version names and the long Xpath names would be distinct within a "service") So an OrderManagement service would have PurchaseOrder , PurchaseOrderChange, PurchaseOrderCancel, PurchaseOrderAcknowledge actions, for example. ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.ebtwg.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC