<?xml version="1.0" encoding="UTF-8"?>
<!-- list of standard enumeration types for VOSpace expressed as resource entries

 -->
<ri:VOResources xmlns:ri="http://www.ivoa.org/xml/ResourceSet/v1.0"
	xmlns:vr="http://www.ivoa.net/xml/VOResource/v1.0"
	xmlns:vsp="http://www.ivoa.net/schema/VOSpaceResource/v1.0rc7"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:vstd="http://www.ivoa.net/xml/VOStandard/v0.2beta1"
   
	xsi:schemaLocation="http://www.ivoa.org/xml/ResourceSet/v1.0 ResourceSet-v1.0.xsd">
	<!-- std properties -->
	<ri:Resource status="active" updated="2005-09-09T12:28:16"
		xsi:type="vstd:ResourceEnumList" created="2005-09-09T12:28:16">
		<title>VOSpace Standard Properties</title>
		<shortName>VOSpaceProps</shortName>
		<identifier>ivo://net.ivoa.vospace/properties</identifier>
		<curation>
			<publisher>IVOA</publisher>
			<creator>
				<name>IVOA</name>
				<logo>
					http://www.ivoa.net/icons/ivoa_logo_small.jpg
				</logo>
			</creator>
			<date role="representative">2006-07-17</date>
			<version>1.0</version>
			<contact>
				<name>IVOA Grid Webservices WG</name>
				<email>vospace@ivoa.net</email>
			</contact>
		</curation>
		<content>
			<subject>VOSpace</subject>
			<description>
				A standard VOSpace property definition
			</description>
			<referenceURL>http://www.ivo.net/vospace</referenceURL>
			<type>Other</type>
		</content>
		<!-- now the actual property metadata -->
		<key name="size" xsi:type="vsp:VOSpaceProperty">
			<description>The size of the data item</description>
			<unit>bytes</unit>
		</key>
		<key name="owner" xsi:type="vsp:VOSpaceProperty">
			<description>The owner of the data</description>
		</key>
      <key name="modificationdate" xsi:type="vsp:VOSpaceProperty">
         <description>The last modification date of the data</description>
      </key>
      <key name="creationdate" xsi:type="vsp:VOSpaceProperty">
         <description>The last modification date of the data</description>
      </key>
     <key name="md5sum" xsi:type="vsp:VOSpaceProperty">
         <description>md5 hash for the data</description>
      </key>
      
 
	</ri:Resource>
	<!-- std protocols -->
	<ri:Resource status="active" updated="2005-09-09T12:28:16"
		xsi:type="vstd:ResourceEnumList" created="2005-09-09T12:28:16">
		<title>VOSpace standard protocols</title>
		<shortName>VOSpace Protocol</shortName>
		<identifier>ivo://net.ivoa.vospace/protocols</identifier>
		<curation>
			<publisher>IVOA</publisher>
			<creator>
				<name>IVOA</name>
				<logo>
					http://www.ivoa.net/icons/ivoa_logo_small.jpg
				</logo>
			</creator>
			<date role="representative">2006-07-17</date>
			<version>1.0</version>
			<contact>
				<name>IVOA Grid Webservices WG</name>
				<email>vospace@ivoa.net</email>
			</contact>
		</curation>
		<content>
			<subject>VOSpace</subject>
			<description>
				standard VOSpace protocol definitions
			</description>
			<referenceURL>http://www.ivo.net/vospace</referenceURL>
			<type>Other</type>
		</content>
		<!-- now the actual protocol metadata -->
        <!-- needs to be completed -->
		<key name="http-client" xsi:type="vsp:VOSpaceProtocol">
			<description>http get according to latest protocol document</description>
			<standardUrl>
				http://www.w3.org/Protocols/rfc2616/rfc2616.html
			</standardUrl>
			<urlScheme>http:</urlScheme>
		</key>
		<key name="http-server" xsi:type="vsp:VOSpaceProtocol">
			<description>http put</description>
			<standardUrl>
				http://www.w3.org/Protocols/rfc2616/rfc2616.html
			</standardUrl>
			<urlScheme>http:</urlScheme>
		</key>
      <key name="https-client" xsi:type="vsp:VOSpaceProtocol">
         <description>http get with TLS expecting client authentication via X509 certificates</description>
         <standardUrl>
            http://www.w3.org/Protocols/rfc2616/rfc2616.html
         </standardUrl>
         <urlScheme>http:</urlScheme>
      </key>
      <key name="https-server" xsi:type="vsp:VOSpaceProtocol">
         <description>http put with TLS expecting client authentication X509 certificates</description>
         <standardUrl>
            http://www.w3.org/Protocols/rfc2616/rfc2616.html
         </standardUrl>
         <urlScheme>http:</urlScheme>
      </key>
      
	   <key name="file" xsi:type="vsp:VOSpaceProtocol">
			<description>direct access to the filesystem</description>
			<urlScheme>file:</urlScheme>
	  </key>

      <key name="dime" xsi:type="vsp:VOSpaceProtocol">
         <description>obtain the data as the first DIME attachment of the current VOSpace SOAP control message Details of the DIME specification can be found at here [http://msdn.microsoft.com/library/en-us/dnglobspec/html/draft-nielsen-dime-02.txt] </description>
         <standardUrl>http://msdn.microsoft.com/library/en-us/dnglobspec/html/draft-nielsen-dime-02.txt</standardUrl>
      </key>
      <key name="mtom" xsi:type="vsp:VOSpaceProtocol">
         <description>
         Obtain the data as the first MTOM attachment of the current VOSpace SOAP control message.
         Details of the MTOM specification can be found here [http://www.w3.org/TR/soap12-mtom/]
         </description>
         <standardUrl>http://www.w3.org/TR/soap12-mtom/</standardUrl>
      </key>
      <key name="gridftp-server" xsi:type="vsp:VOSpaceProtocol">
          <description>
            A grid enabled version of ftp from www.globus.org
          </description>
          <standardUrl>http://www-fp.mcs.anl.gov/dsl/GridFTP-Protocol-RFC-Draft.pdf</standardUrl>
      </key>
      <key name="gridftp-client" xsi:type="vsp:VOSpaceProtocol">
          <description>
            A grid enabled version of ftp from www.globus.org
          </description>
          <standardUrl>http://www-fp.mcs.anl.gov/dsl/GridFTP-Protocol-RFC-Draft.pdf</standardUrl>
      </key>
      <key name="ssh-client" xsi:type="vsp:VOSpaceProtocol" >
          <description>
             capable of an scp to a remote location.
          </description>
      </key>
      <key name="ssh-server" xsi:type="vsp:VOSpaceProtocol" >
          <description>
             capable of receiving scp from a remote location.
          </description>
      </key>
	</ri:Resource>
	<!-- views -->
	<ri:Resource status="active" updated="2005-09-09T12:28:16"
		xsi:type="vstd:ResourceEnumList" created="2005-09-09T12:28:16">
		<title>VOSpace standard views</title>
		<shortName>VOSpace Views</shortName>
		<identifier>ivo://net.ivoa.vospace/views</identifier>
		<curation>
			<publisher>IVOA</publisher>
			<creator>
				<name>IVOA</name>
				<logo>
					http://www.ivoa.net/icons/ivoa_logo_small.jpg
				</logo>
			</creator>
			<date role="representative">2006-07-17</date>
			<version>1.0</version>
			<contact>
				<name>IVOA Grid Webservices WG</name>
				<email>vospace@ivoa.net</email>
			</contact>
		</curation>
		<content>
			<subject>VOSpace</subject>
			<description>
				standard VOSpace protocol definitions
			</description>
			<referenceURL>http://www.ivo.net/vospace</referenceURL>
			<type>Other</type>
		</content>
		<!-- now the actual view metadata -->
		<key name="identity" xsi:type="vsp:VOSpaceProtocol">
			<description>the data in the original format</description>
		</key>
		<key name="votable" xsi:type="vsp:VOSpaceProtocol">
			<description>votable representation</description>
			<standardUrl>
				http://www.ivoa.net/Documents/REC/VOTable/VOTable-20040811.html
			</standardUrl>
		</key>
	</ri:Resource>

	<!-- access control policies -->
	<ri:Resource status="active" updated="2005-09-09T12:28:16"
		xsi:type="vstd:ResourceEnumList" created="2005-09-09T12:28:16">
		<title>VOSpace standard access control policies</title>
		<shortName>VOSpace Policies</shortName>
		<identifier>ivo://net.ivoa.vospace/policies</identifier>
		<curation>
			<publisher>IVOA</publisher>
			<creator>
				<name>IVOA</name>
				<logo>
					http://www.ivoa.net/icons/ivoa_logo_small.jpg
				</logo>
			</creator>
			<date role="representative">2006-07-17</date>
			<version>1.0</version>
			<contact>
				<name>IVOA Grid Webservices WG</name>
				<email>vospace@ivoa.net</email>
			</contact>
		</curation>
		<content>
			<subject>VOSpace</subject>
			<description>
				standard VOSpace access policy definitions
			</description>
			<referenceURL>http://www.ivo.net/vospace</referenceURL>
			<type>Other</type>
		</content>
		<!-- now the actual view metadata -->
		<key name="authenticated-private">
			<description>
				the owner of the resource has full control, and world
				has no ability to read
			</description>
		</key>
		<key name="authenticated-readonly">
			<description>
				all resources are available read-only to world after authentication, but
				there is no ability to write
			</description>
		</key>
		<key name="public-readwrite">
			<description></description>
		</key>
      <key name="open-readonly">
         <description>readonly with no authentication or authorization controls</description>
      </key>
      <key name="custom">
         <description>custom authorization</description>
      </key>

	</ri:Resource>
	<!-- a vospace service -->
	<ri:Resource status="active" updated="2005-09-09T12:28:16" xsi:type="vr:Service"
		created="2005-09-09T12:28:16">
		<title>An example VOSpace definition</title>
		<shortName>VOSpace Protocol</shortName>
		<identifier>ivo://org.eso/vospace</identifier>
		<curation>
			<publisher>ESO</publisher>
			<creator>
				<name>ESO</name>
				<logo>http://www.eso.org/images/eso-logo.gif</logo>
			</creator>
			<date role="representative">2006-07-17</date>
			<version>1.0</version>
			<contact>
				<name>Paul Harrison</name>
				<email>pharriso@eso.org</email>
			</contact>
		</curation>
		<content>
			<subject>VOSpace</subject>
			<description>A set of servers in a VOSpace</description>
			<referenceURL>http://www.ivo.net/vospace</referenceURL>
			<type>Other</type>
		</content>

		<capability xsi:type="vsp:VOSpaceCapability"
			standardID="ivo://net.ivoa/standard/VOSpace">
			<description></description>
			<interface xsi:type="vr:WebService" role="std"
				version="1.0">
				<accessURL>http://host1:8080/vospace</accessURL>
				<!-- there are issues of how to register multiple servers in the space - 
					it could be done with the multiple interfaces or multiple accessURLs within an interface-->
				<accessURL>http://host3:8080/vospace</accessURL>
			</interface>
			<interface xsi:type="vr:WebService" role="std"
				version="1.1">
				<accessURL>http://host2:8080/vospace</accessURL>
			</interface>
			<!-- problem here with versioning - different versions would have different capabilities?
				also the assumption is that all the servers within a space have identical metadata for below 
				- need to examine this assumption-->
			<accessPolicy>
				ivo://net.ivoa.vospace/policies#public-readonly
			</accessPolicy>
			<protocols>
				<accepts>
					<uri>
						ivo://net.ivoa.vospace/protocols#http-1.1-get
					</uri>
				</accepts>
				<provides>
					<uri>
						ivo://net.ivoa.vospace/protocols#http-1.1-get
					</uri>
				</provides>
			</protocols>
			<views>
				<accepts>
					<uri>ivo://net.ivoa.vospace/views#any</uri>
				</accepts>
				<provides>
					<uri>ivo://net.ivoa.vospace/views#any</uri>
				</provides>
			</views>
			<nodeTypes>DataNode</nodeTypes>
		</capability>
	</ri:Resource>
</ri:VOResources>