- From: Schleiff, Marty <marty.schleiff@boeing.com>
- Date: Tue, 5 Sep 2006 10:20:41 -0700
- To: <www-tag@w3.org>
Hi David (& All), Your comment #10 is still missing the point of XRI persistence. The "xri://@example.org <mailto://@example.org?Subject=FW%3A%20Updates%20to%20URNs%2C%20Namespac es%20and%20Registries&In-Reply-To=%253CEBBD956B8A9002479B0C9CE9FE14A6C20 1143BAA%40tayexc19.americas.cpqcorp.net%253E&References=%253CEBBD956B8A9 002479B0C9CE9FE14A6C201143BAA%40tayexc19.americas.cpqcorp.net%253E> *agency*department/docs/govdoc.pdf" is not intended to to provide identity persistence and location independence. I think that example probably came from line #281 of the XRI introduction paper at http://www.oasis-open.org/committees/download.php/11857/xri-intro-V2.0-w d-04.pdf (which the XRI TC is hoping to rewrite/improve when they free up some bandwidth). Instead, the example XRI designed for persistence is on line #305: xri://@!9990!A58F!1C3D/!2495 The idea is that when "@example.org" gets registered, a meaningless number is also assigned as a sort of alias. If the "@example.org" name changes, the numeric version does not have to. I'm not saying that solves all the problems, or that it is easy to administer such capabilities. Instead, I'm just saying that section 5 (and David's comment #10) is displaying a misunderstanding of XRI. Marty.Schleiff
Received on Tuesday, 5 September 2006 17:21:00 UTC