VOResource v0.10

[Roy Williams]

Thank you for your prompt response Ray. But can I clarify a couple of
things?

Suppose I have a Cone Search that I want to register. It takes parameters
RA, Dec, SR (as all cone searches do), and a couple of my own personal
parameters (apple, banana).

Question 1: So I publish this to some registry through forms. The forms ask
me if there are other parameters and I describe these (apple has the
description, dtaatype, ucd, etc). The end result is a piece of XML that
describes MY special cone search with MY special parameters. Something like
what you write below. Is that right?

Question 2: Why are the standard parameters (RA, Dec, SR) mixed up with my
personal paramters (apple, banana)? Has there been a thought of inheritance?
What would seem much better would be to say "I have a standard Cone Search
pus these extra parameters", rather than repeateing the standard parameters
every time.

Question 3: Is there an intention to define which parameters are necessary?
Suppose apple and banana are optional parameters? Suppose there must be at
least one of these? Does the registry record need to know this?

Thanks
Roy



--------
California Institute of Technology
roy at caltech.edu
626 395 3670
----- Original Message ----- 
From: "Ray Plante" <rplante at ncsa.uiuc.edu>
To: <registry at ivoa.net>
Sent: Tuesday, June 22, 2004 10:14 AM
Subject: Re: VOResource v0.10


> Hi Roy,
>
> thanks for the question!
>
> On Tue, 22 Jun 2004, Roy Williams wrote:
> > > I would particularly like extra eyes on...
> > >      o  Cone Search
> >
> > Is the following legal under your cone search schema:
> > http://blah.com/cone?RA=190&Dec=20&SR=1&apple=6&banana=3
>
> (Is the "RA=190" significant to your question?)
>
> Note to others listening in: the Cone Search schema does not cover the
> syntax of the input query itself, but rather describing the instance of
> the service as a resource in the registry.
>
> The availability of these arguments can be encoded with the Cone Search
> schema within the "interface" element, e.g.:
>
>   <vr:interface xsi:type="vs:ParamHTTP" qtype="GET"
>              xmlns="http://www.ivoa.net/xml/VODataService/v0.5">
>      <vr:accessURL use="base">http://blah.com/cone?</vr:accessURL>
>      <resultType>text/xml+votable</resultType>
>
>      <!-- These are the supported input parameters -->
>      <param>
>        <name>RA</name>
>        <description>The right ascension of the search cone
center</description>
>        <dataType>float</dataType>
>        <unit>degrees</unit>
>        <ucd>POS_EQ_RA_MAIN</ucd>
>      </param>
>      <param>
>        <name>Dec</name>
>        <description>The declination of the search cone
center</description>
>        <dataType>float</dataType>
>        <unit>degrees</unit>
>        <ucd>POS_EQ_DEC_MAIN</ucd>
>      </param>
>      <param>
>        <name>apple</name>
>        <description>The number of apples detected with this
source</description>
>        <dataType>int</dataType>
>      </param>
>      <param>
>        <name>Dec</name>
>        <description>The number of bananas detected with this
source</description>
>        <dataType>int</dataType>
>      </param>
>
> Does this answer your question?
>
> cheers,
> Ray
>
>