Re: Atom Link Extensions Use Case

Ed Summers <ehs@pobox.com> Fri, 08 June 2012 17:22 UTC

Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@ietfa.amsl.com
Delivered-To: ietfarch-atompub-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AC0721F88D3 for <ietfarch-atompub-archive@ietfa.amsl.com>; Fri, 8 Jun 2012 10:22:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.82
X-Spam-Level:
X-Spam-Status: No, score=-2.82 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a34-HctmAYdA for <ietfarch-atompub-archive@ietfa.amsl.com>; Fri, 8 Jun 2012 10:22:12 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 71D9F21F87B8 for <atompub-archive@ietf.org>; Fri, 8 Jun 2012 10:22:12 -0700 (PDT)
Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q58HFhhS017854 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Jun 2012 10:15:43 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost) by hoffman.proper.com (8.14.5/8.13.5/Submit) id q58HFhMk017853; Fri, 8 Jun 2012 10:15:43 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from mail-ob0-f171.google.com (mail-ob0-f171.google.com [209.85.214.171]) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q58HFgjW017847 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for <atom-syntax@imc.org>; Fri, 8 Jun 2012 10:15:42 -0700 (MST) (envelope-from ed.summers@gmail.com)
Received: by obfk16 with SMTP id k16so6348823obf.16 for <atom-syntax@imc.org>; Fri, 08 Jun 2012 10:15:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=csUVfIsGY7VqniAS1PX55Ps5r53wRinPWerEKWHX6F4=; b=fwz3VB+EP+aJxw0xttLyd8Wafovd/RzFJZdAnBEivyeoXZq54C34fkTfCKyMEFgro3 06XeL3N/epMC2vTvJgLXiEUWXMm7NORHrfB5dSDd5UTZG03LqHjqje+WYAcmbkU0ViMx kL0KYJfvvHSzCKVT0mhvYtffMn4CzAmYPTLAzqDGkMdCoCKWEehQeaM1Iu+IaMwyzE+Q IagmJlByoj7UemZdaJGz0SZbm0/WxOlyFxfGh1nX56977FnllS5y8K6V3UuNqG5K7MIl wkp8O5SOaJPRok2aTni7kXGezdyib2jIJRZT/KzBX+g09/2u6pBaWME9aio04jNkMYGF CbCw==
MIME-Version: 1.0
Received: by 10.60.10.99 with SMTP id h3mr7845879oeb.72.1339175741717; Fri, 08 Jun 2012 10:15:41 -0700 (PDT)
Received: by 10.60.147.138 with HTTP; Fri, 8 Jun 2012 10:15:41 -0700 (PDT)
In-Reply-To: <CA+ZpN27_XfQnedj1v0BgS7G1BLR2Yq5ETkwROLXnCZbSEJLZ5A@mail.gmail.com>
References: <CABzDd=4pwK3Ao=fGOL4K+vN3po9iwd2QBkmL8OwEw3ZmYvW=Xw@mail.gmail.com> <CA+ZpN27_XfQnedj1v0BgS7G1BLR2Yq5ETkwROLXnCZbSEJLZ5A@mail.gmail.com>
Date: Fri, 08 Jun 2012 13:15:41 -0400
X-Google-Sender-Auth: QFgolJGG_4fgfbkscmHBT8OsjaE
Message-ID: <CABzDd=6551L3XoZUx29kyohHGo26LTrbMXSHp2WoUvuY3Nu7uA@mail.gmail.com>
Subject: Re: Atom Link Extensions Use Case
From: Ed Summers <ehs@pobox.com>
To: Tim Bray <twbray@google.com>
Cc: atom-syntax <atom-syntax@imc.org>, James Snell <jasnell@gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hoffman.proper.com id q58HFgjV017849
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

On Fri, Jun 8, 2012 at 10:41 AM, Tim Bray <twbray@google.com> wrote:
> Why not just drop an element into the <entry> in your own namespace?  This
> doesn’t feel like any kind of a link to me.
>
> <feed xmlns:loc="http://whatever.loc.gov">
>   ...
>   <entry>
>     ...
>     <loc:checksum>3c89ea593c01483fd091</loc:checksum

Since there can (potentially) be multiple <link> elements per <entry>
it would be difficult to know which resource the checksum applied to
no?

//Ed