Some confusion in cone-search

[Tom McGlynn]

At the HEASARC we ran into this problem a few years ago.  We also were
using UCD 1+ in our ConeSearch VOTables.  The Cone search spec 
explicitly uses the 1.0 UCDs and there were a few services that had 
difficulty reading data from us.  We didn't want to go back to the V1.0 
UCDs since the 1+ versions are generally more expressive.  Our solution 
was simply to convert the three UCDs required by the cone search back to 
V1.0 as the last stage of processing.  We left all other UCDs unchanged, 
so that the resulting table used a mixture of V1.0 and V1+ UCDs.  This 
is legal (I think...).

While I'd certainly agree that it would be more elegant to be able to
use the V1+ UCDs consistently, it imposes some cost on clients to 
update.  I'm sure some software already accommodates both forms of UCDs 
but our experience indicates that there were at least a few clients that 
do (or at least did) not.


	Tom McGlynn



Guy Rixon wrote:
> Hi Pierre,
> 
> AFAIK, and having just reviewed the standards, you /have /to use UCD 1 
> to comply with cone search 1.03 and /must not /use UCD1+. You /may /use 
> UCD 1 rather than UCD 1+ in VOTable 1.1, but it's a shame to do so. 
> Anybody who parses VOTable 1.1 /must /be prepared to deal with UCD 1 as 
> well as UCD1+.
> 
> To the group: any chance that we could do a quick cone-search 1.1 that 
> allows both UCD1 and UCD1+? All cone-search 1.03 code would 
> automatically be valid in the new version. 
> 
> Cheers,
> Guy
> 
> On 2 Oct 2009, at 10:43, lesidaner-obs wrote:
> 
>> Hi
>>
>> We have implemented since some time a cone search for exoplanet 
>> catalog. The service have involved by time.
>> http://voparis-srv.obspm.fr/scs/scs_exoplanet.php?
>> our service respond with votable 1.1 as specified in the standards
>> "The service must respond with an XML document in the VOTable format, 
>> ... response must be compliant with VOTable schema, version 1.0 
>> [VOTable v1.0 
>> <http://www.ivoa.net/Documents/REC/DAL/ConeSearch-20080222.html#vot10>] 
>> or 1.1 [VOTable v1.1 
>> <http://www.ivoa.net/Documents/REC/DAL/ConeSearch-20080222.html#vot11>]."
>> so our UCD have the specified format 1.1."
>>
>> the compliance of the service appears to be wrong.
>> http://heasarc.gsfc.nasa.gov/vo/validation/vresults.pl?show=details&sid=182&runid=39628&switch=no
>> because ucd='ID_MAIN', ucd='ID_MAIN', ucd='POS_EQ_DEC_MAIN'.
>> but all these UCD are not compliant with VOTable 1.1 UCD.
>>
>> So what should be the issue
>>
>>
>> I want to thanks Michael Preciado for this precious job of vo service 
>> testing .
>>
>> Best regards
>> Pierre
>>
>> -- 
>> -------------------------------------------------------------------------
>>                          Pierre Le Sidaner
>>            Observatoire de Paris-Meudon-Nancay
>>
>> Service Informatique de l'Observatoire 01 45 07 76 34
>> 5, place Jules Janssen 92195 Meudon
>> Observatoire Virtuel 01 40 51 20 89
>> 61, avenue de l'Observatoire 75014 Paris
>>
>> mail:pierre.lesidaner at obspm.fr
>>
>> vo.obspm.fr
>>
>> --------------------------------------------------------------------------
>