Etienne Urbah on 2010-03-26

• Propose requirement with title  'The Logging and Bookkeeping functionality MUST accept requests querying the Status of an Activity (primarily for completed and finished Activities), and MUST return the Activity Status with different levels of verbosity (basic, detailed, more detailed)'

Etienne Urbah's position on 2010-04-09

• Log analysis and Security audit really require medium and long term persistence of information concerning Activities, even already finished
• Status is one important information concerning Activities
• Therefore, I vote FOR this requirement

Morris, Balazs and Etienne on 2010-04-21

• Source = PGI
• Spreadsheet ID = 38

Amsterdam meeting on 2010-04-29

• Change title to  'The Execution Service MUST accept requests querying the Status of an Activity, and MUST return the Activity Status with different levels of verbosity (basic, detailed, more detailed)'
• Open  (clear, but NO agreement found yet)

Etienne Urbah's position on 2010-05-07

• The title was changed AGAINST MY WILL, and perverted the original requirement :
  The original requirement was NOT about a capability of the Execution Service, but was stressing the need of a functionality securing access to the Activity Status even AFTER Activities are finished
• Therefore, I strongly require to revert to following title  :
  'Some Logging and Bookkeeping functionality MUST accept requests querying the Status of an Activity (primarily for completed and finished Activities), and MUST return the Activity Status with different levels of verbosity (basic, detailed, more detailed)'

Chicago meeting on 2010-06-22

• Change title to 'Logging Information MUST be kept and MUST be remotely made available'
• This is the goal of the JSDL Activity document Schema
• Agree OUT OF SCOPE