Etienne Urbah on 2010-04-20

• The Execution Service creating an Activity MUST store inside the Activity ID the Endpoint of the service managing the Activity, so that any Client is able to extract this Endpoint
• The precise syntax will be defined later, and only if PGI agrees on this requirement
• The Execution Service MAY store any additional information inside the Activity ID, but MUST NOT assume that Clients are able to extract this additional information
• Each Client MUST be able to extract the Endpoint from an Activity ID
• In order to issue requests concerning the Activity to the adequate instance of Service, a Client needs only the Endpoint, and the Activity ID as it is, but does NOT need to extract any further information from the Activity ID
• The Client can NOT anyhow manipulate the content of the Activity ID (except changes allowed by the format of Activity ID and which do not change its syntax, such as whitespaces inside XML)
• This requirement eases implementation of JM4.5 :  the Execution Service creating Activities could be a factory gateway, and Activities could even be implemented as service instances

Morris, Balazs and Etienne on 2010-04-23

• Source = General
• Spreadsheet ID = 51