Agenda for GWS-WG sessions at Beijing Interop meeting

Session 1: VOSpace 1.x

The VOSpace 1.x series are the SOAP-based VOSpace standards. VOSpace 1.0, which is at the WD stage, is for the flat, isolated space. VOSpace 1.1, for which the specification is under discussion by an experts group, adds container (directory) hierarchies and links between spaces; it approximates AstroGrid MySpace in function.

Three presentations (15 min each):

Followed by discussion on changes required for 1.1.

Links :

Objective: decide where we are going with VOSpace 1.1

Actions:

  • Test interoperability of VOSpace implementations at Astrogrid, Caltech and ESO by end of June
  • VOSpace 1.1 has the following issues that need to be resolved:
    • Container level metadata - how to distinguish those that relate to the contents of the container through inheritance and those to the container itself
    • Generated names - vos://null does not work for containers so use ".auto" or "/" as an alternative
    • Typing of protocol and view parameters - these are currently designated as "string" but normal parameters are "URI"
    • ACL - although this forms part of a wider SSO context, should VOSpace have some notions of ACL control
    • Find - a equivalent to the Unix command is desired
  • It was decided to defer manipulation of state, e.g. in an asynchronous data transfer, to a later version of VOSpace

Session 2: RESTful services

This session covers services to the REST paradigm, including particularly:

  • UWS;
  • extensions to DAL services for data staging;
  • RESTful versions of VOSpace (which may appear as the VOSpace 2.x series).

Email discussions suggest that just about everybody prefers REST to SOAP and that all new standards for IVOA should be RESTful rather than SOAPy. If you disagree, then this is your best chance to put your point of view.

Talks:

We shall be tight for time in this session, so please make your talks brief enough to allow time for discussion.

Objective: shared understanding of what REST means and how we can exploit it. But specifically, I want to find out how well UWS v0.3 fits with other, planned IVOA standards and to decide who will be the authors for the later, more-refined drafts of UWS.

Links:

Session 3: SSO and VOSI

Talks:

  • The NVO Identity Services and Suppport for Secure Portals - RayPlante (PDF)
  • Reference implementations for SSO components - GuyRixon

Followed by a short open forum for any attendees to speak on their security work (no slides needed). Hopefully, we can get through the security part in the first half of the session.

Second half of session: what to do with VOSI. This naturally follows on from the discussions in Registry-WG about how to harvest rich metadata. If those discussions reach consensus, then we should be able to decide how VOSI should come out. If there is no consensus then we can't say anything sensible about VOSI and we can finish early.

Links:

Objective: plans for V1.0 WD of VOSI, dependent on outcomes in Registry-WG.

-- GuyRixon - 10 May 2007


Topic attachments
I Attachment Action Size Date Who Comment
PowerPointppt Beijing-GWS1.ppt manage 654.0 K 2007-05-14 - 03:18 MatthewGraham  
PowerPointppt Beijing-GWS2.ppt manage 682.5 K 2007-05-15 - 01:24 MatthewGraham  
PDFpdf IVOAMay07SSO.pdf manage 286.9 K 2007-05-18 - 00:37 RayPlante  
PDFpdf VOSpace1ESOLL.pdf manage 9765.6 K 2007-05-16 - 00:46 PaulHarrison VOSpace 1.0 ESO Lessons learned
PDFpdf VOSpaceWebDAV.pdf manage 7163.5 K 2007-05-16 - 01:30 PaulHarrison VOSpace 2.0 and WebDAV
PDFpdf talk-gray-rest.pdf manage 333.5 K 2007-05-17 - 07:19 NormanGray  
PDFpdf vospace-20070514-01.pdf manage 248.0 K 2007-05-18 - 02:05 DaveMorris Implementing VOSpace 1.x
Edit | Attach | Print version | History: r14 < r13 < r12 < r11 < r10 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r11 - 2007-05-18 - DaveMorris
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback