ebBP 4/19/2005: Comments on Tech Spec for Today's Call (19 April 2005)

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

Everyone,
Please note and attend today's teleconference. In today's call (9 a.m. 
PDT), please let's discuss the brief set of comments received this last 
week (during the CD vote but not attached to any vote cast):

   1. Correction on CPPA-ebBP mapping:
      http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/email/archives/200504/msg00050.html
          * Correction sent by Dale Moberg 18 April 2005:
            http://lists.oasis-open.org/archives/ebxml-cppa/200504/msg00010.html
            (to CPPA list - see second table posted)
   2. Page numbering glitch: Glitch in Microsoft Word (tracked changes
      issue)
   3. Section 3.4.11.1: Fork with many joins - Current text below:

        "For XOR or OR Fork, this does not rule out different joins
        pertaining to states emerging from a Fork or Forks.  This allows
        a split in processing between a group all of which must be done
        and one where at least one (or more) is sufficient for the
        transition. The behavior of Forks over Joins is implementation
        specific."

    The semantics are clear about multiple dependencies that may exist
    to enable next activity. A comment has been raised that, even though
    this could happen in implementation (as we specify), combining XOR
    forks and multiple joins may result in a fork that cannot be
    resolved.  We explicitly leave that to the implementation to
    resolve. If we wish to be explicit, a change may be required.

    Possible change proposed by Kenji Nagahashi: [add] Tools MAY assist
    in detecting any deadlock or unresolvable conditions via static
    analysis. [end-add]

I am verifying with OASIS staff what TC process we would be required to 
adhere to and the conditions should we make changes to the CD after the 
vote. Thank you.