|
META TOPICPARENT |
name="InterOpMay2007" |
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:
Agreements and actions:
- Shared understanding of REST? More nearly, but there are still arguments about details. Maybe we should write a Note?
- RESTful services still more popular than SOAPy ones (one delegate in the meeting spoke in favour of SOAP)
- A RESTful VOSpace 2 is desirable (but VOSpace 1.x is still needed).
|