Indicates that a service has vospace capability This lists additional metadata about the space - might want to put stuff about data storage - or should that be in a special API for the Space? possible static metadata * authorization policy * max data transfer size dynamic metadata - e.g. available storage should be in control API. specific enumeration of the nodetypes supported by this VOSpace enumeration of other features supported by the VOspace - not specifically covered by the nodetypes - e.g. A property description. Note that this is very similar to the a unique identifier describes a view a reference to a published standard A list of parameters for the view. describes a VOSpace transfer protocol a reference to a published standard the URL scheme for the protocol A list of parameters for the view. The property identifier. The id is intended to be used as a fragment identifier to be added to the URL for the container of the property description to uniquely identify the property amongst the possible list of properties. enumeration of possible node types A type to allow dynamc listing of key values in the registry - this saves putting closed lists into schema in many cases. The intention is that the enumeration value would be of the form ivo://authority/resource#key where the fragment part refers to the particular key The basic enumeration key, which has an identifier and description only - This type can be extended if the key has other metadata associated with it. The intention is that the enumeration value would be of the form ivo://authority/resource#key where the fragment part refers to the particular key describes a the name of the column the unit associated with all values in the column the name of a unified content descriptor. See ....