Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 466A9B303 for ; Sun, 22 Jan 2012 18:44:51 +0000 (UTC) Received: (qmail 86237 invoked by uid 500); 22 Jan 2012 18:44:50 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 86182 invoked by uid 500); 22 Jan 2012 18:44:50 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 86174 invoked by uid 99); 22 Jan 2012 18:44:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Jan 2012 18:44:49 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of nslater@tumbolia.org designates 209.85.214.52 as permitted sender) Received: from [209.85.214.52] (HELO mail-bk0-f52.google.com) (209.85.214.52) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Jan 2012 18:44:44 +0000 Received: by bkar19 with SMTP id r19so2094268bka.11 for ; Sun, 22 Jan 2012 10:44:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tumbolia.org; s=google; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:x-gm-message-state:content-type; bh=osFLE9NtPsvnNT7jHqiHHMl/EI0zSoyyOcZs57kkz/o=; b=heDULURKX+AMGZo040OOgk3TtkG5I987/r0AOcTzPPevSa0DSQGPSZC9JLLS+d8cQv SpQQqF7GV44Icjj9Owfo8DsM8Q/wP6AIk1PRTXMOBJVgvT+GoryZBx+XiKO0G+XhHqe3 SO5SSZOQhzXksGRjaSM4GhjYUIATEi6wETW5o= MIME-Version: 1.0 Received: by 10.205.136.202 with SMTP id il10mr1470502bkc.98.1327257863128; Sun, 22 Jan 2012 10:44:23 -0800 (PST) Received: by 10.205.25.202 with HTTP; Sun, 22 Jan 2012 10:44:23 -0800 (PST) X-Originating-IP: [178.250.115.206] In-Reply-To: <20111215021017.GB25751@atypical.net> References: <4EE72C0E.4080704@googlemail.com> <20111214225204.GC11299@atypical.net> <20111215021017.GB25751@atypical.net> Date: Sun, 22 Jan 2012 18:44:23 +0000 Message-ID: Subject: Re: Unique instance IDs? From: Noah Slater To: dev@couchdb.apache.org X-Gm-Message-State: ALoCoQm1swKEUqhnOqyEoZiv8u2waNlAZp7zDMoITNvWjhLZOh98t/RZocIxWNVTkoUSabPTPWWh Content-Type: multipart/alternative; boundary=000e0cdf8f6875059d04b7224df5 --000e0cdf8f6875059d04b7224df5 Content-Type: text/plain; charset=ISO-8859-1 Sorry to bump this old thread, but just going through my backlog. With regard to URLs, I think there is some confusion about the purpose of a URL here. If I write a a cool essay, say, and I stick that up at nslater.org/my-cool-essay, then I can link to it from other places on the web using that address. I might also want to put my cool essay on Dropbox, or post it to Tumblr, or send it in an email. Now my cool essay has lots of URLs. Each one of them perfectly valid. I don't have to go and edit the original copy at nslater.org/my-cool-essay, because I am making copies of it. My cool essay is completely unaware of the URLs that are being used to point to it. And it doesn't care that many URLs point to it. Yes, URLs can be used as identifiers. But when you do this, you tie the thing you're naming to the place you're hosting it. Sometimes that is useful, other times it will cripple you. There is nothing about URLs that requires you to do this. I would hazard a guess that 99% of URLs are de-coupled from the things they point to. WebArch is much more robust when the identity of the object is de-coupled from the URL. Look at Atom, the ID element is supposed to be a URL, but they recommend a non-dereferencable format, precisely to decouple posts from the location you happen to be hosting them this month. Hey, if we're gonna use URLs, maybe we want to go down the same route? http://en.wikipedia.org/wiki/Tag_URI At this point, I'm not sure what they buy us over UUIDs. Thoughts? Thanks, N --000e0cdf8f6875059d04b7224df5--