<div dir="ltr"><br><br><div class="gmail_quote">Manu Sporny wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Tab Atkins Jr. wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, Aug 28, 2008 at 4:42 PM, Kristof Zelechovski<br>
<<a href="mailto:giecrilj@stegny.2a.pl" target="_blank">giecrilj@stegny.2a.pl</a> <mailto:<a href="mailto:giecrilj@stegny.2a.pl" target="_blank">giecrilj@stegny.2a.pl</a>>> wrote:<br>
<br>
Ian's question was about what happens when it goes down forever, or gets<br>
taken over, intercepted, squatted, spoofed or redirected because of a<br>
malicious DNS. I should have known better how to ask it. The<br>
browser cache cannot handle these cases.<br>
<br>
Consider the question to be asked by me as well. A host of a popular<br>
format forgets to maintain its registration and gets squatted by a<br>
malicious person. They pick up another url to host their schema on, but<br>
legacy pages are still pointing to the old url and now may have poisoned<br>
semantics. Do we have a recourse?<br>
<br>
</blockquote>
<br>
The way we deal with this today is by using a Persistent URL (aka: URL<br>
re-direction service) such as <a href="http://purl.org" target="_blank">purl.org</a>[1] or <a href="http://xmlns.com" target="_blank">xmlns.com</a>[2]. We recommend<br>
that all authors use such a service for their vocabularies. This is how<br>
the Media, Audio, Video and Commerce RDF vocabularies are hosted.</blockquote></div></blockquote><div><br>Thanks, Manu. That does help address my concern. However:<br><br>On Fri, Aug 29, 2008 at 3:34 AM, James Graham <span dir="ltr"><<a href="mailto:jg307@cam.ac.uk">jg307@cam.ac.uk</a>></span> wrote: <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Given the problems with using DNS as your registry noted above and the fact that the recommended solution to this problem is to use a small number of registries built atop DNS that promise greater longevity than DNS registrations can ensure, it doesn't seem unreasonable to have a single permanent registry that provides (at least for HTML 5) a canonical prefix:url mapping. So instead of the use of cc:foo requiring a deceleration of cc elsewhere in the document, cc would be declared at, say, <a href="http://cc.rdfa.net" target="_blank">cc.rdfa.net</a> and would be a globally unique prefix from the point of view of the author. People not wanting to bother registering would just have to use full URLs everywhere. This would seem to provide the "follow your nose" principle you desire, remove several of the objections to URL-based namespaces, make authoring for the common case of well known vocabularies easier, and have only mildly different distributedness characteristics to the current recommended practice.</blockquote>
<div><br>I seem to always be a few hours behind in this thread... Rather than rewrite what Graham said, I'll just say that I echo his suggestion.<br><br>~TJ<br></div></div></div>