gtr at ast.cam.ac.uk
Tue Oct 27 02:55:10 PDT 2009
is there any strong reason why this should not work:
However, I would be happy with a "web resource" interface-type in
VoDataService - that would be useful.
On 27 Oct 2009, at 08:17, Ray Plante wrote:
> On Mon, 26 Oct 2009, Matthew Graham wrote:
>> I think that we can incorporate this into the current Availability
>> schema and please feel free to propose what to put in it.
> Please find schema and samples attached.
> A few comments:
> o In keeping with its predecessor
> (http://www.ivoa.net/xml/Availability/v0.4), I have used
> o While working on the capabilities example, I found that there is a
> problem with specifying the capability for the VOSI URL itself
> sect. 2.5). When specifying the interface, where the service
> URL is
> given, one must specify the type of Interface (via xsi:type);
> however, there is no Interface type currently defined that is a
> semantic match to the VOSI interface (a simple URL that resolves
> the underlying data).
> I think the best solution to this would be to propose to add a
> simple Interface type (say, called "WebResource") to the
> VODataService schema which is now in RFC. I will post a comment
> the RFC page to this effect.
> Finally, I will note that I've started using the Volute repository (http://code.google.com/p/volute/
> ) for files related to IVOA standards development. I have checked
> in the attached files under trunk/projects/grid/VOSI (http://code.google.com/p/volute/source/browse/#svn/
> I've also attached them to the GWS twiki page.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the grid