Discussion of the VOSpace 1.0 specification Document

This is a discussion page for the VOSpace-1.0 service specification document.

This is somewhere where we can post proposals and to enable interested parties to discuss the different versions.

For each version there is a Change request section - please add to this and vote on other suggestions

• +1 if you agree
• -1 if you disagree
• 0 if you have no particular preference

---

---

Version 0.21

• vospace-0.21.doc

This document was produced as a result of the discussions that occured at the Victoria Interop meeting.

Change Requests

Specify the key names and meanings for a small group of "essential" property keys

The minimum set which I would say we need mandatory names are

• vos.Owner
• vos.ModificationDate
• vos.Size
• vos.MimeType

-- PaulHarrison

I agree a list of the common properties would be useful.

How about Define each of the common (not mandatory) properties in an annex of the main specification.

Then, we post a separate change request for each property, including details of exactly what it means and how it is represented.

-- DaveMorris - 16 Jun 2006

Votes

name	vote	comment
PaulHarrison	+1

Clarify the use of the Format parameter in some calls

I believe that the original intention of Format was to specify a possible transformation of the data (mainly on export of table data from RDBMS based stores). In the current version of the document it reads as if this parameter is merely a description of the data - in which case mime-type suffices. In addition I am not sure if this parameter has any meaning for import operations.

-- PaulHarrison

I agree we need to clarify this. However, MIME type does not describe what we need.

Like property and protocol, we should add definitions of the common VO formats as an annex to the specification.

-- DaveMorris - 16 Jun 2006

Votes

name	vote	comment
PaulHarrison	+1