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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

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


Subject: [ebBP] 2/22/2004: ebMS-ebCPPA.ebBP Mapping WI 28 [RSD]


Discussion|Oasis.ebBP.ebCPPA ebMS mappings;
Topic|ebCPPA version 2.0 texts pertaining to ebBP and supported mappings
to ebMS;
Point|Integrating mappings for ebBP ebCPPA and ebMS into ebBP technical
specification;

mm1@
On this item, I would propose for the team's consideration:

1. Address text clarification on Action value in ebMS related to 
ebBP.Seek alignment if practical in 2.0 but at a minimum by 3.0.
2. Ask Hima Mukkamala to participate in a session to talk about 
ActionContext and its map in the ebBP.
3. Recognize that Binary Collaboration item will be handled outside of 
WI 28 in the work on WI 13, Roles.
4. Clarify the items needed by ebMS and ebCPPA:
 Service values
 Action values
 Role values
 Instance identifiers

Note, consider if Martin Roberts suggestion is sufficient:
.........................
   In my simple mind the CPP/A needs to point at four things for each BPPS:
   a) the ProcessSpecification [uuid]
   b) the BinaryCollab that implements a BusinesTransactionActivity
   c) the BusinessTransactionActivty so you could amend its details TTP
   d) the underlying BusinessTransaction that is used by the BTA so you 
can change its criteria.
   ( of course there is the roles )

   The reason for the Four levels is a partner may not implement all of 
the Binary Collabs specified in a BPSS and so you need to be able to 
know which BC they are allowed to use.  3 and 4 are just to enable the 
properties to be amended.  ( I presume the CPP/A allows this? )

   For messaging under the control of a BPSS you need the following:
   a) The processSpecification [uuid]
   b) The BinaryCollaboration - that represents a description of the 
conversation that should/could take place
   c) the BTA that is being invoked.

   The reason for all three is these are all needed to uniquely identify 
the BTA that is being invoked.  I am concerned that this is not 
currently supported and therefore our BPSS spec would have to make BTA 
names unique across all BinaryCollaborations in a BPSS.  This to me in 
not acceptable as a you may choose to use one BPSS to escribe two very 
similar but different processes where the BTA occurs in more than one BC.
.........................

5. Identify a mapping for all the BPSS nesting/hierarchy onto short names.

I would suggest we set up a meeting in the near-future or coordinate at 
the OASIS symposium to discuss these items with representatives from 
ebMS and ebCPPA.

May I have comments from the team? Thanks.
@mm1



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