<div dir="ltr">Hi Markus,<div><br></div><div>What you propose sounds fine to me. Thank you for seeing this through.</div><div><br></div><div>-- Alberto</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 8, 2015 at 5:04 AM, Markus Demleitner <span dir="ltr"><<a href="mailto:msdemlei@ari.uni-heidelberg.de" target="_blank">msdemlei@ari.uni-heidelberg.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Alberto,<br>
<br>
Thanks for being persistent here, because...<br>
<span class=""><br>
On Wed, Oct 07, 2015 at 11:24:49AM -0400, Accomazzi, Alberto wrote:<br>
> "resolution," which in my mind is the simple process of mapping an<br>
> identifier to one or more actionable addresses (typically http URLs). This<br>
> process can be enhanced to provide useful identifier metadata by the<br>
> resolver using things such as content negotiation (see e.g.<br>
> <a href="http://www.crosscite.org/cn/" rel="noreferrer" target="_blank">http://www.crosscite.org/cn/</a>)<br>
><br>
> If we start calling all or most VO services "resolvers" of pubDIDs then the<br>
> meaning of what a resolver does gets diluted to the point that one would<br>
> not know what it means. To me, SSA, Obscore, etc. are services that accept<br>
<br>
</span>...you are of course completely right. So, here's my next offer<br>
(volute rev. 3094); this, now, actually does mention the global<br>
PubDID resolver, but a subtle hint that such a shameless plug has no<br>
place in a recommendation will suffice to make me drop it.<br>
<span class=""><br>
Note that by this specification publishers have no obligation to<br>
ensure continued access to datasets identified with PubDIDs. They<br>
</span> are not by themselves persistent identifiers with guarantees on<br>
<span class=""> resolvability. Their main function is to provide globally unique<br>
identifiers for use in, e.g., federating responses from different<br>
services.<br>
<br>
</span> Publishers are, however, encouraged to declare at least one<br>
capability of a protocol dealing with PubDIDs[2] in the resource<br>
record referenced by the Registry part of a PubDID (i.e., the URI in<br>
front of the first question mark). In that way, clients can attempt<br>
to retrieve data based on stand-alone PubDIDs by querying the<br>
Registry for the "embedding" resource and seeing if it supports any<br>
protocol they implement.<br>
<br>
The definition of a proper resolver or resolution strategy is beyond<br>
the scope of this standard. Although services prototyping such<br>
funtionality have been written[3], we maintain additional efforts are<br>
required outside of Registry to build a reliable infrastructure on<br>
top of PubDIDs.<br>
<br>
with the footnotes<br>
<br>
[2] At the time of this writing, Datalink, Obscore, and SSA are<br>
IVOA recommended protocols allowing queries involving PubDIDs. SIA<br>
<span class=""> (Tody & Plante 2009) will, according to current proposed<br>
</span> recommendations, have an analogous facility in version 2.0.<br>
<br>
[3] e.g., GAVO's global PubDID resolver at <a href="http://dc.g-vo.org/glopidir" rel="noreferrer" target="_blank">http://dc.g-vo.org/glopidir</a>.<br>
<br>
This now *almost* has a forward reference to future standards, but<br>
I feel it's not really promising anything, and I hope it maintains<br>
acceptable levels of terminological rigour.<br>
<br>
Opinions? Further suggestions for improvement?<br>
<br>
Thanks,<br>
<br>
Markus<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Dr. Alberto Accomazzi<br>Program Manager<br>NASA Astrophysics Data System - <a href="http://ads.harvard.edu" target="_blank">http://ads.harvard.edu</a><br>Harvard-Smithsonian Center for Astrophysics - <a href="http://www.cfa.harvard.edu" target="_blank">http://www.cfa.harvard.edu</a><br>60 Garden St, MS 83, Cambridge, MA 02138, USA</div>
</div>