Notes for today's meetings

[Ti Leggett]

Action Items:
* Read all three documents
* Justin, Mike, and I should provide questions for Bob, Terry, Ivan, and
Tom to talk about
* Get comments back on VV document so that we can get comments to Todd
* Make  a list of friends to go over these documents


-------------- next part --------------
Notes for 08/20/02 AG meeting

-Arch Overview
  + Allows to move forward by providing context for agreed upon definitions and conecpts of the AG
  + Describe in general the AG and how it worked
    * from here design and implementaion follows
  + Venues
    * High level descrip of venue and assumptions that venues need to fulfill
      # support for presence
    * Must provide highest quality of a shared context
      # no objects in space that are hidden
      # i.e., either all users see it or no users see it
  + Users
    * bring in "things" to share with other users
  + Nodes
    * provide shared capabilities to users
    * Node isn't first person in venue
    * Users can go into venues without nodes
    * Nodes enable *groups* of users to interact
  + Applications
    * represent shared apps *and* network service (NMI)
    * Not users and not venues
    * May need to be redefined are refined
    * Collaborative Apps
      # workstation docking(?)
      # need to think how we'll approach collab apps
      # need to provide requirements of capabilities the AG can offer to app writers
    * Network services
      # Can't look at it
      # There but can't be seen by users and shouldn't be seen
  + Maybe add how the AG is different from other systems at same level of abstraction
    * Need to know what we agree on first before we can show how it's different
  + How do we distinguish between tools left in a venue a shared things
    * things in venues should be persistent even though what they point to may or may not be accessible
    * data must be possible to be there.
    * apps/tools/interfaces may or may not be there
    * an object in a venue is a described thing and must be user visible


-----------------------------------------------------


Architecture:
 - concepts, terminology, definitions, why we decided to do this
 - completely technology/desgin independent

Desgin:
 - API and protocols
 - may not be interoperable


Look around GGF sites for how their documents (arch, design, etc) aren't defined/layed out.