[ebBP] Roberts 2/23/2004: Pattern Properties WI 22 [RSD]

["Monica J. Martin" <Monica.Martin@Sun.COM>]

Discussion: OASIS.ebBP.WI22-Transaction Pattern Support;
Topic|;
Attachment|http://www.oasis-open.org/archives/ebxml-bp/200402/msg00229.html; 

Point|Differentiation between Request-Confirm and Request-Response;

mm1@
*||Attachment: Patterns properties, Martin Roberts 23 Feb 2004: 
http://www.oasis-open.org/archives/ebxml-bp/200402/msg00229.html
||Includes these gifs: <<bta_pr2.gif>> <<bta_pr1.gif>>*

Martin,
If you look at R10 Chapter 9 Patterns, the key difference between 
Request-Response and Request-Confirmation may explain although I agree 
what is in ebBP should be clear and traceable:

    * Similarities:
          o Both do not allow the use of Acceptance Acknowledgement.
          o Both see non-repudiation as optional.
    * Differences:
          o Request-Response: Does not make specific mention to a
            Receipt Acknowledgement.
          o Request-Confirmation:
                + Allows explicitly for a Receipt Acknowledgement.
                + Can be used for business contracts.
                + Example given: A request for authorization to sell
                  certain product and an expected confirmation response
                  to request to confirm requester is authorized or not
                  to sell the products. [Infers some level of business
                  semantic missing in Request-Response]

Actually this points out that the tables may need redress to be 
consistent with the defined business transaction patterns.
Martin, do you have specific suggestions?

Thanks.

=======================================================================================================
martin.me.roberts@bt.com wrote:

> * <<bta_pr2.gif>> <<bta_pr1.gif>> *
>
> Dear all,
>         Attached are the two tables that give the various properties 
> of the transaction patterns that are defined for BPSS.  The reason for 
> sending them is that I am not sure the values of the properties make 
> much sense. For example:
>
>         Request/Confirm in the Request Authorization is false in 
> Response it is True?  If you look at the tables you will see a number 
> of these inconsistencies.  What do we do about them as we were 
> intending to add the patterns to the schemas.  DO we work of these 
> blindly or change the values as we see fit?
>
> / Martin Roberts /
> xml designer,
> BT Exact
> * e-mail: * martin.me.roberts@bt.com
> * tel: * +44(0) 1473 609785   clickdial 
> <http://clickdial.bt.co.uk/clickdial?001609785.cld>
> * fax: * +44(0) 1473 609834
> * Intranet Site : * http://twiki.btlabs.bt.co.uk/twiki 
> <http://twiki.btlabs.bt.co.uk/twiki>
> pp 16 Floor 5, Orion Building, Adastral Park, Martlesham, Ipswich IP5 
> 3RE, UK
>
@mm1