VoSpace 2.x

SetNodeProperties

Set the properties for a specific node.

Parameters

• Target - The URI of an existing node. note
  • vos://[service]/000-517
  • vos:///000-517
  • vos://[service]/path/my%20results
  • vos:///path/my%20results
  • vos:///my%20results

• Properties - A set of updated properties for the node
• Type specific data - Any additional type specific data that can be modified

Returns

A <node> element for the node, containing

• The full URI encoded identifier for the node. note
  • vos://[service]/000-517
  • vos://[service]/my%20results
  • vos://[service]/path/path/my%20results

• The node name as a plain string
  • 000-517
  • my results

• Type - The URI of the node type
  • ivo://org.astrogrid.vospace/types/data.node

• Properties - The set of name value properties for the node

Again, an XML friendly way to include any additional type specific data could be to use a generic <node> element, and then use xsi:type attribute to extend it as required.

Throws

• The service will throw a NodeNotFound exception if the target node does not exist.

• The service may throw an InternalFault exception if an operation fails.
• The service may throw a PermissionDenied exception if the user does not have permissions to perform the operation.

• The service will throw a LinkFound exception if the target path includes a link. note

Notes

• If the node is a link, then this will modify the properties for the link, not the node the link points to.

• Some properties may be read-only e.g. MD5 checksum.

• The <target> identifier in the request can be full a URI including the service identifier and node path.
  • vos://[service]/000-517
  • vos://[service]/path/my%20results

• The <target> identifier in the request can be a relative URI just containing the node path.
  • vos:///000-517
  • vos:///path/my%20results

• The <node> identifier in the response must be full a URI including the service identifier and node path.
  • vos://[service]/000-517
  • vos://[service]/path/my%20results

• Link nodes are not part of the V1.0 specification, they will be defined in a future version of the specification.
• LinkFound exceptions are defined in this version of the specification to enable future versions to extend the current interface, rather than require a completely new interface type.

Questions

-- DaveMorris - 18 May 2006