Lifting 1.1 limit in SCS?
Wu, Xiuqin
xiuqin at ipac.caltech.edu
Fri Nov 19 21:05:31 CET 2021
I want to express explicitly that I support this erratum for SCS.
Xiuqin
---------
Xiuqin Wu (she/her) | Task Lead | Caltech/IPAC
NASA/IPAC Extragalactic Database
On Nov 19, 2021, at 3:35 AM, Molinaro, Marco <marco.molinaro at inaf.it<mailto:marco.molinaro at inaf.it>> wrote:
Dear Apps & DAL,
an erratum has been proposed for
Simple Cone Search v1.03.
You can find it here:
https://wiki.ivoa.net/twiki/bin/view/IVOA/SCS-1_03-Err-2
and below there's the DAL thread that started
this update.
Apps WG is added to this thread to gather
comments and feedback on the client impact
assessment for the erratum itself.
Thanks in advance and
Cheers
Marco
PS - Mark/Markus: check whether I acted
on the text as expected.
Il giorno ven 19 nov 2021 alle ore 10:58 Markus Demleitner <msdemlei at ari.uni-heidelberg.de<mailto:msdemlei at ari.uni-heidelberg.de>> ha scritto:
Hi Mark,
On Thu, Nov 18, 2021 at 02:34:51PM +0000, Mark Taylor wrote:
> On Thu, 18 Nov 2021, Markus Demleitner wrote:
> > On Wed, Nov 17, 2021 at 01:19:59PM +0100, Molinaro, Marco wrote:
> > > I took the liberty to draft the erratum:
> > >
> > > https://wiki.ivoa.net/twiki/bin/view/IVOA/SCS-1_03-Err-2
> >
> > Thanks for making that move. I've expanded the erratum a bit, and
> > I'd now be happy with it.
>
> I prefer Marco's original
>
> "The XML content of the response must be compliant with the
> VOTable Recommendation."
Fair enough -- unless someone else speaks out for the lengthy
> "Simple Cone Search services MUST return VOTable version 1 documents.
> This means that clients will have to handle the namespace URIs
> http://www.ivoa.net/xml/VOTable/v1.1,
> http://www.ivoa.net/xml/VOTable/v1.2, and
> http://www.ivoa.net/xml/VOTable/v1.3, where the last namespace
> will be used for all future VOTable 1 versions.
> For forward compatibility clients should ignore unknown elements
> and attributes in these documents as per the IVOA schema versioning
> policies."
totally feel free to revert -- though I can't say I like either of
"XML content" and "compliant with" very much, which is what made be
try a re-formulation in the first place; perhaps we can go for "SCS
responses are returned in the VOTable format"?)
> I'm dubious also about Markus's mention of BINARY serialization,
> only to point out that it's not relevant here:
>
> "We note that, in particular, the main interoperability problem even
> in the days of SCS 1.03, lack of support for BINARY-serialised tables,
> is orthogonal to the problem addressed here, as BINARY serialisation
> was already part of VOTable 1.1."
>
> I would therefore prefer to delete the middle paragraph of the r2
> impact assessment.
Yeah, that might be hedging too much, and I don't think it's been a
problem in the last 10 years or so any more. So, yes, chuck it out.
-- Markus
--
Marco Molinaro
INAF - Istituto Nazionale di AstroFisica
Osservatorio Astronomico di Trieste
email marco.molinaro at inaf.it<mailto:marco.molinaro at inaf.it>
tel. [+39] 333 33 20 564 / 040 3199 152
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/apps/attachments/20211119/85487a91/attachment-0001.html>
More information about the apps
mailing list