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

Peter  Kunszt <Peter.Kunszt@cern.ch>
Kalman Kovari <Kalman.Kovari@cern.ch>
=====================================

  1) The examples are sometimes more misleading than useful...
     
     -> why?
     -> TODO ANDRE: clearify, discuss on list
 
 
  2) The error handling and error semantics are not defined well
     enough.  This is essential in order to assure proper
     interoperability.
 
     -> compile list of error codes, check for consistency
     -> TODO TOM: create proposal for procedural and OO
 
 
  3) There is a lack of structure in terms of interface layering.  High
     level interfaces (like JobManagement) and low level interfaces
     (like Stream) are not distinguished, motivated, or put into
     context.  E.g. why is there a need of a networkstream-level
     interface for a grid application?
 
     -> intentional, see use cases!  
     -> DONE: ANDRE: CLEARIFY in intro
 
 
  4) Example (P18): OO structured, not like the iface. 
     (eg. i = dir.getNumEntries() instead of dir.getNumEntries(a) ? )
 
     -> TODO ANDRE: cleanup, also session handle etc.
    

  5) Example (P29): an exact copy of Ex. 1.

     -> check
     -> DONE ANDRE


  6) Description - Streams (P62): close or destroyStream? maybe close,
     but not consistent.

     -> see Notes in Streams
     -> DONE ANDRE: use <constructor> or so. - check SIDL
        ==> not specified in SIDL, 
            proposal: use "CONSTRUCTOR" and "destructor"


  7) General: sometimes bitwise OR-s are used for multiple options
     (Stream/ActivityType, P59), sometimes arrays of values
     (NameSpace/CopyFlags, P9). Why no convention? 

     -> I agree, bitwise OR is simplier
     -> TODO ANDRE: check for languages, fix
    

  - Interface NSDir: what are the semantics of the copy method? of
    getName and getURL?

    -> ?
    -> DONE ANDRE: ask for clearification, sync with GFS


Thorsten Sch"utt:
-----------------

  9) isFile -> isEntry?

    -> should we revive NSEntry (more reasons?)?
    -> TODO ANDRE: ask mailing list


  10) SIDL docs on wiki!

      -> TODO TOM/JOHN


  11) fix all examples in respect to session and context

      -> DONE ANDRE.
         Use a default session handle if none is specified 
         -> examples are still valid :-D


  12) flags 
  
      -> TODO ANDRE: see above


  13) Attribute -> AttributeSet 

      -> TODO TOM: leave naming, but better describe idea


Steven Newhouse:
----------------

  14) Inconsistent use of security!  Its only in the stream
      section, nowhere else.  "Not specifying a security system
      makes sense, but I think all of these methods should have
      a security token being passed into them or it should be an
      argument in the relevant object constructor."

      -> should be fixed by session and context
      -> DONE ANDRE


  15) I assume the URL can support a number of protocols -
      http/https/file/gridftp. I see no way to register plugins in the
      interface (may be this is an 'internal' interface as opposed to a
      user funtion. Maybe there needs to be aet of interfaces to help
      the developers, e.g. register protocol plugins.
  
      -> plugin: implementation level
      -> url support: util class?  any://? -> language specific
      -> need good error codes
    

  16) State example language each time!  Do examples in multiple
      languages!

      -> TODO: 


  17) How are you going to handle partial functionality implementations?
      Should _all_ operations support a NotImplementedException? Should
      there be a standard static method in each section to discover what
      is implemented? e.g. supported protocols & supported methods.

      - methods need ALL to be implemented.  
      - protocols etc: hmmm...
      - discussed at GGF, DONE
      - was discussed at GGF...
      - there WILL be partial implementation, but they are not SAGA
        conform then.
      - necessary  (session, context, ...) 
      - sufficient (one other subsys)
      - CAN implement subsystems -> complete subsystems (partial
        compliant)
      - DONE ANDRE

      - should we allow query of implemented subsystems?
      - OPEN ISSUE


  18) You have an 'LSF' schema for >>, >, < & <<. But in the
      file/directory area you use a series of attribute flags. I think
      you should carry these attribute flags forward into the job
      definition area - either way I think you should have one model not
      two! 

      - TODO ANDRE: mark as known issue

  19) I.   General Model. 
           Language mapping. 
           Standard attribute model. 
           Security. 
           Tasks
      II.  Tier 1 Interfaces.
      III. Tier 2 and above Interfaces.

      - II and III on same level!
      - DONE


  20) What is to come in version 2?

      - steering and monitoring
      - possibly combining logical/physical files (read on
        logical files)
      - advert service
      - GridRPC
      - GridCPR
      - Task dependencies (simple work flows and batches)
      - extensions to existing classes
      - we have no explicit roadmap!!
    
Others:
=======

  21) 'The URL Problem' 
      
      - should we approach it?
      - TODO ANDRE: 
        - explain problem, leave it open
        - an implementation MAY be able to translate, or use any://
        - MUST throw good exception otherwise


  22) advert service

      -> easy: NS + Attribute + find on attribute!
         why not do it?


  23) find in name spaces?

      -> why not, at least for names!?  
         But over attributes?  
         What about query language then?
         TODO ANDRE: proposal to the mailing list.

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

Andre:
======

  24) list only on dir - why not on file?

  25) go from getSize to real stat

  26) namespace ops on files - why not on wildcards?

  27) should callbacks be introduced for some things?  Best on tasks,
      but also for streams (is factory!)  Necessary for
      monitoring/streaming, so best introduce in general...

  28) integrate GridRPC / GridCPR / JSDL?  What else?

  29) check if bulk operations can be done with task containers
      (explicit support needef for argument list generations?)

  30) ACLs 
    
  31) Authorization (call outs?)

  32) task = ftf.read (1, buffer, &n);
      task.run ();

      When are 'n' and 'buffer' available?  I would say after wait.

  33) default: define semantics, point out parts where semantics is up
      to the implementation    


GGF14:
======
  34) who sends UC doc to editors?

+-------------------------------------------------------------+

  35) TODO ANDRE: relation to OGSA into intro
  
  36) TODO ANDRE/TOM: 
      - example are not normative for language binding
      - peovide one examples in various languages