<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Dear marco,</p>
<p>Very good for me</p>
<p>Thanks</p>
<p>François<br>
</p>
<br>
<div class="moz-cite-prefix">Le 18/04/2019 à 18:22, Molinaro, Marco
a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAFtRUxLC1Ab4EzwD-0orPa00DMxrfTEWCBqkOUR2M=zNavkZ+w@mail.gmail.com">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Dear <span class="" id=":bzg.1" tabindex="-1">François</span>,
dear all,</div>
<div>I tried to add your input in the rationale.</div>
<div>Have a look whether it is fine and reflects your thoughts.</div>
<div><br>
</div>
<div>I had also to modify the erratum content because I</div>
<div>found out the wrong UCD was repeated another 3</div>
<div>times in the text.</div>
<div><br>
</div>
<div>If nothing else shows up I'll push this to <span class=""
id=":bzg.2" tabindex="-1">TCG</span> review tomorrow.</div>
<div><br>
</div>
<div>Cheers</div>
<div> Marco</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr"><span class="" id=":bzg.3"
tabindex="-1">Il</span> <span class="" id=":bzg.4"
tabindex="-1">giorno</span> <span class="" id=":bzg.5"
tabindex="-1">gio</span> 18 <span class="" id=":bzg.6"
tabindex="-1">apr</span> 2019 <span class="" id=":bzg.7"
tabindex="-1">alle</span> ore 11:30 <span class=""
id=":bzg.8" tabindex="-1">François</span> <span class=""
id=":bzg.9" tabindex="-1">Bonnarel</span> <<span
class="" id=":bzg.10" tabindex="-1">francois</span>.<span
class="" id=":bzg.11" tabindex="-1">bonnarel</span>@<span
class="" id=":bzg.12" tabindex="-1">astro</span>.<span
class="" id=":bzg.13" tabindex="-1">unistra</span>.fr>
ha <span class="" id=":bzg.14" tabindex="-1">scritto</span>:<br>
</div>
<blockquote class="gmail_quote">
<div>
<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="gmail-m_7942573353658755996moz-cite-prefix">Le
17/04/2019 à 16:30, Molinaro, Marco a écrit :<br>
</div>
<blockquote type="cite">
<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"
target="_blank" moz-do-not-send="true">msdemlei@ari.uni-heidelberg.de</a>>
ha scritto:<br>
</div>
<blockquote class="gmail_quote">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>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>