Simple Cone Search 1.1 - (new) internal WD

[Walter Landry]

Markus Demleitner <msdemlei at ari.uni-heidelberg.de> wrote:
> As to BINARY2, we could simply say (and that's actually the behaviour
> of DaCHS):
> 
>   Services MUST NOT serve VOTables in BINARY2 serialisations unless
>   the client explicitly requests it using a
>   RESPONSEFORMAT=application/x-votable+xml;serialization=BINARY2
>   request parameter.

This would address my concerns with compatibility.  It would also be
different behavior from all of my other services (TAP, SIA2, SSA).  It
is a secret "Handle Nulls Correctly" button.  So I can not say that I
like this solution.

>> I would like to provide more than 3 UCD's.  They are kind of useful.
> 
> You are free to give UCD 1+ ucds in all fields not required for SCS
> -- that's common practice.  For instance (random SCS service picked):
> 
> http://vizier.u-strasbg.fr/viz-bin/votable/-A?-out.all&-source=J%2FApJ%2F798%2F54%2Ftable3&RA=0&DEC=10&SR=180

CDS, to their credit, actually embeds the old UCD's in comments.  So
while I admire CDS in figuring out a way to move into the present day
despite the spec, this means that clients have to be able to parse
both old and new UCD's.  It sounds like topcat is already doing this.

So at this point, I would vote for making a new major revision
including VOTable > 1.1 and UCD1+.  VOTable 1.3 has been a standard
for 4 years.  UCD1+ has been a standard for 10 years (longer than
SCS).  It is not too soon to update SCS.

Cheers,
Walter Landry