Named message elements

["Oliver Kopp" <oliver.kopp@iaas.uni-stuttgart.de>]

In the current version of the spec, the "name" attribute may only be used to
name activities.

It is helpful for us to have names on all elements used for receiving
messages. I.e. we would like to have the possibility to name <onMessage> and
<onEvent> elements. Maybe it is be good for consitency to offer "onAlarm"
also to be named.

Compact example:

<pick name="WaitForBidOrReferral">
  <onMessage name="processBid" ...>
    <scope>
      <eventHandlers>
        <onEvent name="statusRequest" ...>
        ...
        </onEvent>
      </eventHandlers>
      ...
    </scope>
  </onMessage>
  <onMessage name="processReferral" ...>
    ...
  </onMessage>
  <onAlarm name="timeout">
    <for>PT1H</for>
    ...
  </onAlarm>
</pick>

We know that there is no requirement on the names to be unique. We want to
solve that issue by specifiying a new Abstract Process Profile.


Is it possible to work-in our proposed change in the upcoming version of the
specification?


Thank you in advance


Oliver Kopp

--
University of Stuttgart
Institute of Architecture of Application Systems (IAAS)
Universitätsstraße 38 - 70569 Stuttgart
+49 711 7816 - 483
http://www.iaas.uni-stuttgart.de