SCS spec bug

Markus Demleitner msdemlei at ari.uni-heidelberg.de
Thu Apr 28 08:04:00 CEST 2022


Hi Pat,

On Wed, Apr 27, 2022 at 01:53:47PM -0700, Patrick Dowler wrote:
> On Wed, 6 Apr 2022 at 02:31, Markus Demleitner <
> msdemlei at ari.uni-heidelberg.de> wrote:
> 
> > Since I'd expect we'll go along with SCS 1.03 for a bit longer, what
> > if we issued an erratum that fixed that example to
> >
> >   <?xml version="1.0"?>
> >   <VOTABLE xmlns="http://www.ivoa.net/xml/VOTable/v1.3">
> >     <DESCRIPTION>MAST Simple Cone Search Service</DESCRIPTION>
> >             <INFO ID="Error" name="Error" value="Error in input RA value:
> > as3f"/>
> >     <RESOURCE/>
> >   </VOTABLE>
> >
> > (the namespace is *the* VOTable version 1 namespace for now and
> > eternity).
> >
> 
> it seems a little odd for an erratum on a 2008 standard to change an
> example to refer to a 2013 (VOTable-1.3) standard

Yes -- but that's just a consequence of the original sin of this
business, that is, putting minor versions in the namespace URIs.  I
don't think there's a sane alternative to putting in the "current"
(and future) one.

> Both standards are now far back in time and I would suspect/hope the impact
> of the erratum would be negligible in practice.

Since it's just an example, there shouldn't be any impact at all,
except perhaps that SCS implementors (and doing SCS oneself is rather
realistic) don't base their code an invalid VOTables...

        -- Markus


More information about the dal mailing list