IETF Logo Mail Archive

Re: Atom Link Extensions Use Case

Philippe Rathé <prathe@gmail.com> Fri, 08 June 2012 14:34 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 6A2EC21F8932 for <ietfarch-atompub-archive@ietfa.amsl.com>; Fri, 8 Jun 2012 07:34:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.689
X-Spam-Level:
X-Spam-Status: No, score=-2.689 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DRUGS_MUSCLE=0.01, J_CHICKENPOX_45=0.6, MIME_8BIT_HEADER=0.3, 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 jnzyD1RgyLcQ for <ietfarch-atompub-archive@ietfa.amsl.com>; Fri, 8 Jun 2012 07:34:10 -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 4A73F21F892C for <atompub-archive@ietf.org>; Fri, 8 Jun 2012 07:34:10 -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 q58EQMWc001810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Jun 2012 07:26:22 -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 q58EQMID001809; Fri, 8 Jun 2012 07:26:22 -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-ey0-f171.google.com (mail-ey0-f171.google.com [209.85.215.171]) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q58EQKis001801 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for <atom-syntax@imc.org>; Fri, 8 Jun 2012 07:26:21 -0700 (MST) (envelope-from prathe@gmail.com)
Received: by eaaa12 with SMTP id a12so2185589eaa.16 for <atom-syntax@imc.org>; Fri, 08 Jun 2012 07:26:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=nLZeEsi1GvkoHD4vIhx/Oghu8W31LyfI9JsaK5jPzA0=; b=Zd6dw8feJPEjQFQDLDtQAxK/p3MxAtqYRCw73kTlHTaDqvpChlZnO/bGFFRudElE00 ruO+ndlzEHsGjPB7RZxFv4Kvi8Qea/QrDdiLuAS28d6xypqW37NZoUlghqBIPFO/cUJl o3daEtyKmJjZ0bVBlNyg1NZN4198d9rRvzgErqvVVKewLca+3ERaM3TboCrki2DGWTOw I0RBUW1tM/zEOlyL6UgvwTDDjaNqWtT67CXK4PSu2Mnvx9F4QkuoHkd8I4fpcMSh2vBX fbLuNEWB9sQrLKr3x3ZHQepRdlCPGYILSRUHpp5N+hz+sO0C+fwIO3AlFYiVh4XLgePK 5amQ==
MIME-Version: 1.0
Received: by 10.14.28.77 with SMTP id f53mr3698308eea.98.1339165579280; Fri, 08 Jun 2012 07:26:19 -0700 (PDT)
Received: by 10.14.205.3 with HTTP; Fri, 8 Jun 2012 07:26:19 -0700 (PDT)
In-Reply-To: <OF0E27AFCB.EC2E9FD8-ON85257A17.004BA423-85257A17.004BB9B2@us.ibm.com>
References: <CABzDd=4pwK3Ao=fGOL4K+vN3po9iwd2QBkmL8OwEw3ZmYvW=Xw@mail.gmail.com> <OF0E27AFCB.EC2E9FD8-ON85257A17.004BA423-85257A17.004BB9B2@us.ibm.com>
Date: Fri, 08 Jun 2012 10:26:19 -0400
Message-ID: <CAE-VBsB=mySEBY0THqTLnjF4bKOJqg=969xDV_BdM=DpPv3-_A@mail.gmail.com>
Subject: Re: Atom Link Extensions Use Case
From: Philippe Rathé <prathe@gmail.com>
To: Richard Salz <rsalz@us.ibm.com>
Cc: Ed Summers <ehs@pobox.com>, atom-syntax <atom-syntax@imc.org>, James Snell <jasnell@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hoffman.proper.com id q58EQLir001805
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>

Whatever the status of the I-D would change or not, I would use it
anyway as its current state. Unless that you find a standard that
provides exactly what you want.

In addition to that, it may be a good idea to add to your atom:entry a
link relation that advertise your potentially big file size with a
rel="alternate" link. So when crawler may handle it appropriately and
cache the result.

    <link rel="enclosure" type="application/x-bzip2" length="123456789"
            href="http://chroniclingamerica.loc.gov/data/dumps/ocr/part-00001.tar.bz2"/>

Well it is what I intend to do, I have similar needs.

-- Philippe

On Fri, Jun 8, 2012 at 9:47 AM, Richard Salz <rsalz@us.ibm.com> wrote:
> Way cool application!  Yes, it'd be good to refresh the I-D.  At a minimum,
> change the md5 examples to sha-256. :)
> --
> STSM, WebSphere Appliance Architect
> https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/

v2.23.0 | Report a Bug | By Email