<div dir="ltr"><div><div>I will have to find out of fixing examples is an errata item or if the doc can just be fixed.<br><br></div>Otherwise, just ignore REQUEST entirely. If the doc is vague, the intent in DALI and SIA-2.0 is that MAXREC support by a service is mandatory.<br><br></div>Pat<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 24 February 2016 at 02:06, Pierre Le Sidaner <span dir="ltr"><<a href="mailto:pierre.lesidaner@obspm.fr" target="_blank">pierre.lesidaner@obspm.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear James<span class=""><br>
<br>
On 02/23/2016 07:56 AM, James.Dempsey@csiro.au wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Pierre,<br>
<br>
It's great to see a validator for SIA2. Thank-you!<br>
<br>
I tried to run it myself but kept getting a " Fatal: Error while retrieving data. Is the remote service URL correct?" so I am assuming I am not putting my URL in correctly. It could also be caused by us not recognising (and thus rejecting) the REQUEST parameter. If the REQUEST parameter is the issue, could you show the error message coming back from the service please?<br>
</blockquote></span>
did you try with a ? at the end of the URL<span class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Speaking for the CASDA implementation:<br>
1. We added support for +Inf and -Inf ranges in our last release, around two weeks ago. A query with BAND=0.21 +Inf will work so long as the + is URL encoded.<br>
</blockquote></span>
nice<span class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
2. Was the schema location a request to implementers? We could add that to our response if so.<br>
</blockquote></span>
If we want to validate the VOTable it 's much more convenient to have the associated schema for it. And it's not unusual to see non valid VOTable.<br>
It's a request from me to the DAL group<span class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
4. We removed support for the REQUEST parameter as it was removed from the SIA2 spec in version WD-SIA-2.0-20140707. I see it is still in the examples though, which is confusing.<br>
</blockquote></span>
Ok Could one of the author of SIA modify the example that is wrong ?<br>
It's really important if you want to have valid services and be able to use them<span class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
5. It might be worth checking the obscore validator in taplint for what it enforces in Obscore. I know our SIA2 response is a reuse of the obscore TAP response, so we would prefer to see them have exactly the same requirements.<br>
</blockquote></span>
Ok I have check only the parameters that are explicitly describe in the SIA2 document<span class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
7. With MAXREC I would assume you need to test that you get no more results than requested and that if a query with a lower MAXREC gets less results then it should have an overflow entry. I've just noticed that we do limit the results returned but don’t provide an overflow entry. We'll fix that in our next release.<br>
</blockquote></span>
My question was more : should I put MAXREC as a "mandatory" parameter that the service must handle ?<br>
This is not clear for me regarding the SIA2 documentation<br>
<br>
<br>
until the problem of REQUEST parameter is solved, I put a test validator of SIA2 (choose Simple Image Access 2.0-test) same as the other one but with no REQUEST=query and no Inf in the parameters request<br>
it work wth your url <a href="http://casda.csiro.au/casda_vo_tools/sia2/query" rel="noreferrer" target="_blank">http://casda.csiro.au/casda_vo_tools/sia2/query</a>?<br>
as in the other one, I have put as mandatory Xtype and datatype in the VOTable response<br>
Let me know about all errors in the validation, I'll try to be reactive<br>
<br>
Regards<span class="HOEnZb"><font color="#888888"><br>
Pierre</font></span><div class="HOEnZb"><div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Cheers,<br>
James Dempsey<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:dal-bounces@ivoa.net" target="_blank">dal-bounces@ivoa.net</a> [mailto:<a href="mailto:dal-bounces@ivoa.net" target="_blank">dal-bounces@ivoa.net</a>] On Behalf Of Pierre Le Sidaner<br>
Sent: Tuesday, 23 February 2016 5:15 AM<br>
To: <a href="mailto:dal@ivoa.net" target="_blank">dal@ivoa.net</a><br>
Subject: validation of SIA 2<br>
<br>
Dear All<br>
<br>
I was working on the SIA2 validator on the last days I have a first version as a draft <a href="http://voparis-validator.obspm.fr" rel="noreferrer" target="_blank">http://voparis-validator.obspm.fr</a><br>
<br>
I try it with the 3 examples taken from RFC Page <a href="http://wiki.ivoa.net/twiki/bin/view/IVOA/Siav2RFC" rel="noreferrer" target="_blank">http://wiki.ivoa.net/twiki/bin/view/IVOA/Siav2RFC</a><br>
The SIA2 document is confusing because it refer to ObsCore without telling exactly what is mandatory.<br>
Moreover I have question about SIA V2 and the implementations<br>
<br>
* non of them support Inf as > or < of as it's proposed in the last documentation of sia2 like BAND=300 +Inf<br>
<br>
* could you please reference the schema in votable to validate it, something like<br>
xsi:schemaLocation="<a href="http://www.ivoa.net/xml/VOTable/v1.3" rel="noreferrer" target="_blank">http://www.ivoa.net/xml/VOTable/v1.3</a><br>
<a href="http://www.ivoa.net/xml/VOTable/VOTable-1.3.xsd" rel="noreferrer" target="_blank">http://www.ivoa.net/xml/VOTable/VOTable-1.3.xsd</a>"<br>
<br>
* for Utype example use an extension in the Utype name like<br>
obscore:Char.SpatialAxis.Coverage.Location.Coord.Position2D.Value2.C1<br>
but as the Utype come from Characterisation, is it relevant to add obscore, specially taking into account that Utype should be normalized.<br>
<br>
* for request in the query. In the example inside the document, REQUEST take the value query. Nothing in the documentation is related to DALI for that. <a href="http://dalservices.ivoa.net/sia_b?REQUEST=query&POS=CIRCLE" rel="noreferrer" target="_blank">http://dalservices.ivoa.net/sia_b?REQUEST=query&POS=CIRCLE</a><br>
180.475 -18.70 0.01&BAND= 0.0008 0.0009&TIME= 55708 55710&COLLECTION=ALMA. It should be more explicit in the documentation.<br>
And one ref implementation does not support this parameter/value.<br>
<br>
* what about datatype and xtype are they both mandatory in the votable output ? for s_region, s_fov ... in Obscore document there is both adql:REGION and AstroCoordArea does both are acceptable. VOTable schema should include a list of xtype if it's possible<br>
<br>
* don't you see any problem as s_resolution have datatype=float and xtype=adql:DOUBLE and sometime double in obscore doc.<br>
<br>
* what should I do with MAXREC, I mean what to test ?<br>
<br>
<br>
<br>
The 3 examples I took where<br>
<br>
<a href="http://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/sia/v2query" rel="noreferrer" target="_blank">http://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/sia/v2query</a>?<br>
it was my reference for test, if you try you must remove all the Inf<br>
<br>
casda implementation<br>
<a href="http://casda.csiro.au/casda_vo_tools/sia2/query" rel="noreferrer" target="_blank">http://casda.csiro.au/casda_vo_tools/sia2/query</a><br>
does not support Request=query,<br>
<br>
<br>
VAO implementation<br>
<a href="http://vaosa-vm1.aoc.nrao.edu/ivoa-dal/siapv2-vao/sync" rel="noreferrer" target="_blank">http://vaosa-vm1.aoc.nrao.edu/ivoa-dal/siapv2-vao/sync</a>?<br>
problem with DTD on votable<br>
<br>
<br>
Please give feedback about the validator, I am sure there is some bogus left.<br>
<br>
Regards<br>
Pierre<br>
<br>
--<br>
-------------------------------------------------------------------------<br>
Pierre Le Sidaner<br>
Observatoire de Paris<br>
<br>
Direction Informatique de l'Observatoire Observatoire Virtuel 01 40 51 20 82 61, avenue de l'Observatoire 75014 Paris<br>
<br>
mailto:<a href="mailto:pierre.lesidaner@obspm.fr" target="_blank">pierre.lesidaner@obspm.fr</a><br>
<a href="http://vo.obspm.fr" rel="noreferrer" target="_blank">http://vo.obspm.fr</a><br>
<br>
--------------------------------------------------------------------------<br>
<br>
</blockquote>
<br>
<br>
-- <br>
-------------------------------------------------------------------------<br>
Pierre Le Sidaner<br>
Observatoire de Paris<br>
<br>
Direction Informatique de l'Observatoire<br>
Observatoire Virtuel 01 40 51 20 82<br>
61, avenue de l'Observatoire 75014 Paris<br>
<br>
mailto:<a href="mailto:pierre.lesidaner@obspm.fr" target="_blank">pierre.lesidaner@obspm.fr</a><br>
<a href="http://vo.obspm.fr" rel="noreferrer" target="_blank">http://vo.obspm.fr</a><br>
<br>
--------------------------------------------------------------------------<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div>Patrick Dowler<br></div>Canadian Astronomy Data Centre<br></div>Victoria, BC, Canada<br></div></div>
</div>