ebBP 3/31/2005: Comment re: Pure Choreography (wd10-schema 2/22)

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

In Tuesday's call, we discussed a public comment from the Government of 
Canada (thanks Ed) about statefulness, and pure choreography and message 
exchange. To answer Ed's question, summarize and provide for a brief 
change, see below:

    Is pure choreography stateful? Yes.

Discussion Summary 29 March 2005:

    * ebBP allows you to monitor what occurs. Status values and business
      documents have state. Events are part of history or state of the
      business transaction and processes related to the exchanges.
      Involves state alignment.

Here are a few examples, of many that exist in the wd10 technical 
specification:
Section 4.2

    ........The state of a given business transaction activity instance
    can be explicitly calculated at run-time by evaluating these
    signals. As such they are instrumental in establishing a business
    collaboration protocol that insures that the representation of the
    state of a business collaboration instance for each party, is
    strictly identical.   For example, an Acceptance Acknowledgement
    signal is generated after an application, service or middleware has
    successfully processed and business validated a business document.
    The process of exchanging signals and state changes of a business
    transaction enables "state alignment" between the parties
    involved........

Section 4.5

    ......One or more Business Signals MAY additionally be exchanged as
    part of a Business Transaction to ensure state alignment of both
    parties. The business collaboration is defined as a choreography of
    business transactions performed relative to each other.....

In order to be more explicit to the supposed reference that raised Ed's 
question, here is a descriptive change proposed. Comments welcome. Thanks.

=========================================================================================
Proposed change (descriptive)

Section 4.9
Change from:
The operation mappings allow for using the ebBP technical specification 
and schema for mapping web service interactions without any other ebXML 
support such as Collaboration Protocol Profile or Message Service. The 
ebBP technical specification allows the definition of pure message 
exchange in a choreography.

Change to:
The operation mappings allow for using the ebBP technical specification 
and schema for mapping web service interactions without any other 
required ebXML support such as Collaboration Protocol Profile or Message 
Service (although they could be used). The ebBP technical specification 
allows the definition of pure message exchange in a choreography 
including constructs for state alignment using business signals, state 
transition and condition guards, etc.
=========================================================================================