[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [ebBP] 4/8/2004: [RSD] Summary Review for WI-13-28 Role Changes
Discussion|OASIS.ebBP.WI13-28-Role Reversal and Business Partner Role; Topic|; Attachment|http://www.oasis-open.org/archives/ebxml-bp/200404/msg00008.html; Attachment|http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/download.php/6260/ebBP-mtgminutes-040504.txt; Attachment|http://www.oasis-open.org/archives/ebxml-bp/200403/msg00110.html; Point|Update on summary proposals to review and prepare for vote; mm1@ Please find below a complete discussion summary of Work Item 28 Role Reversal or Changes. I've incorporated multiple discussions, emails, and a sideline with implementors (Sybase and Cyclone). I would like to address this in Monday's call. Thanks. Work Item 28 Summary: Address how roles change in a business collaboration affect our syntax and the semantics behind it. This could impact collaboration, and determine if could also affect BT/BTA. Relates to WIs: 13 Business partner and business partner roles v2.0 Summary Resolve a. Recommend closure of WI 13 (Business partner and business partner role - v2.0 items only) with WI 28 via this resolution. b. Provide the capability to support performs that allows role binding for binary and multi-party collaboration. c. Provide clarification of AuthorizedRole. d. Provide capability to associate external roles ([1] see below). d. Support access to the BPSS instance for the process of forming or negotiating a CPPA. The CPP obtains values for ebXML Messaging for Service, Action, and Role from the BPSS instance. The CPP also assembles its internal mapping construct, Action Context, and the ProcessSpecification attributes. e. If external role is accepted, work with CPPA on a change for CollaborationRole in their specification (currently only allows 1). Tell suggestion: http://www.oasis-open.org/archives/ebxml-bp/200402/msg00182.html Roberts schema: http://www.oasis-open.org/archives/ebxml-bp/200403/msg00002.html Roberts explanation of external roles: http://www.oasis-open.org/archives/ebxml-bp/200403/msg00110.html; Moberg reference for (d) above: http://www.oasis-open.org/archives/ebxml-bp/200404/msg00008.html Meeting minutes 5 April: http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/download.php/6260/ebBP-mtgminutes-040504.txt; Open Items for v2.0 resolution: 1. Determine if entry points for top level process constructs are required with explicit declaration of Role values participating in the business process in the Start construct [Related to d. above]. Note that pre-v2.0 the capability exists but may be complex for the implementor. 2. Clarify whether Name or NameID is used for referencing [This relates to d. above and will be handled in WI 43]. Both Nagahashi, Moberg and Mukkamala feel using both would be complicated for implementors. If IDREF proposal is accepted, provide explanatory/semantic constraint that ensure there is no collision of values in IDREF. 3. Provide a clear mapping from the Role value in the referring context that goes with the referred-to process segment. 4. Provide an unambiguous mapping to requesting and responding role. 5. In cases where the roles do not change, allow the Performs to be omitted and the identity mapping will serve as a default. If accepted, provide explanatory text that indicates if the roles names (identify mapping) do not change, that a default could be used and the performs would not be required. 6. In the 1 March 2004 draft schema, explain the relationship between the CollaborationActivity child element Role and the collaboration pointed to by the collaborationID (that defines the roles relevant to the collaboration). 7. Show one consistent way to use Performs. Need explanatory text on how to use the ExternalRole and performs. Need an example for review. In draft schema it is being used in two ways: a. Map role to role value. b. Map external role to bound role in a referred to context. Open Items for v3.0: Additional support for business partner and business partner role (WI 13). I will be sending out another sideline discussion item for: * Name and NameID proposal from Nagahashi * Business signals Thanks. ================================================================================================================== [1] Roberts: Every binary collaboration has two roles. This level of role is use to indicate the relationship between the parties and the transactions. ExternalRole are used to map 'real' roles to thoe used by the Binary Collaborations. This is done by saying that an External Role performs a BC role. When a Binary collaboration calls another BinaryCollaboration using CollaborationActivity the BinaryCollaration Roles are mapped to the new BinaryCollaboration roles. An Example: 3 top level BC HandleOrder Roles: Buyer and Seller QueryOrder: Buyer and Seller CreditCheck: Customer and CreditService External Roles Retailer Wholesaler CreditAgency External Role Mappings Retailer performs Buyer Wholesaler performs Seller and Customer CreditAgency performs CreditService HandleOrder invokes CreditCheck via a CollaborationActivity Role Mapping Seller performs Customer CreditAgency** perform CreditService **Notice use of External Role within the CollaborationActivity. In order for this to work there would have to be at least three parties bound to the three roles involved. This may be new but I believe is needed. |Previously provided references for WI-28: |Attachment|http://www.oasis-open.org/archives/ebxml-bp/200402/msg00250.html; |Attachment|http://www.oasis-open.org/archives/ebxml-bp/200402/msg00225.html; |Attachment|http://www.oasis-open.org/archives/ebxml-bp/200402/msg00182.html; |Attachment|http://www.oasis-open.org/archives/ebxml-bp/200403/msg00002.html; @mm1
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]