[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
Re: Why have a multipart document address?
- To: xanadu@xxxxxxxxxx, udanax@xxxxxxxxxx
- Subject: Re: Why have a multipart document address?
- From: Jeff Rush <jeff@xxxxxxxxxx>
- Date: Sat, 12 Feb 2005 04:23:01 -0600
- In-reply-to: <126.96.36.199.2.20050211093503.104c8ec0@xxxxxxxxxxxxxxxxxxxx>
- Organization: Tau Productions Inc.
- References: <4fdbc18c14b8dad71125938f840f190a@xxxxxxxxxxxxx> <20050209104100.GH18048@xxxxxxxxxxxxxxxxxxxxxxx> <188.8.131.52.2.20050211093503.104c8ec0@xxxxxxxxxxxxxxxxxxxx>
On Fri, 2005-02-11 at 09:41 -0700, Art Pollard wrote:
> One issue as far as addresses are concerned is how do you pass around
> Has anybody given any thought to this issue ?
Thought, yes. In my conversations with several Xanadu people, including
Ted, I've never gotten a good answer to the 'URI' question, other than
that tumblers are NOT to be exposed to the general public, but that some
other, yet to be defined, layer above that.
Since Roger just now said that any facility to search using external
strings or numbers is not included, I'm at a bit of a loss now as to how
a human-readable URI would be translated by a front-end into a tumbler
address in a scalable way. The DNS system provides some of that "string
=> number" mapping for the web, but Xanadu strives to avoid reliance
It still seems there needs a be a basic way to assign brief, textual
"labels" to information. At one point the suggestion was that a file-
like name could be assigned to any document, by linking the document to
a textual title/filename string. That's fine, but I still need a way to
specify all/part of that title so as to search for the link. Once that
is done, I can grab one endpoint of that link, and follow it back to the
The question remains; what was Xanadu going to use for the human-
readable URI? What do I put on my business card, my letterhead, in TV
ads, on billboards that points back to my content?