Henning wrote:
"How can an activity be sub-divided and how can this be
implemented? Although the activity is per definition atomic, it may happen that a work-flow execution engine decides to 
split it into various activities and assign those to different services. How is such a situation handled?

A potential solution could be some FollowerURIs that do a forward reference to potential sub activities." [http://ogf.
org/gf/docs/comment.php?id=344]

Action: Discuss. Is this covered by the use cases?