JSDL Activity Instance Document Schema Session
==============================================

* Review of issues raised at the BOF

* Presentation of schema

  - information contained in 'resource' element could be
    - jsdl
    - rsl
    - other resource request
  - 'resource' may not be the right term for this
  - consider changing to 'resource requirements'
  - resource should probably be 0-1 not *

  - usage record could go in 'context'
  - activity record to find things according to state
    - omitting elements from an entry means no change in that
      information

  - The main use case is lifetime record of activity

  - Would be nice to have a separate usage record element
    - Would a usage record entry be a snapshot or for a period
    - Agreed that this depends on the definition of the UR 
      - It could be a cumulative record or a snapshot
      - and it should be part of the UR entry so outside the scope of
        the Activity specification
  - Record timestamp is the point in time of the record creation; no
    more semantics than that
    - Could have more restrictive semantics in a profile 

  - Category: include a 'final' type as well
  - dependency: rather than general 'dependency' restricted to an
    'activity' dependency or to another record?
  - Move to specifically-named elements rather than general named elements?
    - as concrete as possible or general bucket that can be
      specialized ... this comes back to a proposal at the bof to do
      this specifically for a set of OGF specs

  Agreed to keep the discussion on this topic within the JSDL-WG (for
  now at least)

  Action: Chris, Shabaz, Philipp, to provide use cases

  Action: Andreas to look at DMI Activity specification

  Issue: Decide level of concreteness; how specific top-level elements
         should be 

  Action: Andreas to adjust teleconf times to allow for PDT
          participation