wspbel 5/1/2007: Draft Primer Comments for WS-BPEL v2.0

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

Related to: 
http://www.oasis-open.org/apps/org/workgroup/wsbpel/download.php/23797/wsbpel-primer-draft.doc

   1. Reference to design goals: There are goals we have yet to (or may
      not soon achieve). I suggest we state generally our overall design
      goals and then the result we have today or delete this section.
      For example, even though we have compensation, we do not address
      its relationship to transactionality - this is a separate discussion.
   2. Section 2.3 jumps into differences with technical details too
      quickly. May wish to place this later in the primer (think about
      audience and then target where it should go).
   3. Section 3.1: Abstract process may not be a subset (i.e. abstract
      process may result in many executable completions and then
      executable processes). It could go either way. Uncertain this
      statement is required.
   4. Section 3.4.3: Change from: "The parallel variant is discussed
      further in the rest of this primer document". Change to: The
      parallel variant is discussed in more detail later.
   5. Section 3.4.4: Move this statement up where you introduce
      transition condition and talk about links (page 21~), "Transition
      conditions offer a mechanism to split the control flow based on
      certain conditions."
   6. Section 3.4.6: "As it can be seen in the example, a fault handler
      can have to types of children:..." to=>two
   7. Section 4.1: Introduce loop counter variable without explaining
      what it is. Same with suppressJoinFailure. May need to check the
      document overall to see if this is true in other cases and/or
      sections.
   8. Section 4.1.3 and 4.1.4: Explain what compensate and
      compensateScope are here somewhere (you talk about but don't
      differentiate).
   9. Section 4.2.5: May wish to state if message activities are
      ambiguous, we do have standard faults that handle. Here we state a
      case on how to alleviate.
  10. General:
          * Audience target: This is targeted to IT folks not business
            analysts. Look at how you jump into technical details
            quickly. Suggest you qualify the audience or concentrate on
            those that are most relevant to this document (system
            integrators, developers, etc).
          * Suggest to read specification first or used as a cross
            reference - suggest this be stated early in the document
            (particularly if you look at current Section 2.3 and the
            angle brackets showing up almost immediately).

Will continue - stopped at top of Section 4.3. Thanks.