Re: [ebxml-bp] State Alignment and Web Services

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

I think what we are discussing is that the business value is to provide 
state alignment [1].  That is a clear differentiator for ebBP.  On 
John's point on the acceptance acknowledgement, I think we need to be 
clear to separate what is required for contract formation or 
obligation.  I believe from our previous discussions that the AA is 
separate and distinct from a response. John, perhaps you can explain why 
you think they should be combined (with a use case)?  We may see more 
changes as a new business transaction pattern for contract formation is 
produced. 

On the Operation 'thingy,' I'll be opening the ballot tomorrow after we 
discuss it in the meeting.  JJ, thanks for starting the discussion. I 
think the state alignment issue is extremely important to us and for the 
community.

Sorry for later responses (in transit on move).  Thanks.


[1] This is business confidence in commitments between parties and the 
capability to support legal enforceability and traceability (which is 
what Anders has discussed). I believe we will see more value too in 
these constructs as we learn more about what dispatch-reach means.

> Yunker:
> I'll take issue with just the RM point.  Reliable Messaging as it is 
> normally discussed is implemented at and encapsulated within the 
> transport layer, while business action state confirmation can be 
> implemented at several levels (transport, message, process).
>   <JJ>We agree 100% on that, I was just trying to make the point that 
> RM is not enough.</JJ>....
>
>     Dubray:................Yes, this is precisely my point. In order
>     to ensure state alignment and offer non-repudiation. 
>
>     1)        RM is mandatory
>     2)        You need the receipt Ack for non repudiation
>     3)        You need the acceptance Ack for confirmation that the
>     message was process-able.......
>
>     -----Original Message-----
>     From: Monica J. Martin [mailto:Monica.Martin@Sun.COM]
>     Sent: Tuesday, June 08, 2004 6:53 AM ..................
>         * Support the guiding principles from other sources such as
>           UNCITRAL, other UN legal documents and the ebXML eCommerce
>           Patterns (v1.0) [3]. We do anticipate we will be adding more
>           support in a later version. So, this is our first step to
>     lay the
>           groundwork. Ensure that dispatch-reach requirements are
>     understood
>           and considered here.
>         * Provide the capability to support an abstract web service
>           reference (Operation 'thingy') [1]. Ensure we can support
>           monitoring and existing capabilities given this new function -
>           statuses, conditions, transitions, roles, etc.
>     .............................
>               o Use web services to provide state alignment where parties
>                 can't use a robust capability such as those defined in
>                 existing business transaction patterns [2]. 
>
>
>     [2] Yunker, 7 June 2004
>