<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi all,</p>
<p>Thank you for preparing this erratum which I agree with of
course.</p>
<p>About 3-factor semantics and SODA ID parameter I will make the
following comment: <br>
</p>
<p>I thought 3-factor semantics was meanly thought for
interpretation of custom parameters in service descriptors.</p>
<p>In the case of a parameter part of the standard like SODA ID, the
definition of the parameter is unambiguous. <br>
</p>
<p>Maybe this could be reflected by the rationale ?<br>
</p>
<p>However a 3-factor description is still useful for homegeneity
and comparison to other parameters.</p>
<p>Best Regards<br>
</p>
François<br>
<div class="moz-cite-prefix">Le 17/04/2019 à 16:30, Molinaro, Marco
a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAFtRUxLo2e1ipKm=eaJYsLXVGHR-fiTbTW4weWzm4GPx6Qaejg@mail.gmail.com">
<div dir="ltr">
<div>Hi Markus,</div>
<div>thank you for reviewing and commenting.</div>
<div>I modified the erratum accordingly.</div>
<div><br>
</div>
<div>Thanks also to James for promptly</div>
<div>acting on the validator.</div>
<div><br>
</div>
<div>Cheers</div>
<div> Marco</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Il giorno mer 17 apr 2019
alle ore 09:34 Markus Demleitner <<a
href="mailto:msdemlei@ari.uni-heidelberg.de"
moz-do-not-send="true">msdemlei@ari.uni-heidelberg.de</a>>
ha scritto:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Hi DAL,<br>
<br>
On Tue, Apr 16, 2019 at 08:23:38PM +0200, Molinaro, Marco
wrote:<br>
[<a
href="https://wiki.ivoa.net/twiki/bin/view/IVOA/SODA-1_0-Err-1"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://wiki.ivoa.net/twiki/bin/view/IVOA/SODA-1_0-Err-1</a>]<br>
> @All: I don't think this erratum is complicated or
controversial,<br>
> so I suggest you take a look at it and comment at your
earlier<br>
> convenience so we can push it to TCG consideration
quickly.<br>
<br>
The Erratum content I fully agree with, and as a co-author
I'm<br>
somewhat embarrassed I missed this error; well, it was a
fairly late<br>
addition (rev. 3961). Still, I should've checked the
diffs. Watch<br>
me write in dust and ashes.<br>
<br>
I have, through both dust and ashes, a couple of more or
less formal<br>
nits to pick:<br>
<br>
(a) the part with "thus achieving" in Erratum content is
part of the<br>
rationale and should, I feel, go there. I'd like the
erratum a lot<br>
better if everything starting "thus achieving" went from
"Erratum<br>
Content" and instead we'd append to "Rationale":<br>
<br>
To remedy the situation, we propose here to use<br>
"<a href="http://meta.id" rel="noreferrer" target="_blank"
moz-do-not-send="true">meta.id</a>;meta.dataset" instead.
This achieves:<br>
<br>
* typo amendment<br>
* reference to a dataset rather than an organization<br>
* using a UCD referring to an identifier rather than a
resource locator<br>
* keeping the identifier opaque as required by the
specification<br>
<br>
(b) The impact assessment is overly optimistic. This
*would* be a<br>
major thing if anyone did 3-factor semantics on ID. Which I
think is<br>
not the case -- since there's not been much evolution on
Datalink<br>
processing services before SODA, the SODA parameter names
have, as it<br>
were, been reserved from the start, and so going by names
exclusively<br>
is a fairly safe thing to do for them.<br>
<br>
Also, the argument that no SODA services have been
registered is a<br>
weak one -- in general, there is no reason to register them,
as<br>
nobody has yet offered a scenario that would make SODA
discovery<br>
desirable; I certainly don't register any of mine. Hence,
we can't<br>
know how many SODA services are in place (I alone have ~10,
and other<br>
DaCHS operators run at least another five).<br>
<br>
I'd hence propose to strike the text starting with "On the
client<br>
side" and instead write:<br>
<br>
On the client side, changing a UCD will break clients
using 3-factor<br>
semantics to find the parameter to pass the identifier in.<br>
However, as ID is defined by both Datalink and SODA and no<br>
competing definition ever existed, no known client
actually uses<br>
3-factor semantics to locate the ID parameter and instead
just uses<br>
the hard-coded name "ID". Hence, to our knowledge the UCD
changed<br>
here is ignored by clients, and no breakage will occur. <br>
<br>
The safety of changing this UCD is also plausible in view
of the<br>
fact that several data centers (e.g., GAVO's Heidelberg
data<br>
center; example here:<br>
<a
href="http://dc.zah.uni-heidelberg.de/feros/q/sdl/dlmeta?ID=ivo%3A%2F%2Forg.gavo.dc%2F%7E%3Fferos%2Fdata%2Ff02891.fits"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://dc.zah.uni-heidelberg.de/feros/q/sdl/dlmeta?ID=ivo%3A%2F%2Forg.gavo.dc%2F%7E%3Fferos%2Fdata%2Ff02891.fits</a>)<br>
have been successfully operating SODA services that used<br>
<a href="http://meta.id" rel="noreferrer" target="_blank"
moz-do-not-send="true">meta.id</a>;meta.main as a UCD for
ID without interoperabilty issues.<br>
<br>
This latter observation perhaps can also count as an urgent
call for<br>
validators...<br>
<br>
-- Markus<br>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>