Re: rel="shortlink" proposal for advertising short URLs in HTML/HTTP

Barry Leiba <barryleiba@computer.org> Wed, 22 April 2009 19:23 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4830F3A6D45 for <apps-discuss@core3.amsl.com>; Wed, 22 Apr 2009 12:23:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.176
X-Spam-Level:
X-Spam-Status: No, score=-2.176 tagged_above=-999 required=5 tests=[AWL=-0.199, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GuK8yfwsHLyR for <apps-discuss@core3.amsl.com>; Wed, 22 Apr 2009 12:23:53 -0700 (PDT)
Received: from mail-bw0-f163.google.com (mail-bw0-f163.google.com [209.85.218.163]) by core3.amsl.com (Postfix) with ESMTP id 517073A6C36 for <apps-discuss@ietf.org>; Wed, 22 Apr 2009 12:23:53 -0700 (PDT)
Received: by bwz7 with SMTP id 7so149207bwz.37 for <apps-discuss@ietf.org>; Wed, 22 Apr 2009 12:25:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=OybNWbwyD6GqEf8coVWernnAhpOqfZZK55No7g32sFc=; b=Qt9tXodwcp6cC6KqcodKQdFjRqZWtfJgNfhrquacdlIBMKeU7+xFu1jG1z9QMlHhuD cSeColIftNHbhpZuP2i+KAkLBpU9bhaoLTv0qkQBGP9EUyc3INBFaRvRtXiJNNWi6Cgp 5XohceGYXcy1MsidO5jxHfot+jbhTsJV8opVc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=WMAOoDkKX7IOuEoaYJYuOdVtLfIS9dloTwrK0wHc40vIOXSVUKZZgQNXOgbzRkv7lQ S4mxI7Nvpc4efXkFi59qjm3SW+jZ3LUfoMsfxiiZfOQSgb2f0PRY15g6E3boscOPx4bj CTAnvHp4lci0VzRpSvrmE0MrgFd1NQmRxEbas=
MIME-Version: 1.0
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.223.126.66 with SMTP id b2mr61384fas.3.1240428309950; Wed, 22 Apr 2009 12:25:09 -0700 (PDT)
In-Reply-To: <21606dcf0904162309k70d83661uae6810f48c7f8799@mail.gmail.com>
References: <21606dcf0904141153t3433975fh2bacf75f37353beb@mail.gmail.com> <49E521DB.8080403@cs.utk.edu> <21606dcf0904150508k210991b6gf8001c262d305a3f@mail.gmail.com> <49E5D4FE.1010003@cs.utk.edu> <21606dcf0904162309k70d83661uae6810f48c7f8799@mail.gmail.com>
Date: Wed, 22 Apr 2009 15:25:09 -0400
X-Google-Sender-Auth: 679e2073a7f92cdf
Message-ID: <6c9fcc2a0904221225o91a6966q76a6c23b1ac9d2f5@mail.gmail.com>
Subject: Re: rel="shortlink" proposal for advertising short URLs in HTML/HTTP
From: Barry Leiba <barryleiba@computer.org>
To: Sam Johnston <samj@samj.net>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@cs.utk.edu>, apps-discuss@ietf.org
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2009 19:23:54 -0000

Hm.

The problem, as I see it, with defining "persistence" is that one
wants different things in different contexts.  Consider these three
cases of things I might write:

1 ---------------------------------------------------
Note that any comments you post here are subject to my host's
copyright policy: [link to current copyright policy at time of
clicking].
------------------------------------------------------

2 ---------------------------------------------------
Note that the comment you just made is subject to my host's copyright
policy: [link to version of copyright policy in effect at the time of
writing].
------------------------------------------------------

3 ---------------------------------------------------
Check out the stupid typo in my host's copyright policy:
[link to immutable snapshot of copyright policy at the time of writing].
------------------------------------------------------

In case 1, I want a pointer that will always get me to the current
policy at the time you click the link.

In case 2, I want a pointer that will always get me to the policy
that's in effect when I wrote the text, regardless of subsequent
policy changes.

In case 3, I want a pointer that will always get me to the version
with the typo, even if they go and fix the typo without issuing a new
policy version.

With URL shorteners, you have no idea what you'll get, even when the
link isn't broken.  There's no guarantee that the content the link
points to has any relation whatever to what was there when the short
URL was made (if, say, the URL was set up to point to the current
front page of the newspaper).

With "short URLs" created by the content provider, you have a chance
of at least knowing what you're getting.  But what is it that you want
to get, and how do you specify it.  There are at least the three use
cases above, and perhaps others.

Barry