<div dir="ltr">Hi Markus,<br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 16, 2015 at 12:42 PM, 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"><br>
(a) Shouldn't the RofR be at least mentioned here? While I agree<br>
that in everyday Registry operations, its impact is fairly moderate,<br>
mentioning here that the IVOA operates a special registry will, I<br>
think, make things much clearer. <br></blockquote><div><br></div><div>As far as the new EuroVO codebase is concerned, the RofR is used for the initial system bootstrapping (starting from a clean database) and thereafter it continues to be periodically checked as a supplemental mechanism of discovering new registries to harvest from. So yes, I feel it should be mentioned.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
(b) I always felt it was a bit of a pain that you had to discover<br>
support for seconds-granularity in OAI-PMH before using it. How<br>
would everyone feel about making it mandatory for VO publishing<br>
registries?<br></blockquote><div><br></div><div>I second that. The fewer options the better.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">(e) There's a recommendation to use the namespace URI as schema<br></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
location in the introduction to 3. What was the intent of that<br>
recommendation? Would anyone be cross if I removed it? </blockquote><div> </div><div>I second that as well. [schemaLocation] elements taint the XSD artifacts in a half-hearted (being mere hints) attempt to address a non-functional concern; the community should use other channels to communicate to application developers the reference location of its XSDs.</div><div><br></div><div>Cheers,</div><div>Menelaus.</div></div></div></div>