Discussion of the VOSpace 1.0 specification Document

The VOSpace-1.0 specification has been completed and submitted as an IVOA working draft.

The final versions are available here :

• Service specification

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
• 0 if you have no particular preference
• -1 if you think the proposal is useful but needs more work
• -2 if you disagree with the proposal

If you register a -1 or -2 vote, then please add a link to a page outlining your objections or comments.

Details and discussion of implementation plans are here.

Version 0.22

Change Requests

Allow typing of properties

<property uri="ivo://net.ivoa/properties/color" type="myschema.xsd">
 <color>
   <red>123</red>
   <blue>234</blue>
   <green>89</green>
 </color>
</property> 

Votes

Rename views to formats

Votes

Decoupled data servers

1. Client calls pushToVoSpace(<node>, <transfer>) returns <node> and <transfer> - the latter containing details for the data server
2. Client transfers data to data server
3. Client notifies VOSpace that transfer has been completed, e.g.

There are a couple of problems with this, however: the client has to call the space twice and might forget to do the notification call and what happens if the transfer fails or is not done. An alternate approach is to do the data transfer first of all and then register the data object with the node including its physical location so pushToVoSpace becomes:

1. Client transfer data to data server
2. Client registers data with VOSpace: register(, URI of location) returns the registered <node>

This is actually the only transfer method which needs a modification: all the others work fine with decoupled servers. In fact, instead of adding an additional operation, we can modify pushToVoSpace either to have an additional URI argument: pushToVoSpace(<node>, <transfer>, location-uri) or we could just incorporate the location-uri into the transfer so that if the protocol contains an endpoint then that endpoint is interpreted to be the physical location of the data object.

One thing that would be useful is another operation to return the list of (decoupled) data servers (resources in SRB speak) that the VOSpace is using so I would suggest that we add a getDataServers operation.

Votes

copyNode and moveNode to operate across stores

See message for rationale of above itemized list:

1. make (file)name a mandatory node property
2. use pullDataToVOSpace with copyNode and moveNode to operate across stores
3. {copy|move}Node to support exception StoreFull
4. drop list paging in favor of filtering by property value

Apparently this democratic page accepts votes: Well, obviously I vote in favor of my comments, however, in case of disagreement I'd rather see how to use level 1 as is based on some real scenarios. Markus

Four points in one post, so I'll add comments as a similar list (DaveMorris).

1. make (file)name a mandatory node property
   • The name is in the node URI, so it is already mandatory
2. use pullDataToVOSpace with copyNode and moveNode to operate across stores
   • If services exchange SOAP messages, then this causes problems interoperability problems later on. All future services would have to support all the previous versions of the SOAP messages.
   • The current specification does support direct data transfer between services, but the control messages always come from the client. i.e. The client contacts service A and asks for a URL to access the data, and then calls service B and asks it to import the data from the URL.
   • See email and wiki for more details.
3. {copy|move}Node to support exception StoreFull
   • This is a good point, and we don't have anything in the specification to handle this. Should this be a new fault type, or do we just wrap it as a PermissionDenied fault with an appropriate message ? Either way, we probably need to add something to the specification to say what should happen.
4. drop list paging in favor of filtering by property value
   • Simple filtering on names (similar to Unix ls) is going to be added to version 1.0.
   • Complex filtering on property values (similar to Unix find) has been deferred version 1.1.
   • The paging is primarily intended to enable clients to handle large lists without exploding.
   • See email for more details.

Votes

Make the destination of CopyNode and MoveNode a simple uri

The advantage is it simplifies the standard doc (so many restrictions on node) and is much easier for client to use... as does not have to create a node object - simply create a uri for the destination.

Votes

Re-assess what metadata should be returned with various faults

Some faults need to return metadata beyond simply their type to convery meaningful information about exactly what has gone wrong. e.g. for a setDataNodeProperties call could specify several read-only properties amongst a larger number of properties, and the client would not know which were the properties in error without a list being returned in the fault.

Votes

Version 0.21

Changes

Changes for later versions of VOSpace

Consider adding an optional wildcard matching identifier to parameters for ListNodes

Reason for change: improved efficiency - if ListNodes always has to list the whole VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.

Use Case

-- PaulHarrison 19 Jun 2006

Votes

Add a FindNodes operation

This operation would allow a simple search on the VOSpace - the level of functionality would be similar to the unix "find" command.

Discussion of the VOSpace 1.0 specification Document

The VOSpace-1.0 specification has been completed and submitted as an IVOA working draft.

The final versions are available here :

• Service specification
• WSDL for 1.0 service
• Schema for 1.0 service

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
• 0 if you have no particular preference
• -1 if you think the proposal is useful but needs more work
• -2 if you disagree with the proposal

If you register a -1 or -2 vote, then please add a link to a page outlining your objections or comments.

Details and discussion of implementation plans are here.

Version 0.22

• vospace-0.22.doc

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

Change Requests

Allow typing of properties

<property uri="ivo://net.ivoa/properties/color" type="myschema.xsd">
 <color>
   <red>123</red>
   <blue>234</blue>
   <green>89</green>
 </color>
</property> 

Votes

Rename views to formats

Votes

Decoupled data servers

1. Client calls pushToVoSpace(<node>, <transfer>) returns <node> and <transfer> - the latter containing details for the data server
2. Client transfers data to data server
3. Client notifies VOSpace that transfer has been completed, e.g.

There are a couple of problems with this, however: the client has to call the space twice and might forget to do the notification call and what happens if the transfer fails or is not done. An alternate approach is to do the data transfer first of all and then register the data object with the node including its physical location so pushToVoSpace becomes:

1. Client transfer data to data server
2. Client registers data with VOSpace: register(, URI of location) returns the registered <node>

This is actually the only transfer method which needs a modification: all the others work fine with decoupled servers. In fact, instead of adding an additional operation, we can modify pushToVoSpace either to have an additional URI argument: pushToVoSpace(<node>, <transfer>, location-uri) or we could just incorporate the location-uri into the transfer so that if the protocol contains an endpoint then that endpoint is interpreted to be the physical location of the data object.

One thing that would be useful is another operation to return the list of (decoupled) data servers (resources in SRB speak) that the VOSpace is using so I would suggest that we add a getDataServers operation.

Votes

copyNode and moveNode to operate across stores

See message for rationale of above itemized list:

1. make (file)name a mandatory node property
2. use pullDataToVOSpace with copyNode and moveNode to operate across stores
3. {copy|move}Node to support exception StoreFull
4. drop list paging in favor of filtering by property value

Apparently this democratic page accepts votes: Well, obviously I vote in favor of my comments, however, in case of disagreement I'd rather see how to use level 1 as is based on some real scenarios. Markus

Four points in one post, so I'll add comments as a similar list (DaveMorris).

1. make (file)name a mandatory node property
   • The name is in the node URI, so it is already mandatory
2. use pullDataToVOSpace with copyNode and moveNode to operate across stores
   • If services exchange SOAP messages, then this causes problems interoperability problems later on. All future services would have to support all the previous versions of the SOAP messages.
   • The current specification does support direct data transfer between services, but the control messages always come from the client. i.e. The client contacts service A and asks for a URL to access the data, and then calls service B and asks it to import the data from the URL.
   • See email and wiki for more details.
3. {copy|move}Node to support exception StoreFull
   • This is a good point, and we don't have anything in the specification to handle this. Should this be a new fault type, or do we just wrap it as a PermissionDenied fault with an appropriate message ? Either way, we probably need to add something to the specification to say what should happen.
4. drop list paging in favor of filtering by property value
   • Simple filtering on names (similar to Unix ls) is going to be added to version 1.0.
   • Complex filtering on property values (similar to Unix find) has been deferred version 1.1.
   • The paging is primarily intended to enable clients to handle large lists without exploding.
   • See email for more details.

Votes

Make the destination of CopyNode and MoveNode a simple uri

The advantage is it simplifies the standard doc (so many restrictions on node) and is much easier for client to use... as does not have to create a node object - simply create a uri for the destination.

Votes

Re-assess what metadata should be returned with various faults

Some faults need to return metadata beyond simply their type to convery meaningful information about exactly what has gone wrong. e.g. for a setDataNodeProperties call could specify several read-only properties amongst a larger number of properties, and the client would not know which were the properties in error without a list being returned in the fault.

Votes

Version 0.21

• vospace-0.21.doc

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

Changes

Changes for later versions of VOSpace

Consider adding an optional wildcard matching identifier to parameters for ListNodes

Reason for change: improved efficiency - if ListNodes always has to list the whole VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.

Use Case

-- PaulHarrison 19 Jun 2006

Votes

Add a FindNodes operation

This operation would allow a simple search on the VOSpace - the level of functionality would be similar to the unix "find" command.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Discussion of the VOSpace 1.0 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
• 0 if you have no particular preference
• -1 if you think the proposal is useful but needs more work
• -2 if you disagree with the proposal

If you register a -1 or -2 vote, then please add a link to a page outlining your objections or comments.

Details and discussion of implementation plans are here.

Version 0.22

• vospace-0.22.doc

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

Change Requests

Allow typing of properties

<property uri="ivo://net.ivoa/properties/color" type="myschema.xsd">
 <color>
   <red>123</red>
   <blue>234</blue>
   <green>89</green>
 </color>
</property> 

Votes

Rename views to formats

Votes

Decoupled data servers

1. Client calls pushToVoSpace(<node>, <transfer>) returns <node> and <transfer> - the latter containing details for the data server
2. Client transfers data to data server
3. Client notifies VOSpace that transfer has been completed, e.g.

There are a couple of problems with this, however: the client has to call the space twice and might forget to do the notification call and what happens if the transfer fails or is not done. An alternate approach is to do the data transfer first of all and then register the data object with the node including its physical location so pushToVoSpace becomes:

1. Client transfer data to data server
2. Client registers data with VOSpace: register(, URI of location) returns the registered <node>

This is actually the only transfer method which needs a modification: all the others work fine with decoupled servers. In fact, instead of adding an additional operation, we can modify pushToVoSpace either to have an additional URI argument: pushToVoSpace(<node>, <transfer>, location-uri) or we could just incorporate the location-uri into the transfer so that if the protocol contains an endpoint then that endpoint is interpreted to be the physical location of the data object.

One thing that would be useful is another operation to return the list of (decoupled) data servers (resources in SRB speak) that the VOSpace is using so I would suggest that we add a getDataServers operation.

Votes

copyNode and moveNode to operate across stores

See message for rationale of above itemized list:

1. make (file)name a mandatory node property
2. use pullDataToVOSpace with copyNode and moveNode to operate across stores
3. {copy|move}Node to support exception StoreFull
4. drop list paging in favor of filtering by property value

Apparently this democratic page accepts votes: Well, obviously I vote in favor of my comments, however, in case of disagreement I'd rather see how to use level 1 as is based on some real scenarios. Markus

Four points in one post, so I'll add comments as a similar list (DaveMorris).

1. make (file)name a mandatory node property
   • The name is in the node URI, so it is already mandatory
2. use pullDataToVOSpace with copyNode and moveNode to operate across stores
   • If services exchange SOAP messages, then this causes problems interoperability problems later on. All future services would have to support all the previous versions of the SOAP messages.
   • The current specification does support direct data transfer between services, but the control messages always come from the client. i.e. The client contacts service A and asks for a URL to access the data, and then calls service B and asks it to import the data from the URL.
   • See email and wiki for more details.
3. {copy|move}Node to support exception StoreFull
   • This is a good point, and we don't have anything in the specification to handle this. Should this be a new fault type, or do we just wrap it as a PermissionDenied fault with an appropriate message ? Either way, we probably need to add something to the specification to say what should happen.
4. drop list paging in favor of filtering by property value
   • Simple filtering on names (similar to Unix ls) is going to be added to version 1.0.
   • Complex filtering on property values (similar to Unix find) has been deferred version 1.1.
   • The paging is primarily intended to enable clients to handle large lists without exploding.
   • See email for more details.

Votes

Make the destination of CopyNode and MoveNode a simple uri

The advantage is it simplifies the standard doc (so many restrictions on node) and is much easier for client to use... as does not have to create a node object - simply create a uri for the destination.

Votes

Re-assess what metadata should be returned with various faults

Some faults need to return metadata beyond simply their type to convery meaningful information about exactly what has gone wrong. e.g. for a setDataNodeProperties call could specify several read-only properties amongst a larger number of properties, and the client would not know which were the properties in error without a list being returned in the fault.

Votes

Version 0.21

• vospace-0.21.doc

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

Changes

Changes for later versions of VOSpace

Consider adding an optional wildcard matching identifier to parameters for ListNodes

Reason for change: improved efficiency - if ListNodes always has to list the whole VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.

Use Case

-- PaulHarrison 19 Jun 2006

Votes

Add a FindNodes operation

This operation would allow a simple search on the VOSpace - the level of functionality would be similar to the unix "find" command.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

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
• 0 if you have no particular preference
• -1 if you think the proposal is useful but needs more work
• -2 if you disagree with the proposal

If you register a -1 or -2 vote, then please add a link to a page outlining your objections or comments.

Details and discussion of implementation plans are here.

Version 0.22

• vospace-0.22.doc

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

Change Requests

Allow typing of properties

<property uri="ivo://net.ivoa/properties/color" type="myschema.xsd">
 <color>
   <red>123</red>
   <blue>234</blue>
   <green>89</green>
 </color>
</property> 

Votes

Rename views to formats

Votes

Decoupled data servers

1. Client calls pushToVoSpace(<node>, <transfer>) returns <node> and <transfer> - the latter containing details for the data server
2. Client transfers data to data server
3. Client notifies VOSpace that transfer has been completed, e.g.

There are a couple of problems with this, however: the client has to call the space twice and might forget to do the notification call and what happens if the transfer fails or is not done. An alternate approach is to do the data transfer first of all and then register the data object with the node including its physical location so pushToVoSpace becomes:

1. Client transfer data to data server
2. Client registers data with VOSpace: register(, URI of location) returns the registered <node>

This is actually the only transfer method which needs a modification: all the others work fine with decoupled servers. In fact, instead of adding an additional operation, we can modify pushToVoSpace either to have an additional URI argument: pushToVoSpace(<node>, <transfer>, location-uri) or we could just incorporate the location-uri into the transfer so that if the protocol contains an endpoint then that endpoint is interpreted to be the physical location of the data object.

One thing that would be useful is another operation to return the list of (decoupled) data servers (resources in SRB speak) that the VOSpace is using so I would suggest that we add a getDataServers operation.

Votes

1. make (file)name a mandatory node property
2. use pullDataToVOSpace with copyNode and moveNode to operate across stores
3. {copy|move}Node to support exception StoreFull
4. drop list paging in favor of filtering by property value

Apparently this democratic page accepts votes: Well, obviously I vote in favor of my comments, however, in case of disagreement I'd rather see how to use level 1 as is based on some real scenarios. Markus

Four points in one post, so I'll add comments as a similar list (DaveMorris).

1. make (file)name a mandatory node property
   • The name is in the node URI, so it is already mandatory
2. use pullDataToVOSpace with copyNode and moveNode to operate across stores
   • If services exchange SOAP messages, then this causes problems interoperability problems later on. All future services would have to support all the previous versions of the SOAP messages.
   • The current specification does support direct data transfer between services, but the control messages always come from the client. i.e. The client contacts service A and asks for a URL to access the data, and then calls service B and asks it to import the data from the URL.
   • See email and wiki for more details.
3. {copy|move}Node to support exception StoreFull

1. drop list paging in favor of filtering by property value
   • Simple filtering on names (similar to Unix ls) is going to be added to version 1.0.
   • Complex filtering on property values (similar to Unix find) has been deferred version 1.1.
   • The paging is primarily intended to enable clients to handle large lists without exploding.
   • See email for more details.

Votes

Make the destination of CopyNode and MoveNode a simple uri

The advantage is it simplifies the standard doc (so many restrictions on node) and is much easier for client to use... as does not have to create a node object - simply create a uri for the destination.

Votes

Re-assess what metadata should be returned with various faults

Some faults need to return metadata beyond simply their type to convery meaningful information about exactly what has gone wrong. e.g. for a setDataNodeProperties call could specify several read-only properties amongst a larger number of properties, and the client would not know which were the properties in error without a list being returned in the fault.

Votes

Version 0.21

• vospace-0.21.doc

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

Changes

Changes for later versions of VOSpace

Consider adding an optional wildcard matching identifier to parameters for ListNodes

Reason for change: improved efficiency - if ListNodes always has to list the whole VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.

Use Case

-- PaulHarrison 19 Jun 2006

Votes

Add a FindNodes operation

This operation would allow a simple search on the VOSpace - the level of functionality would be similar to the unix "find" command.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

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
• 0 if you have no particular preference
• -1 if you think the proposal is useful but needs more work
• -2 if you disagree with the proposal

If you register a -1 or -2 vote, then please add a link to a page outlining your objections or comments.

Details and discussion of implementation plans are here.

Version 0.22

• vospace-0.22.doc

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

Change Requests

Allow typing of properties

<property uri="ivo://net.ivoa/properties/color" type="myschema.xsd">
 <color>
   <red>123</red>
   <blue>234</blue>
   <green>89</green>
 </color>
</property> 

Votes

Rename views to formats

Votes

Decoupled data servers

1. Client calls pushToVoSpace(<node>, <transfer>) returns <node> and <transfer> - the latter containing details for the data server
2. Client transfers data to data server
3. Client notifies VOSpace that transfer has been completed, e.g.

There are a couple of problems with this, however: the client has to call the space twice and might forget to do the notification call and what happens if the transfer fails or is not done. An alternate approach is to do the data transfer first of all and then register the data object with the node including its physical location so pushToVoSpace becomes:

1. Client transfer data to data server
2. Client registers data with VOSpace: register(, URI of location) returns the registered <node>

This is actually the only transfer method which needs a modification: all the others work fine with decoupled servers. In fact, instead of adding an additional operation, we can modify pushToVoSpace either to have an additional URI argument: pushToVoSpace(<node>, <transfer>, location-uri) or we could just incorporate the location-uri into the transfer so that if the protocol contains an endpoint then that endpoint is interpreted to be the physical location of the data object.

One thing that would be useful is another operation to return the list of (decoupled) data servers (resources in SRB speak) that the VOSpace is using so I would suggest that we add a getDataServers operation.

Votes

See message for rationale of above itemized list:

1. make (file)name a mandatory node property
2. use pullDataToVOSpace with copyNode and moveNode to operate across stores
3. {copy|move}Node to support exception StoreFull
4. drop list paging in favor of filtering by property value

Apparently this democratic page accepts votes: Well, obviously I vote in favor of my comments, however, in case of disagreement I'd rather see how to use level 1 as is based on some real scenarios. Markus

Votes

Make the destination of CopyNode and MoveNode a simple uri

The advantage is it simplifies the standard doc (so many restrictions on node) and is much easier for client to use... as does not have to create a node object - simply create a uri for the destination.

Votes

Re-assess what metadata should be returned with various faults

Some faults need to return metadata beyond simply their type to convery meaningful information about exactly what has gone wrong. e.g. for a setDataNodeProperties call could specify several read-only properties amongst a larger number of properties, and the client would not know which were the properties in error without a list being returned in the fault.

Votes

Version 0.21

• vospace-0.21.doc

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

Changes

Changes for later versions of VOSpace

Consider adding an optional wildcard matching identifier to parameters for ListNodes

Reason for change: improved efficiency - if ListNodes always has to list the whole VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.

Use Case

-- PaulHarrison 19 Jun 2006

Votes

Add a FindNodes operation

This operation would allow a simple search on the VOSpace - the level of functionality would be similar to the unix "find" command.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

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

• 0 if you have no particular preference

Version 0.22

• vospace-0.22.doc

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

Change Requests

Allow typing of properties

<property uri="ivo://net.ivoa/properties/color" type="myschema.xsd">
 <color>
   <red>123</red>
   <blue>234</blue>
   <green>89</green>
 </color>
</property> 

Votes

Rename views to formats

Votes

Decoupled data servers

1. Client calls pushToVoSpace(<node>, <transfer>) returns <node> and <transfer> - the latter containing details for the data server
2. Client transfers data to data server
3. Client notifies VOSpace that transfer has been completed, e.g.

There are a couple of problems with this, however: the client has to call the space twice and might forget to do the notification call and what happens if the transfer fails or is not done. An alternate approach is to do the data transfer first of all and then register the data object with the node including its physical location so pushToVoSpace becomes:

1. Client transfer data to data server
2. Client registers data with VOSpace: register(, URI of location) returns the registered <node>

This is actually the only transfer method which needs a modification: all the others work fine with decoupled servers. In fact, instead of adding an additional operation, we can modify pushToVoSpace either to have an additional URI argument: pushToVoSpace(<node>, <transfer>, location-uri) or we could just incorporate the location-uri into the transfer so that if the protocol contains an endpoint then that endpoint is interpreted to be the physical location of the data object.

One thing that would be useful is another operation to return the list of (decoupled) data servers (resources in SRB speak) that the VOSpace is using so I would suggest that we add a getDataServers operation.

Votes

See message for rationale of above itemized list:

1. make (file)name a mandatory node property
2. use pullDataToVOSpace with copyNode and moveNode to operate across stores
3. {copy|move}Node to support exception StoreFull
4. drop list paging in favor of filtering by property value

Apparently this democratic page accepts votes: Well, obviously I vote in favor of my comments, however, in case of disagreement I'd rather see how to use level 1 as is based on some real scenarios. Markus

Votes

Make the destination of CopyNode and MoveNode a simple uri

The advantage is it simplifies the standard doc (so many restrictions on node) and is much easier for client to use... as does not have to create a node object - simply create a uri for the destination.

Votes

Re-assess what metadata should be returned with various faults

Some faults need to return metadata beyond simply their type to convery meaningful information about exactly what has gone wrong. e.g. for a setDataNodeProperties call could specify several read-only properties amongst a larger number of properties, and the client would not know which were the properties in error without a list being returned in the fault.

Votes

Version 0.21

• vospace-0.21.doc

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

Changes

Changes for later versions of VOSpace

Consider adding an optional wildcard matching identifier to parameters for ListNodes

Reason for change: improved efficiency - if ListNodes always has to list the whole VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.

Use Case

-- PaulHarrison 19 Jun 2006

Votes

Add a FindNodes operation

This operation would allow a simple search on the VOSpace - the level of functionality would be similar to the unix "find" command.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

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

Details and discussion of implementation plans are here.

Version 0.22

• vospace-0.22.doc

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

Change Requests

1. make (file)name a mandatory node property
2. use pullDataToVOSpace with copyNode and moveNode to operate across stores
3. {copy|move}Node to support exception StoreFull
4. drop list paging in favor of filtering by property value

Apparently this democratic page accepts votes: Well, obviously I vote in favor of my comments, however, in case of disagreement I'd rather see how to use level 1 as is based on some real scenarios. Markus

Votes

Make the destination of CopyNode and MoveNode a simple uri

The advantage is it simplifies the standard doc (so many restrictions on node) and is much easier for client to use... as does not have to create a node object - simply create a uri for the destination.

Votes

Re-assess what metadata should be returned with various faults

Some faults need to return metadata beyond simply their type to convery meaningful information about exactly what has gone wrong. e.g. for a setDataNodeProperties call could specify several read-only properties amongst a larger number of properties, and the client would not know which were the properties in error without a list being returned in the fault.

Votes

Version 0.21

• vospace-0.21.doc

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

Changes

Changes for later versions of VOSpace

Consider adding an optional wildcard matching identifier to parameters for ListNodes

Reason for change: improved efficiency - if ListNodes always has to list the whole VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.

Use Case

-- PaulHarrison 19 Jun 2006

Votes

Add a FindNodes operation

This operation would allow a simple search on the VOSpace - the level of functionality would be similar to the unix "find" command.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

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

Details and discussion of implementation plans are here.

Version 0.22

• vospace-0.22.doc

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

Change Requests

Make the destination of CopyNode and MoveNode a simple uri

The advantage is it simplifies the standard doc (so many restrictions on node) and is much easier for client to use... as does not have to create a node object - simply create a uri for the destination.

Votes

Re-assess what metadata should be returned with various faults

Some faults need to return metadata beyond simply their type to convery meaningful information about exactly what has gone wrong. e.g. for a setDataNodeProperties call could specify several read-only properties amongst a larger number of properties, and the client would not know which were the properties in error without a list being returned in the fault.

Votes

Version 0.21

• vospace-0.21.doc

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

Changes

Changes for later versions of VOSpace

Consider adding an optional wildcard matching identifier to parameters for ListNodes

Reason for change: improved efficiency - if ListNodes always has to list the whole VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.

Use Case

-- PaulHarrison 19 Jun 2006

Votes

Add a FindNodes operation

This operation would allow a simple search on the VOSpace - the level of functionality would be similar to the unix "find" command.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

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

Details and discussion of implementation plans are here.

Version 0.22

Change Requests

Make the destination of CopyNode and MoveNode a simple uri

The advantage is it simplifies the standard doc (so many restrictions on node) and is much easier for client to use... as does not have to create a node object - simply create a uri for the destination.

Votes

Re-assess what metadata should be returned with various faults

Some faults need to return metadata beyond simply their type to convery meaningful information about exactly what has gone wrong. e.g. for a setDataNodeProperties call could specify several read-only properties amongst a larger number of properties, and the client would not know which were the properties in error without a list being returned in the fault.

Votes

Version 0.21

• vospace-0.21.doc

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

Changes

Changes for later versions of VOSpace

Consider adding an optional wildcard matching identifier to parameters for ListNodes

Reason for change: improved efficiency - if ListNodes always has to list the whole VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.

Use Case

-- PaulHarrison 19 Jun 2006

Votes

Add a FindNodes operation

This operation would allow a simple search on the VOSpace - the level of functionality would be similar to the unix "find" command.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

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

Details and discussion of implementation plans are here.

Version 0.22

• vospace-0.22.doc

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

Change Requests

Make the destination of CopyNode and MoveNode a simple uri

The advantage is it simplifies the standard doc (so many restrictions on node) and is much easier for client to use... as does not have to create a node object - simply create a uri for the destination.

Votes

Re-assess what metadata should be returned with various faults

Some faults need to return metadata beyond simply their type to convery meaningful information about exactly what has gone wrong. e.g. for a setDataNodeProperties call could specify several read-only properties amongst a larger number of properties, and the client would not know which were the properties in error without a list being returned in the fault.

Votes

Version 0.21

• vospace-0.21.doc

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

Changes

Changes for later versions of VOSpace

Consider adding an optional wildcard matching identifier to parameters for ListNodes

Reason for change: improved efficiency - if ListNodes always has to list the whole VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.

Use Case

-- PaulHarrison 19 Jun 2006

Votes

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

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

Details and discussion of implementation plans are here.

Version 0.22

• vospace-0.22.doc

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

Change Requests

Re-assess what metadata should be returned with various faults

Some faults need to return metadata beyond simply their type to convery meaningful information about exactly what has gone wrong. e.g. for a setDataNodeProperties call could specify several read-only properties amongst a larger number of properties, and the client would not know which were the properties in error without a list being returned in the fault.

Votes

Version 0.21

• vospace-0.21.doc

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

Changes

Changes for later versions of VOSpace

Consider adding an optional wildcard matching identifier to parameters for ListNodes

Reason for change: improved efficiency - if ListNodes always has to list the whole VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.

Use Case

-- PaulHarrison 19 Jun 2006

Votes

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

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

Details and discussion of implementation plans are here.

Change Requests

Mandate and define at least one transport protocol

I recommend http be mandatory.

see detailed discussion in email thread http://www.ivoa.net/forum/vospace/0606/0097.htm

-- PaulHarrison

• Which version, http-1.0 or http-1.1 ?
• Which methods http-get, http-put or both ?
  • For a space that stores public images, then http-1.1-get makes sense.
  • For a space that allows upload to sensitive database tables, then http-1.x-put does not have sufficient authentication.

-- DaveMorris - 16 Jun 2006

I think that where VOSpace is acting as a http server then it would be good to mandate http-1.1 compliance - it does fix issues with 1.0 and afterall it is a 7 year old specification now....

As far as a compliance statement goes - how about

(http-1.1-get or https-1.1-get) and (http-1.1-put or https-1.1-put)

-- PaulHarrison - 19 Jun 2006

Making some form of HTTP mandatory makes it easier to write clients and harder to write services. VOSpace fails unless we get useful services, and services are already harder to write than clients.

-- GuyRixon - 03 Jul 2006

we are already implicitly mandating http for the "control" interface - i.e. the web service - as far as implementors are concerned adding http-get would be not a great burden for the implementor - without a mandatory transport the success of the use case where a client sets up direct space to space transfers is not guaranteed, so the fallback would have to be copying the data to the client which understands the transport of each space and then transferring to the second space.

-- PaulHarrison - 04 Jul 2006

Votes

Specify as optional a small list of well known transport protocols

• ftp
• gridftp
• file - direct access to the file system

-- PaulHarrison

Agree with the list of common protocols.

Defined in a annex to the main specification, including a standard URI and details of the protocol specification (can be just short note and a reference to the external specification).

e.g.

HTTP 1.1 get
URI
    ivo://....vospace/protocols/http-1.1-get
Description :
    Get data using the HTTP-1.1 GET method as defined in RFC2616.
    http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.3

Votes

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

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

-- PaulHarrison

Agree with the list of common properties.

Defined in a annex to the main specification, including a standard URI and details of what each property means and how it is represented.

e.g.

Data created date
KEY
    vos.data.created.date
Description :
    A read-only property generated by the server.
    Indicating when the data contents were originally created.
    Formatted as a ISO 8601 date-time [yyyy-mm-ddTHH:MM:SS.SSS]
----
Data modified date
KEY
    vos.data.modified.date
Description :
    A read-only property generated by the server.
    Indicating when the data contents were last modified.
    Formatted as a ISO 8601 date-time [yyyy-mm-ddTHH:MM:SS.SSS]

Note - As VOSpace-1.0 does not support append, the only way the created and modified dates will be different is if the server modifies the data underneath.

-- DaveMorris - 16 Jun 2006

Votes

Clarify the use of the Format parameter in some calls

Votes

Change "exception" to "fault"

Votes

Consider adding an optional identifier list to the parameters for ListNodes

Reason for change: improved efficiency - if ListNodes always has to list the whole VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.

Use Case

-- PaulHarrison 19 Jun 2006

Votes

Reconsider getNodeProperties and setNodeProperties

Votes

Semantics not clear for setNodeProperties

• how to delete a property - does a null value of the property pair denote this?
• does the whole set of node properties given as an argument replace the whole set for the node, or is a union operation performed.
• interaction with the "read-only" properties in these scenarios...

Agree, need to make this clearer.

• Null value deletes property.
• Operation is union not replace.
• Server throws PermissionDenined for read-only properties.
  • what if only one of the list of properties is read-only? - need to signal which are the bad properties in the exception - also PermissionDenied could be confusing as this normally refers to the permissions on the data object which could potentially be changed in future versions of VOSpace - certain properties are fundamentally readOnly and so would

-- DaveMorris - 16 Jun 2006

Votes

Change names of parameters for moveNode and copyNode

Yep, source and destination are probably better. As long as we make it clear that these are internal locations, not references to external locations.

-- DaveMorris - 16 Jun 2006

Votes

Rename bulk data transfer operations

• I stilll find the data transfer operations confusing- I think that the basic problem is that the push and pull verbs are opposite in meaning and viewed from opposite perspectives. I have a new set of proposals

which I think are better because

1. the overall objective of the operation is the first verb
2. the active party in the transfer is identified
3. the direction of the transfer is then related to the active party.

-- PaulHarrison - 13 Jun 2006

This is a change to the specification not the WSDL, move this to the specification change page.

-- DaveMorris - 16 Jun 2006

I find the newly-proposed names more confusing. It's not obvious to me whether "import" moves data into VOSpace or into the client of VOSpace; similarly with "export".

-- GuyRixon - 04 Jul 2006

Votes

New GetPropertyKeys operation

Should return a list of the keys with an indication of which ones relate to read-only properties.

-- PaulHarrison - 13 Jun 2006

I agree with adding the method. However, this should be changed in the specification first, not the WSDL. Move this to the specification change page.

-- DaveMorris - 16 Jun 2006

Suggestion 1: this operation only returns the set of properties understood by the service. Collating the other properties doesn't seem useful and might be expensive to implement.

Suggestion 2: for the properties of interest, return metadata roughly equivalent to those for a CEA parameter:

• Key (i.e. formal name)
• Name to show in UI
• Description
• Whether writeable by client (probably as boolean attribute "readOnly")
• UCD 1+
• Unit

-- GuyRixon - 04 Jul 2006

Suggestion 2 does have some appeal. Suggestion 1, however, I am not so keen on, the original intention of this proposal was to be able to find out about the "custom properties" that clients might be using, rather than simply the ones that the service "understands" - for the extra metadata to be supplied though it would imply that an extra "registerPropertyMetadata" operation would be needed before a client could set the property.

And I do not see this being at all expensive to implement - it is much easier to implement than storing the property values of each of the property instances for each of the stored data objects, and we already require that.

-- PaulHarrison - 04 Jul 2006

Votes

Re-assess the semantics of creating a server named data object.

Votes

Rename Status (of Node object) to TransferStatus

The Status member of the Node object is really referring to the transfer status.

Votes

Consider interactions when two clients attempt operations on same data object

use case

client 2 attempts to delete a file that client 1 is currently downloading via a "pull" transfer.

As specified at the moment, Client 1 could have a data transfer cut off with out any real knowledge of why, or client 2 could receive a PermissionDenied fault

Possible solutions

• add a DataInUse fault to the destructive manipulation methods
• add a dataBeingRead to the list of Status values

This use case is actually quite an implementation challenge....involves close interaction with the states of the actual data streams for the transports.

Votes

Expand "expired" Node status to include "failed"

perhaps failed is a better name can then encompass the case where a partial data transfer has occured and failed half way, for some reason other than expiry

Votes

Different type of list operation that returns only the uris...

Proposed (and provisionally agreed by DaveMorris, MatthewGraham and GuyRixon) that we include a "level" parameter to select what is returned. The returned elements are always node elements but:

• level="minimal" returns nodes with only the URI child;
• level="standard" returns nodes with the properties as well;
• level="extended" alls the return of derived types of nodes.

(Naming of the levels can be tweaked if necessary.) "Derived types of nodes" allows implementors to design special nodes (e.g. LdapDataNode) that have all the parts of a normal node and also extra children. The level parameter protects the clients from parser grief when derived node-types are in play.

The URI child might become an attribute of the node element.

-- GuyRixon - 04 Jul 2006

This design does not seem very OO to me - too may meanings are being attached to level - we are saying that the ListNodes operation returns a type Node, but for level="minimal" actually something is returned that is an "incomplete" node though it is still being called a node. It would seem cleaner to have a different operation ListIdentifiers that returned an identifier array for this case.

the level=extended seems not to be within scope of 1.0 - It also seems to be confusing the metadata about a node with the data in a node.

-- PaulHarrison - 05 Jul 2006

Votes

Confusing that pullDataToVoSpace, pushDataFromVoSpace return transfer object.

The transfer object contains a location element which is intended to be the uri that pullDataFromVoSpace and pushDataToVoSpace supply as an output parameter, so it is confusing that pullDataToVoSpace, pushDataFromVoSpace return a uri for a transfer when for those methods the uri for transfer is an input parameter.

Recommend that the pullDataToVoSpace, pushDataFromVoSpace return only what is necessary for the client to know - this might mean removing the transfer object from the return list, or refactoring the transfer object - global analysis needed.

Votes

Need to have describe how VOSpace should be registered

Votes

Transports operation needs to return the direction of operation

Votes

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

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

Details and discussion of implementation plans are here.

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

Mandate and define at least one transport protocol

I recommend http be mandatory.

see detailed discussion in email thread http://www.ivoa.net/forum/vospace/0606/0097.htm

-- PaulHarrison

• Which version, http-1.0 or http-1.1 ?
• Which methods http-get, http-put or both ?
  • For a space that stores public images, then http-1.1-get makes sense.
  • For a space that allows upload to sensitive database tables, then http-1.x-put does not have sufficient authentication.

-- DaveMorris - 16 Jun 2006

I think that where VOSpace is acting as a http server then it would be good to mandate http-1.1 compliance - it does fix issues with 1.0 and afterall it is a 7 year old specification now....

As far as a compliance statement goes - how about

(http-1.1-get or https-1.1-get) and (http-1.1-put or https-1.1-put)

-- PaulHarrison - 19 Jun 2006

Making some form of HTTP mandatory makes it easier to write clients and harder to write services. VOSpace fails unless we get useful services, and services are already harder to write than clients.

-- GuyRixon - 03 Jul 2006

we are already implicitly mandating http for the "control" interface - i.e. the web service - as far as implementors are concerned adding http-get would be not a great burden for the implementor - without a mandatory transport the success of the use case where a client sets up direct space to space transfers is not guaranteed, so the fallback would have to be copying the data to the client which understands the transport of each space and then transferring to the second space.

-- PaulHarrison - 04 Jul 2006

Votes

Specify as optional a small list of well known transport protocols

• ftp
• gridftp
• file - direct access to the file system

-- PaulHarrison

Agree with the list of common protocols.

Defined in a annex to the main specification, including a standard URI and details of the protocol specification (can be just short note and a reference to the external specification).

e.g.

HTTP 1.1 get
URI
    ivo://....vospace/protocols/http-1.1-get
Description :
    Get data using the HTTP-1.1 GET method as defined in RFC2616.
    http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.3

-- DaveMorris - 16 Jun 2006

Votes

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

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

-- PaulHarrison

Agree with the list of common properties.

Defined in a annex to the main specification, including a standard URI and details of what each property means and how it is represented.

e.g.

Data created date
KEY
    vos.data.created.date
Description :
    A read-only property generated by the server.
    Indicating when the data contents were originally created.
    Formatted as a ISO 8601 date-time [yyyy-mm-ddTHH:MM:SS.SSS]
----
Data modified date
KEY
    vos.data.modified.date
Description :
    A read-only property generated by the server.
    Indicating when the data contents were last modified.
    Formatted as a ISO 8601 date-time [yyyy-mm-ddTHH:MM:SS.SSS]

Note - As VOSpace-1.0 does not support append, the only way the created and modified dates will be different is if the server modifies the data underneath.

-- DaveMorris - 16 Jun 2006

Votes

Clarify the use of the Format parameter in some calls

Votes

Change "exception" to "fault"

Votes

Consider adding an optional wildcard matching identifier to parameters for ListNodes

Reason for change: improved efficiency - if ListNodes always has to list the whole VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.

Use Case

-- PaulHarrison 19 Jun 2006

Votes

Consider adding an optional identifier list to the parameters for ListNodes

Reason for change: improved efficiency - if ListNodes always has to list the whole VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.

Use Case

-- PaulHarrison 19 Jun 2006

Votes

Reconsider getNodeProperties and setNodeProperties

Votes

Semantics not clear for setNodeProperties

• how to delete a property - does a null value of the property pair denote this?
• does the whole set of node properties given as an argument replace the whole set for the node, or is a union operation performed.
• interaction with the "read-only" properties in these scenarios...

Agree, need to make this clearer.

• Null value deletes property.
• Operation is union not replace.
• Server throws PermissionDenined for read-only properties.
  • what if only one of the list of properties is read-only? - need to signal which are the bad properties in the exception - also PermissionDenied could be confusing as this normally refers to the permissions on the data object which could potentially be changed in future versions of VOSpace - certain properties are fundamentally readOnly and so would

-- DaveMorris - 16 Jun 2006

Votes

Change names of parameters for moveNode and copyNode

Yep, source and destination are probably better. As long as we make it clear that these are internal locations, not references to external locations.

-- DaveMorris - 16 Jun 2006

Votes

Rename bulk data transfer operations

• I stilll find the data transfer operations confusing- I think that the basic problem is that the push and pull verbs are opposite in meaning and viewed from opposite perspectives. I have a new set of proposals

which I think are better because

1. the overall objective of the operation is the first verb
2. the active party in the transfer is identified
3. the direction of the transfer is then related to the active party.

-- PaulHarrison - 13 Jun 2006

This is a change to the specification not the WSDL, move this to the specification change page.

-- DaveMorris - 16 Jun 2006

I find the newly-proposed names more confusing. It's not obvious to me whether "import" moves data into VOSpace or into the client of VOSpace; similarly with "export".

-- GuyRixon - 04 Jul 2006

Votes

New GetPropertyKeys operation

Should return a list of the keys with an indication of which ones relate to read-only properties.

-- PaulHarrison - 13 Jun 2006

I agree with adding the method. However, this should be changed in the specification first, not the WSDL. Move this to the specification change page.

-- DaveMorris - 16 Jun 2006

Suggestion 1: this operation only returns the set of properties understood by the service. Collating the other properties doesn't seem useful and might be expensive to implement.

Suggestion 2: for the properties of interest, return metadata roughly equivalent to those for a CEA parameter:

• Key (i.e. formal name)
• Name to show in UI
• Description
• Whether writeable by client (probably as boolean attribute "readOnly")
• UCD 1+
• Unit

-- GuyRixon - 04 Jul 2006

Suggestion 2 does have some appeal. Suggestion 1, however, I am not so keen on, the original intention of this proposal was to be able to find out about the "custom properties" that clients might be using, rather than simply the ones that the service "understands" - for the extra metadata to be supplied though it would imply that an extra "registerPropertyMetadata" operation would be needed before a client could set the property.

And I do not see this being at all expensive to implement - it is much easier to implement than storing the property values of each of the property instances for each of the stored data objects, and we already require that.

-- PaulHarrison - 04 Jul 2006

Votes

Re-assess what metadata should be returned with various faults

Some faults need to return metadata beyond simply their type to convery meaningful information about exactly what has gone wrong. e.g. for a setDataNodeProperties call could specify several read-only properties amongst a larger number of properties, and the client would not know which were the properties in error without a list being returned in the fault.

Votes

Re-assess the semantics of creating a server named data object.

Votes

Rename Status (of Node object) to TransferStatus

The Status member of the Node object is really referring to the transfer status.

Votes

Consider interactions when two clients attempt operations on same data object

use case

client 2 attempts to delete a file that client 1 is currently downloading via a "pull" transfer.

As specified at the moment, Client 1 could have a data transfer cut off with out any real knowledge of why, or client 2 could receive a PermissionDenied fault

Possible solutions

• add a DataInUse fault to the destructive manipulation methods
• add a dataBeingRead to the list of Status values

This use case is actually quite an implementation challenge....involves close interaction with the states of the actual data streams for the transports.

Votes

Expand "expired" Node status to include "failed"

perhaps failed is a better name can then encompass the case where a partial data transfer has occured and failed half way, for some reason other than expiry

Votes

Different type of list operation that returns only the uris...

Proposed (and provisionally agreed by DaveMorris, MatthewGraham and GuyRixon) that we include a "level" parameter to select what is returned. The returned elements are always node elements but:

• level="minimal" returns nodes with only the URI child;
• level="standard" returns nodes with the properties as well;
• level="extended" alls the return of derived types of nodes.

(Naming of the levels can be tweaked if necessary.) "Derived types of nodes" allows implementors to design special nodes (e.g. LdapDataNode) that have all the parts of a normal node and also extra children. The level parameter protects the clients from parser grief when derived node-types are in play.

The URI child might become an attribute of the node element.

-- GuyRixon - 04 Jul 2006

This design does not seem very OO to me - too may meanings are being attached to level - we are saying that the ListNodes operation returns a type Node, but for level="minimal" actually something is returned that is an "incomplete" node though it is still being called a node. It would seem cleaner to have a different operation ListIdentifiers that returned an identifier array for this case.

the level=extended seems not to be within scope of 1.0 - It also seems to be confusing the metadata about a node with the data in a node.

-- PaulHarrison - 05 Jul 2006

Votes

Confusing that pullDataToVoSpace, pushDataFromVoSpace return transfer object.

The transfer object contains a location element which is intended to be the uri that pullDataFromVoSpace and pushDataToVoSpace supply as an output parameter, so it is confusing that pullDataToVoSpace, pushDataFromVoSpace return a uri for a transfer when for those methods the uri for transfer is an input parameter.

Recommend that the pullDataToVoSpace, pushDataFromVoSpace return only what is necessary for the client to know - this might mean removing the transfer object from the return list, or refactoring the transfer object - global analysis needed.

Votes

Need to have describe how VOSpace should be registered

Votes

name <-- -->	vote	comment
GuyRixon	+1
PaulHarrison	+1	proposer

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

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

Details and discussion of implementation plans are here.

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

Mandate and define at least one transport protocol

I recommend http be mandatory.

see detailed discussion in email thread http://www.ivoa.net/forum/vospace/0606/0097.htm

-- PaulHarrison

• Which version, http-1.0 or http-1.1 ?
• Which methods http-get, http-put or both ?
  • For a space that stores public images, then http-1.1-get makes sense.
  • For a space that allows upload to sensitive database tables, then http-1.x-put does not have sufficient authentication.

-- DaveMorris - 16 Jun 2006

I think that where VOSpace is acting as a http server then it would be good to mandate http-1.1 compliance - it does fix issues with 1.0 and afterall it is a 7 year old specification now....

As far as a compliance statement goes - how about

(http-1.1-get or https-1.1-get) and (http-1.1-put or https-1.1-put)

-- PaulHarrison - 19 Jun 2006

Making some form of HTTP mandatory makes it easier to write clients and harder to write services. VOSpace fails unless we get useful services, and services are already harder to write than clients.

-- GuyRixon - 03 Jul 2006

we are already implicitly mandating http for the "control" interface - i.e. the web service - as far as implementors are concerned adding http-get would be not a great burden for the implementor - without a mandatory transport the success of the use case where a client sets up direct space to space transfers is not guaranteed, so the fallback would have to be copying the data to the client which understands the transport of each space and then transferring to the second space.

-- PaulHarrison - 04 Jul 2006

Votes

Specify as optional a small list of well known transport protocols

• ftp
• gridftp
• file - direct access to the file system

-- PaulHarrison

Agree with the list of common protocols.

Defined in a annex to the main specification, including a standard URI and details of the protocol specification (can be just short note and a reference to the external specification).

e.g.

HTTP 1.1 get
URI
    ivo://....vospace/protocols/http-1.1-get
Description :
    Get data using the HTTP-1.1 GET method as defined in RFC2616.
    http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.3

-- DaveMorris - 16 Jun 2006

Votes

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

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

-- PaulHarrison

Agree with the list of common properties.

Defined in a annex to the main specification, including a standard URI and details of what each property means and how it is represented.

e.g.

Data created date
KEY
    vos.data.created.date
Description :
    A read-only property generated by the server.
    Indicating when the data contents were originally created.
    Formatted as a ISO 8601 date-time [yyyy-mm-ddTHH:MM:SS.SSS]
----
Data modified date
KEY
    vos.data.modified.date
Description :
    A read-only property generated by the server.
    Indicating when the data contents were last modified.
    Formatted as a ISO 8601 date-time [yyyy-mm-ddTHH:MM:SS.SSS]

Note - As VOSpace-1.0 does not support append, the only way the created and modified dates will be different is if the server modifies the data underneath.

-- DaveMorris - 16 Jun 2006

Votes

Clarify the use of the Format parameter in some calls

Votes

Change "exception" to "fault"

Votes

Consider adding an optional wildcard matching identifier to parameters for ListNodes

Reason for change: improved efficiency - if ListNodes always has to list the whole VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.

Use Case

-- PaulHarrison 19 Jun 2006

Votes

Consider adding an optional identifier list to the parameters for ListNodes

Reason for change: improved efficiency - if ListNodes always has to list the whole VOSpace then it is a pretty blunt instrument, especially as the number of data objects in the space increases.

Use Case

-- PaulHarrison 19 Jun 2006

Votes

Reconsider getNodeProperties and setNodeProperties

Votes

Semantics not clear for setNodeProperties

• how to delete a property - does a null value of the property pair denote this?
• does the whole set of node properties given as an argument replace the whole set for the node, or is a union operation performed.
• interaction with the "read-only" properties in these scenarios...