Description:

• Execution Service instance is a factory gateway for creating Activities
• Upon creation, Activities are either immediately passed to service instance performing their management, or are created at those services on request of initial service instance.
• This also covers Activity-as-service situation.
• In response to Activity creation request, additionally to Activity ID Client is informed about new location of Activity - endpoint or whatever is needed to access service managing the Activity.
• Alternatively, Activity ID may serve as container for that kind of information. But in this case Activity ID is not opaque anymore.
• New location/service instance also implements interface of Execution Service.  At least as much of it as need for managing the Activity.
• Even if during processing the Activity is moved to another location (whatever that means), it is still accessible through the Service instance which was initially assigned to the Activity.

Morris, Balazs and Etienne on 2010-04-23

• Original title of this requirement dated 2010-03-17 was :
  'After creation of the Activity, the Endpoint used by the Client to manage the Activity MUST stay the same until Activity termination, but MAY be different from the initial Endpoint to which the Client submitted the well-defined Job Description document'
• Change title to  'An Execution Service MAY offer several Endpoints to create and later manage the Activities while the later Endpoint must stay fixed'
• Spreadsheet ID = 49

Amsterdam meeting on 2010-04-29

• Still unclear after 10 mn discussion
• Please propose conceptual and example diagrams