(r3) VOSpaceBrainstormMeeting < IVOA

IVOA Web>TonyLinde>VOSpaceBrainstormMeeting (revision 3) (raw view)~~EditAttach~~

<H1>VOSpace Brainstorm Meeting</H1>
%TOC%
This is a set of notes made during a meeting to brainstorm ideas on VOSpace. Those present in the meeting were:
   * WilliamOMullane, GuyRixon, KeithNoddle, Dave Morris, NoelWinstanley, TonyLinde
and on the following telecon:
   * RoyWilliams, JohnGood, MatthewGraham

---++ Presentations
We pretty much made up the agenda as we went along but included a couple of MySpace presentations from AstroGrid people:
   * MySpace structure & scenarios (Dave Morris): [[%ATTACHURL%/FileStore.html][FileStore.html]], [[%ATTACHURL%/FileManager.html][FileManager.html]]
   * Security aspects (GuyRixon): [[][.ppt]]

---++ Notes
---+++ Dave's <nop>FileStore presn
   * in Export: MIME type allowed for data conversion (eg FITS to jpeg)
      * as yet no negotiation
   * question of about how dumb is the VOStore
      * contains metadata per item but does not interpret them
      * but must do so to implement security
   * <nop>MyDB vs MySpace: 
      * MySpace returns exact file put in
      * <nop>MyDB will translate into database and back again
      * so need to include flag that says 'store exactly'
   * VOSpace vs VOStore
      * Wil: implement only VOStore first
      * AG: <nop>FileStore is dumb and <nop>FileManager has all intelligence (incl who owns items)
   * coffee discussion
      * need layer above <nop>FileStore to implement security
      * VOBroker
      * but AG could just plug this into its <nop>FileStore --> VOStore

---+++ Dave's <nop>FileManager presn
   * do we want to introduce replica management into the spec at this stage
   * for now, AG only implements http protocol for filestore
      * but could implement other protocols
   * need to define minimum set of protocols
   * if http, need to ensure security
   * need protocol negotiation
      * minimum: 
         * SOAP with DIME attachment, 
         * HTTP
            * needs to allow security
   * VOSpace will support N protocols
      * will address many underlying filestores
      * client agent can state which protocol it wants to use
      * VOSpace will only pass back stores which support that protocol

---+++ Guy's Security presn
   * 

---++ Arguments
   * whether we need transformation (RESOLVED with VOStore capabilities)
      * mandatory if you are putting from file to database
      * metadata must indicate capabilities of store

---++ Agreements
   * still only need VOSpace and VOStore protocol levels
      * VOStore is higher level than AG <nop>FileStore
   * VOStore will advertise its capabilities
      * eg ability to return data in given format
         * AG filestore (currently) will only return in format uploaded
            * AG will extend filestore to support VOStore
         * <nop>MyDB will allow return in VOTable, CSV, FITS

---++ Action list
   * Dave: update VOStore doc with new methods
      * synch/asynch
      * init & data


<br><br><br>
<!--
      * Set ALLOWTOPICRENAME = %MAINWEB%.TWikiAdminGroup
-->

Topic revision: r3 - 2005-03-07 - TonyLinde

IVOA

Log in or Register

IVOA.net
Wiki Home
WebChanges
WebTopicList
WebStatistics

Twiki Meta & Help
IVOA
Know
Main
Sandbox
TWiki

TWiki intro
TWiki tutorial
User registration
Notify me

Working Groups

Interest Groups

Time Domain

Committees

Stds&Procs

www.ivoa.net
Documents
Events
Members
XML Schema