[saga-rg] strawman...

[Andre Merzky]

Hi folx, 

GGF17 is getting closer, and we had the plan to have a
stable strawman API by then.  That means we whould try hard
to address the remaining issues.

I attach the current list of open issues: if you have
thoughts to any of them, please post them to the list.

Also, we should try to take up phone calls I think, and
dedicate them to the issue list.  

Best regards, 

  Andre.


-- 
"So much time, so little to do..."  -- Garfield
-------------- next part --------------

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

               #####
              #     #  #####   ######  #    #
              #     #  #    #  #       ##   #
              #     #  #    #  #####   # #  #
              #     #  #####   #       #  # #
              #     #  #       #       #   ##
               #####   #       ######  #    #
        ###
         #    ####    ####   #    #  ######   ####
         #   #       #       #    #  #       #
         #    ####    ####   #    #  #####    ####
         #        #       #  #    #  #            #
         #   #    #  #    #  #    #  #       #    #
        ###   ####    ####    ####   ######   ####

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


  12) change signature of read/write to have len_out as out param, and to return
      error code (== EAGAIN on unsucessful read)
      - DECIDED at GGF16
      - OPEN (is that _really_ the right way?)

  29) check if bulk operations can be done with task containers
      - explicit support needed/wanted for argument list generation?
      - consider parametrisable job descriptions for bulk jobs?
      - TODO STEPHAN

  30) ACLs!
      - Later, after we get input from the security area and GFS
      - OPEN
    
  36) - example are not normative for language binding
      - provide one examples in various languages
      - TODO TOM:     Fortran
      - TODO HARTMUT: Python
      
  47) check JSDL compliance
      - TODO CHRIS/ANDRE

  55) check strawman for references
      - OPEN

  60) add attributes to others?  consistency model might be an
      option for replication, blocking/nonblocking for file I/O
      - OPEN

  70) describe task model verbosely in the spec, leave details to
      language bindings.
      - TODO ANDRE

  75) have ALL possible error codes documented
      - OPEN

  76) add specs for literals (attribute names), 
      and add them like enums
      - OPEN

  77) no details for getURL and getName
      - TODO ANDRE

  81) document pattern and extended read/write
      - TODO ANDRE

  82) Explain sidl.SIDLException !
      - OPEN

  83) Exceptions should go into the SIDL part!
      - would clutter the SIDL?
      - OPEN

  88) for job: add clean_up (can also be called after termination)
      - OPEN
      
  90) exceptions missing in job!
      - OPEN

  93) introduction needs sanity checks in respect to the groups development
      (WG/RG split)
      - OPEN
  
  95) Security on observables missing: need callout on metric
      read/write
      - check also stream auth example
      - OPEN
  
  97) flags (and their inheritance) seems somewhat confusing
      - TODO ANDRE (see name space, reuse values in file etc)
    
  98) LogicalFiles/Directories: define attributes
      - TODO ANDRE

 102) document what classes need to implement ErrorHandler
      - OPEN

 105) fix details of keystore security context
      - TODO ANDRE
 
 108) explain why we don't specify constness.  Or should we?
      - OPEN
 
 109) Formatting should be more TeX like
      - TODO ANDRE

 111) ---

 112) monitoring needs detailed descriptions.
      - TODO ANDRE

 115) detailed description for name_space methods out of sync
      ns_entry methods are missing.
      - TODO ANDRE

 118) Stream: detailed description out of sync
      - TODO ANDRE
   
 119) Task: detailed description out of sync
      - TODO ANDRE

 125) Monitoring as in Streams ok, use in all objects, define
      available metrics
      - TODO ANDRE
 
 126) ---