<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Ray,<div><br></div><div>is there any strong reason why this should not work:</div><div><br></div><div><span class="Apple-style-span" style="font-family: Times; "><capability standardID="ivo://org.astrogrid/std/VOSI/v0.3#availability"> <br> <interface xsi:type="vs:ParamHTTP"> <br> <accessURL use="full"><a href="http://casu.ast.cam.ac.uk/ag/iphas-dsa/IDR/vosi/availability">http://casu.ast.cam.ac.uk/ag/iphas-dsa/IDR/vosi/availability</a></accessURL><br> <queryType>GET</queryType><br> <resultType>application/xml</resultType><br> </interface><br></capability></span></div><div><font class="Apple-style-span" face="Times"><br></font></div><div>However, I would be happy with a "web resource" interface-type in VoDataService - that would be useful.</div><div><br></div><div>Regards,</div><div>Guy</div><div><font class="Apple-style-span" face="Times"><br></font><div><div>On 27 Oct 2009, at 08:17, Ray Plante wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Mon, 26 Oct 2009, Matthew Graham wrote:<br><blockquote type="cite">I think that we can incorporate this into the current Availability schema and please feel free to propose what to put in it.<br></blockquote><br>Please find schema and samples attached.<br><br>A few comments:<br><br> o In keeping with its predecessor<br> (<a href="http://www.ivoa.net/xml/Availability/v0.4">http://www.ivoa.net/xml/Availability/v0.4</a>), I have used<br> elementFormDefault="qualified".<br><br> o While working on the capabilities example, I found that there is a<br> problem with specifying the capability for the VOSI URL itself (see<br> sect. 2.5). When specifying the interface, where the service URL is<br> given, one must specify the type of Interface (via xsi:type);<br> however, there is no Interface type currently defined that is a good<br> semantic match to the VOSI interface (a simple URL that resolves to<br> the underlying data).<br><br> I think the best solution to this would be to propose to add a new,<br> simple Interface type (say, called "WebResource") to the<br> VODataService schema which is now in RFC. I will post a comment to<br> the RFC page to this effect.<br><br>Finally, I will note that I've started using the Volute repository (<a href="http://code.google.com/p/volute/">http://code.google.com/p/volute/</a>) for files related to IVOA standards development. I have checked in the attached files under trunk/projects/grid/VOSI (<a href="http://code.google.com/p/volute/source/browse/#svn/">http://code.google.com/p/volute/source/browse/#svn/</a>trunk/projects/grid/VOSI).<br>I've also attached them to the GWS twiki page.<br><br>cheers,<br>Ray<br></div></blockquote></div><br></div></body></html>