but this is deprecated in atom 1.0 I > think. From owner-atom-syntax@mail.imc.org Tue Apr 04 07:03:29 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FQjJU-0006eE-2X for atompub-archive@lists.ietf.org; Tue, 04 Apr 2006 07:03:08 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FQjHN-00082a-1Y for atompub-archive@lists.ietf.org; Tue, 04 Apr 2006 07:00:58 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k34AppIi053364; Tue, 4 Apr 2006 03:51:51 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k34App2h053363; Tue, 4 Apr 2006 03:51:51 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from isolokki.dnainternet.net (isolokki.dnainternet.net [212.149.75.39]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k34ApocM053356 for ; Tue, 4 Apr 2006 03:51:50 -0700 (MST) (envelope-from hsivonen@iki.fi) Received: from [217.140.228.131] (217-140-228-131.adsl-net.finnetcom.net [217.140.228.131]) by isolokki.dnainternet.net (Postfix) with ESMTP id C2BAEC816; Tue, 4 Apr 2006 13:42:13 +0300 (EEST) In-Reply-To: <200604041236.52128.cedric@over-blog.com> References: <200604041236.52128.cedric@over-blog.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <93786809-6971-45E5-A37F-74F6F7257892@iki.fi> Cc: Atom Syntax Content-Transfer-Encoding: 7bit From: Henri Sivonen Subject: Re: Error in example ? Date: Tue, 4 Apr 2006 13:51:39 +0300 To: cedric@over-blog.com X-Mailer: Apple Mail (2.746.2) Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 On Apr 4, 2006, at 13:36, cedric wrote: > In 3.1.1.3 XHTML of > http://www.atomenabled.org/developers/syndication/atom-format- > spec.php#atom.documents > > There is example using

John Panzer
System Architect
http://abstractioneer.org
From owner-atom-syntax@mail.imc.org Wed Apr 26 22:32:28 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FYwIu-0006hR-Ly for atompub-archive@lists.ietf.org; Wed, 26 Apr 2006 22:32:28 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYwIu-0000mY-KX for atompub-archive@lists.ietf.org; Wed, 26 Apr 2006 22:32:28 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FYw9g-0006L7-GP for atompub-archive@lists.ietf.org; Wed, 26 Apr 2006 22:22:58 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3R2888c009972; Wed, 26 Apr 2006 19:08:08 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k3R2888p009971; Wed, 26 Apr 2006 19:08:08 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.238]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3R2876W009964 for ; Wed, 26 Apr 2006 19:08:08 -0700 (MST) (envelope-from jasnell@gmail.com) Received: by wproxy.gmail.com with SMTP id i34so1573061wra for ; Wed, 26 Apr 2006 19:08:07 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=OP1IGhQPGSXIN5nNA1aMWieBNfkisTucbspFirRp0Ek+/dsq5ILhEpN58wd45qQE0ivPN9P0twQkubAED5srGb9VXmvXwE6iZg17ve0PLIlONmXesdApaUGSzCrQZo2CP3NSgUTo6lmVjy8uswTFW+EMcTVXqD4QhDt6C1pUDy0= Received: by 10.54.94.14 with SMTP id r14mr7842670wrb; Wed, 26 Apr 2006 19:08:07 -0700 (PDT) Received: from ?192.168.1.104? ( [67.181.222.86]) by mx.gmail.com with ESMTP id g7sm123272wra.2006.04.26.19.08.06; Wed, 26 Apr 2006 19:08:06 -0700 (PDT) Message-ID: <44502780.1030303@gmail.com> Date: Wed, 26 Apr 2006 19:08:00 -0700 From: James M Snell User-Agent: Thunderbird 1.5.0.2 (X11/20060420) MIME-Version: 1.0 CC: atom-syntax Subject: Re: Tools that make use of previous/next/first/last links? References: <4450200D.1000809@aol.net> In-Reply-To: <4450200D.1000809@aol.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.2 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Just ran it through my parser impl. The paging works great. However, I nearly cried when I saw aj:commentCount ;-) .... - James John Panzer wrote: > We just deployed support for link@rel="previous" et al. for AOL > Journals. If anyone has a client that makes use of these links, please > let me know, I'd love to see if there are any interoperability problems. > > Example Atom feed: > http://journals.aol.com/panzerjohn/abstractioneer/atom.xml > > Thanks, > -- > Abstractioneer John Panzer > System Architect > http://abstractioneer.org From owner-atom-syntax@mail.imc.org Wed Apr 26 22:47:47 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FYwXj-0004du-No for atompub-archive@lists.ietf.org; Wed, 26 Apr 2006 22:47:47 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYwXi-0001ej-BC for atompub-archive@lists.ietf.org; Wed, 26 Apr 2006 22:47:47 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3R2X8X1011573; Wed, 26 Apr 2006 19:33:08 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k3R2X8LE011572; Wed, 26 Apr 2006 19:33:08 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from mcom.com (c3po.aoltw.net [64.236.137.25]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3R2X6Oo011562 for ; Wed, 26 Apr 2006 19:33:07 -0700 (MST) (envelope-from jpanzer@aol.net) Received: from [10.169.186.29] (sera-10-169-186-29.nscp.aoltw.net [10.169.186.29]) by mcom.com (8.10.0/8.10.0) with ESMTP id k3R2Wxj03845; Wed, 26 Apr 2006 19:32:59 -0700 (PDT) Message-ID: <44502D5B.90102@aol.net> Date: Wed, 26 Apr 2006 19:32:59 -0700 From: John Panzer User-Agent: Mozilla Thunderbird 1.0RC1 (Windows/20041201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: James M Snell CC: atom-syntax Subject: Re: Tools that make use of previous/next/first/last links? References: <4450200D.1000809@aol.net> <44502780.1030303@gmail.com> In-Reply-To: <44502780.1030303@gmail.com> Content-Type: multipart/alternative; boundary="------------030200010607070602080209" Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.1 (/) X-Scan-Signature: 386e0819b1192672467565a524848168 This is a multi-part message in MIME format. --------------030200010607070602080209 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Yeah, I know. Just to put it in perspective, that field is much older than Atom 1.0. :) Looking forward to linking together our entry and subsidiary comment threads using threading extensions (and moving the comment count to the comment feed)... James M Snell wrote: >Just ran it through my parser impl. The paging works great. However, I >nearly cried when I saw aj:commentCount ;-) .... > >- James > >John Panzer wrote: > > >>We just deployed support for link@rel="previous" et al. for AOL >>Journals. If anyone has a client that makes use of these links, please >>let me know, I'd love to see if there are any interoperability problems. >> >>Example Atom feed: >>http://journals.aol.com/panzerjohn/abstractioneer/atom.xml >> >>Thanks, >>-- >>Abstractioneer John Panzer >>System Architect >>http://abstractioneer.org >> >> > > > --------------030200010607070602080209 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Yeah, I know. Just to put it in perspective, that field is much older than Atom 1.0. :)

Looking forward to linking together our entry and subsidiary comment threads using threading extensions (and moving the comment count to the comment feed)...

James M Snell wrote:

Just ran it through my parser impl.  The paging works great.  However, I
nearly cried when I saw aj:commentCount ;-) ....

- James

John Panzer wrote:

We just deployed support for link@rel="previous" et al. for AOL
Journals.  If anyone has a client that makes use of these links, please
let me know, I'd love to see if there are any interoperability problems.

Example Atom feed:
http://journals.aol.com/panzerjohn/abstractioneer/atom.xml

Thanks,
-- 
Abstractioneer <http://feeds.feedburner.com/aol/SzHO>John Panzer
System Architect
http://abstractioneer.org

--------------030200010607070602080209-- From owner-atom-syntax@mail.imc.org Wed Apr 26 23:17:24 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FYx0O-0005mC-B1 for atompub-archive@lists.ietf.org; Wed, 26 Apr 2006 23:17:24 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYx0L-0003tT-Uz for atompub-archive@lists.ietf.org; Wed, 26 Apr 2006 23:17:24 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3R34Mw4012822; Wed, 26 Apr 2006 20:04:22 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k3R34M9Z012821; Wed, 26 Apr 2006 20:04:22 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.236]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3R34J55012812 for ; Wed, 26 Apr 2006 20:04:20 -0700 (MST) (envelope-from jasnell@gmail.com) Received: by wproxy.gmail.com with SMTP id i14so1595720wra for ; Wed, 26 Apr 2006 20:04:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=de6uN6HefurLBixIcriA/wBKpQtru+eADadwgCRtWa/GDd67P0V7a/aXLxCJ8Q/PrpHIIj/S4doqERx+Xwm9BJyYXabK8r8wz0JY1hnv2AoXG+VSx+wLQhz6xkZ/ytpL0rPEg5RDIiPDdVuBriciS9118VWrVakXnYFrqk78qQY= Received: by 10.65.72.11 with SMTP id z11mr2174878qbk; Wed, 26 Apr 2006 20:04:19 -0700 (PDT) Received: from ?192.168.1.104? ( [67.181.222.86]) by mx.gmail.com with ESMTP id q14sm57548qbq.2006.04.26.20.04.18; Wed, 26 Apr 2006 20:04:19 -0700 (PDT) Message-ID: <445034AC.2020206@gmail.com> Date: Wed, 26 Apr 2006 20:04:12 -0700 From: James M Snell User-Agent: Thunderbird 1.5.0.2 (X11/20060420) MIME-Version: 1.0 To: atom-syntax Subject: Re: Tools that make use of previous/next/first/last links? References: <4450200D.1000809@aol.net> <44502780.1030303@gmail.com> <44502D5B.90102@aol.net> In-Reply-To: <44502D5B.90102@aol.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b ;-) I'm just messing with you. The feed looks good. Excellent to see folks using the paging links. I also note that you're using temporal ordering of the pages where previous == older. Good stuff. - James John Panzer wrote: > Yeah, I know. Just to put it in perspective, that field is much older > than Atom 1.0. :) > > Looking forward to linking together our entry and subsidiary comment > threads using threading extensions (and moving the comment count to the > comment feed)... > > James M Snell wrote: >> Just ran it through my parser impl. The paging works great. However, I >> nearly cried when I saw aj:commentCount ;-) .... >> >> - James >> >> John Panzer wrote: >> >>> We just deployed support for link@rel="previous" et al. for AOL >>> Journals. If anyone has a client that makes use of these links, please >>> let me know, I'd love to see if there are any interoperability problems. >>> >>> Example Atom feed: >>> http://journals.aol.com/panzerjohn/abstractioneer/atom.xml >>> >>> Thanks, >>> -- >>> Abstractioneer John Panzer >>> System Architect >>> http://abstractioneer.org >>> >> >> > From owner-atom-syntax@mail.imc.org Wed Apr 26 23:49:14 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FYxVC-00029j-Tf for atompub-archive@lists.ietf.org; Wed, 26 Apr 2006 23:49:14 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYxV7-0005fy-Dx for atompub-archive@lists.ietf.org; Wed, 26 Apr 2006 23:49:14 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3R3ZfTT014102; Wed, 26 Apr 2006 20:35:41 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k3R3ZfLU014101; Wed, 26 Apr 2006 20:35:41 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from hotmail.com (bay109-dav10.bay109.hotmail.com [64.4.19.82]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3R3ZfYt014095 for ; Wed, 26 Apr 2006 20:35:41 -0700 (MST) (envelope-from j4_james@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 26 Apr 2006 20:35:40 -0700 Message-ID: Received: from 81.179.77.76 by BAY109-DAV10.phx.gbl with DAV; Thu, 27 Apr 2006 03:35:37 +0000 X-Originating-IP: [81.179.77.76] X-Originating-Email: [j4_james@hotmail.com] X-Sender: j4_james@hotmail.com From: "James Holderness" To: "atom-syntax" References: <4450200D.1000809@aol.net> Subject: Re: Tools that make use of previous/next/first/last links? Date: Thu, 27 Apr 2006 04:35:35 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-OriginalArrivalTime: 27 Apr 2006 03:35:40.0445 (UTC) FILETIME=[A7EF74D0:01C669AB] Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 3.0 (+++) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f We added support for next/prev/previous links in version 0.3.0 of Snarfer [1]. We don't use the reconstruction algorithm suggested in the Feed History draft, but your example feed seems to work ok for an initial retrieval. There may be problems with subsequent updates, though, depending on how you handle items falling out the bottom of the main feed. Regards James [1] http://www.snarfware.com/ John Panzer wrote: > We just deployed support for link@rel="previous" et al. for > AOL Journals. If anyone has a client that makes use of these > links, please let me know, I'd love to see if there are any > interoperability problems. From owner-atom-syntax@mail.imc.org Thu Apr 27 06:19:29 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FZ3ar-0007h9-2x for atompub-archive@lists.ietf.org; Thu, 27 Apr 2006 06:19:29 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZ3aq-0002RY-56 for atompub-archive@lists.ietf.org; Thu, 27 Apr 2006 06:19:29 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3RA097A029330; Thu, 27 Apr 2006 03:00:09 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k3RA09uE029329; Thu, 27 Apr 2006 03:00:09 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from mtaout03-winn.ispmail.ntl.com (mta09-winn.ispmail.ntl.com [81.103.221.49]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3RA08Kk029321 for ; Thu, 27 Apr 2006 03:00:08 -0700 (MST) (envelope-from djpowell@djpowell.net) Received: from aamtaout03-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout03-winn.ispmail.ntl.com with ESMTP id <20060427100002.KGOO27969.mtaout03-winn.ispmail.ntl.com@aamtaout03-winn.ispmail.ntl.com>; Thu, 27 Apr 2006 11:00:02 +0100 Received: from cpc1-stok1-0-0-cust263.bagu.cable.ntl.com ([86.4.229.8]) by aamtaout03-winn.ispmail.ntl.com with ESMTP id <20060427100002.ICVS16286.aamtaout03-winn.ispmail.ntl.com@cpc1-stok1-0-0-cust263.bagu.cable.ntl.com>; Thu, 27 Apr 2006 11:00:02 +0100 Date: Thu, 27 Apr 2006 10:59:58 +0100 From: David Powell X-Mailer: The Bat! (v3.72.11 (Beta)) Professional X-Priority: 3 (Normal) Message-ID: <62815737.20060427105958@djpowell.net> To: James M Snell CC: atom-syntax Subject: Re: Feed Thread Draft Updated In-Reply-To: <44497E86.1060601@gmail.com> References: <443C0F90.3070809@gmail.com> <1864175160.20060412230210@djpowell.net> <20060412235958.GP30787@klangraum> <443DB0DE.3080208@gmail.com> <20060413044341.GQ30787@klangraum> <443DF5A8.6000004@gmail.com> <20060421231757.GN21391@klangraum> <44497E86.1060601@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.1 (/) X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024 Saturday, April 22, 2006, 1:53:26 AM, James M Snell wrote: > So this is what I've got: > count = element thr:count { > attribute xml:base { atomUri }?, > attribute ref { atomUri }?, > attribute updated { date-time }?, > ( nonNegativeInteger ) > } I think that is ok. Aristotle's suggestion is ok, in that it saves a bit of typing in the common case where there is only one link - but in the case where there is more than one link, a combined count seems pretty useless: if there are multiple comment links, then either the consumer can cope with them and process both the links and counts, or the consumer can't cope with them and can only process the combined count - but the count alone without any links to reach the comments isn't very useful, so why bother with it - consumers that can cope with multiple comments links will be able to manage addition of the counts if necessary. A variation would be to go with your proposal, but to say that ref is optional if there is only one comments link, but would that be fragile? People would have to remember to fix things up if they added extra comment links - but is that going to be a common occurrence? And implementations that add comment links will presumably be aware of the semantics of comment links, and will therefore know about the need to add missing refs? Anyway, I think that any of these options is better than the current situation. > The value of ref is the href of a replies link appearing in the > entry/feed/source. Where that gets nasty, of course, is when the href > is relative and xml:base is being used to set the Base URI. xml:base always gets nasty, but I don't see it as being a big problem in this case. > The updated spec would have an appendix that would explain that previous > versions of the extension defined the attributes and that some > implementations have been deployed that use the attributes. The spec > will indicate that those attributes are deprecated in favor of the > thr:count element but that feed consumers have the discretion of whether > or not to support them. Maintaining compatibility with an expired Internet Draft? I don't really support that. Is it really needed: Stage 1: Implementation X has no support for FTE Stage 2: Implementation X supports obsolete draft of FTE Stage 3: Implementation X supports final version of FTE Nobody is going to consider the obsolete form to be invalid. All that would happen if consumers don't support it, is that they won't see the thread counts. This isn't a big deal, as before the implementations had implemented support for FTE consumers wouldn't see the thread counts anyway. Eventually those implementations that support the obsolete form will be updated, and consumers will be able to process the thread counts. (I think the moral of this story is to, in future, not to specify IANA-namespaced link rel until a specification has been finalised. During development there are bound to be changes, and IANA links don't allow versioning, or DO-NOT-DEPLOY banners in the URI (like the one we put in Atom draft namespace). Although, to be honest, I'm amazed if there is any real reluctance to make breaking changes to an Internet Draft.) > Does this work? > - James -- Dave From owner-atom-syntax@mail.imc.org Thu Apr 27 12:37:41 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FZ9Ur-0004nr-Py for atompub-archive@lists.ietf.org; Thu, 27 Apr 2006 12:37:41 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZ9Up-0001Gp-8I for atompub-archive@lists.ietf.org; Thu, 27 Apr 2006 12:37:41 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3RGOPIr048385; Thu, 27 Apr 2006 09:24:25 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k3RGOPXD048384; Thu, 27 Apr 2006 09:24:25 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by balder-227.proper.com (8.13.5/8.13.5) with SMTP id k3RGON7h048375 for ; Thu, 27 Apr 2006 09:24:24 -0700 (MST) (envelope-from pagaltzis@gmx.de) Received: (qmail invoked by alias); 27 Apr 2006 16:24:17 -0000 Received: from xdsl-213-196-249-201.netcologne.de (EHLO klangraum) [213.196.249.201] by mail.gmx.net (mp039) with SMTP; 27 Apr 2006 18:24:17 +0200 X-Authenticated: #163624 Date: Thu, 27 Apr 2006 18:24:17 +0200 From: "A. Pagaltzis" To: atom-syntax Subject: Re: Feed Thread Draft Updated Message-ID: <20060427162417.GD2690@klangraum> Mail-Followup-To: atom-syntax References: <443C0F90.3070809@gmail.com> <1864175160.20060412230210@djpowell.net> <20060412235958.GP30787@klangraum> <443DB0DE.3080208@gmail.com> <20060413044341.GQ30787@klangraum> <443DF5A8.6000004@gmail.com> <20060421231757.GN21391@klangraum> <44497E86.1060601@gmail.com> <62815737.20060427105958@djpowell.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <62815737.20060427105958@djpowell.net> User-Agent: Mutt/1.4.2.1i X-Y-GMX-Trusted: 0 Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by balder-227.proper.com id k3RGOPIr048385 X-Spam-Score: 0.1 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 * David Powell [2006-04-27 12:10]: > Aristotle's suggestion is ok, in that it saves a bit of typing > in the common case where there is only one link - but in the > case where there is more than one link, a combined count seems > pretty useless: if there are multiple comment links, then > either the consumer can cope with them and process both the > links and counts, or the consumer can't cope with them and can > only process the combined count - but the count alone without > any links to reach the comments isn't very useful, so why > bother with it - consumers that can cope with multiple comments > links will be able to manage addition of the counts if > necessary. I don=E2=80=99t think it=E2=80=99s that useless, actually. One case I can= think of is where several comment feeds exist, where some comments are duplicated in multiple feeds, but others are not. In that case, the sum of local counts will be greater than the global count. I expect that in practice, if a global count is present, it will turn out to be the most precise count available, whereas there=E2=80=99s nothing you could infer from a sum of local counts. (That does not change the fact that all counts remain advisory, of course.) Regards, --=20 Aristotle Pagaltzis // From owner-atom-syntax@mail.imc.org Fri Apr 28 02:39:09 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FZMdB-0007YB-By for atompub-archive@lists.ietf.org; Fri, 28 Apr 2006 02:39:09 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZMd9-0002ud-V9 for atompub-archive@lists.ietf.org; Fri, 28 Apr 2006 02:39:09 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3S6FdjE084680; Thu, 27 Apr 2006 23:15:39 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k3S6FdQ1084679; Thu, 27 Apr 2006 23:15:39 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from mcom.com (r2d2.aoltw.net [64.236.137.26]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3S6Fcam084673 for ; Thu, 27 Apr 2006 23:15:38 -0700 (MST) (envelope-from jpanzer@aol.net) Received: from [10.169.186.29] (sera-10-169-186-29.nscp.aoltw.net [10.169.186.29]) by mcom.com (8.10.0/8.10.0) with ESMTP id k3S6FNJ13313; Thu, 27 Apr 2006 23:15:24 -0700 (PDT) Message-ID: <4451B2FC.9060500@aol.net> Date: Thu, 27 Apr 2006 23:15:24 -0700 From: John Panzer User-Agent: Mozilla Thunderbird 1.0RC1 (Windows/20041201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "A. Pagaltzis" CC: atom-syntax@imc.org Subject: Re: Is there a way to specify that a feed requires a login? References: <43FCED98.40507@totic.org> <20060223042006.GJ13715@klangraum> In-Reply-To: <20060223042006.GJ13715@klangraum> Content-Type: multipart/alternative; boundary="------------040604030409050501020001" Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.2 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 This is a multi-part message in MIME format. --------------040604030409050501020001 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by balder-227.proper.com id k3S6FdjE084680 A. Pagaltzis wrote: >Hi Aleks, > >* Aleks Totic [2006-02-23 00:15]: > =20 > >>For authenticated sites, if your login cookies are not there, >>you get back a login page. In Thunderbird there is no way to >>fill in the login page, as all browsing requests are redirected >>to Firefox. >> =20 >> > >I think the standard answer to that would be =E2=80=9Cuse HTTP >authentication instead of cookies.=E2=80=9D Many aggregators support >subscribing to HTTP-authenticated feeds. (I don=E2=80=99t know if most >do, but I assume so.) > I'm actually looking for a recent survey on this topic. The latest I've=20 found is here: http://www.megginson.com/blogs/quoderat/archives/2005/07/29/password-prot= ected-rss-challenge/ though that's only for HTTP Basic without TLS; I wish they'd tested with=20 TLS as well. Oh well. Anybody? We're planning on supporting HTTP Basic over TLS for retrieval of=20 private feeds as well as editing via the APP. John --------------040604030409050501020001 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by balder-227.proper.com id k3S6FdjE084680 A. Pagaltzis wrote:

Hi Aleks,

* Aleks Totic <a@totic.org> [2006-02-23 00:15]:

For authenticated sites, if your login cookies are not=
 there,
you get back a login page. In Thunderbird there is no way to
fill in the login page, as all browsing requests are redirected
to Firefox.


I think the standard answer to that would be =E2=80=9Cuse HTTP
authentication instead of cookies.=E2=80=9D Many aggregators support
subscribing to HTTP-authenticated feeds. (I don=E2=80=99t know if most
do, but I assume so.)

I'm actually looking for a recent survey on this topic.=C2=A0 The latest I've found is here:

http://w= ww.megginson.com/blogs/quoderat/archives/2005/07/29/password-protected-rs= s-challenge/

though that's only for HTTP Basic without TLS; I wish they'd tested with TLS as well.=C2=A0 Oh well.=C2=A0 Anybody?

We're planning on supporting HTTP Basic over TLS for retrieval of private feeds as well as editing via the APP.

John
--------------040604030409050501020001-- From owner-atom-syntax@mail.imc.org Fri Apr 28 04:41:39 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FZOXj-0004i0-76 for atompub-archive@lists.ietf.org; Fri, 28 Apr 2006 04:41:39 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZOXh-0002RX-Rn for atompub-archive@lists.ietf.org; Fri, 28 Apr 2006 04:41:39 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3S8MGKX089229; Fri, 28 Apr 2006 01:22:16 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k3S8MGCs089228; Fri, 28 Apr 2006 01:22:16 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from satakieli.dnainternet.net (satakieli.dnainternet.net [212.149.75.40]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3S8MFkM089186 for ; Fri, 28 Apr 2006 01:22:15 -0700 (MST) (envelope-from hsivonen@iki.fi) Received: from [217.140.228.86] (217-140-228-86.adsl-net.finnetcom.net [217.140.228.86]) by satakieli.dnainternet.net (Postfix) with ESMTP id 96461C8F8; Fri, 28 Apr 2006 11:22:07 +0300 (EEST) In-Reply-To: <441FC787.1070002@gmx.de> References: <87slqrytn9.fsf@nwalsh.com> <43F215F5.5030409@fourthought.com> <1546562261.20060314234203@djpowell.net> <6.0.0.20.2.20060315121947.078123c0@localhost> <20060315090130.GB300@nic.fr> <877j6uxuo2.fsf@nwalsh.com> <6.0.0.20.2.20060317172945.0902cba0@localhost> <6.0.0.20.2.20060319161753.09c944e0@localhost> <441D9005.1070505@metalab.unc.edu> <6.0.0.20.2.20060321152820.09efdad0@localhost> <441FC787.1070002@gmx.de> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <525B6C8C-1F79-4F25-9054-ED603ABED6CC@iki.fi> Cc: Atom Syntax Content-Transfer-Encoding: 7bit From: Henri Sivonen Subject: Re: Datatype for IRIs in RELAX NG Date: Fri, 28 Apr 2006 11:22:05 +0300 To: rng-users@yahoogroups.com X-Mailer: Apple Mail (2.749.3) Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 On Mar 21, 2006, at 11:29, Julian Reschke wrote: > maybe it's time that *some* specification adds new datatypes that > do *exactly* what RFC3986 and RFC3987 ask for :-) I have a draft spec at http://hsivonen.iki.fi/html5-datatypes/ A snapshot of the reference implementation (which currently lacks the 'language' datatype) is available for testing as part of my validation service: http://hsivonen.iki.fi/validator/ The reference implementation just wraps the IRI library from Jena (pulled from CVS; the new version does not ship in a Jena release, yet). Disclaimer: The datatype library has undergone *very* little testing. -- Henri Sivonen hsivonen@iki.fi http://hsivonen.iki.fi/ From owner-atom-syntax@mail.imc.org Sun Apr 30 14:01:10 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FaGEI-0001AR-NC for atompub-archive@lists.ietf.org; Sun, 30 Apr 2006 14:01:10 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FaGEH-00052S-Ai for atompub-archive@lists.ietf.org; Sun, 30 Apr 2006 14:01:10 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3UHh6co055421; Sun, 30 Apr 2006 10:43:06 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k3UHh6bi055420; Sun, 30 Apr 2006 10:43:06 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from mxout-03.mxes.net (mxout-03.mxes.net [205.237.194.34]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3UHh51H055414 for ; Sun, 30 Apr 2006 10:43:05 -0700 (MST) (envelope-from mnot@mnot.net) Received: from [192.168.1.5] (adsl-67-119-69-243.dsl.sntc01.pacbell.net [67.119.69.243]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 53EF4519B5; Sun, 30 Apr 2006 13:43:04 -0400 (EDT) In-Reply-To: References: <4450200D.1000809@aol.net> Mime-Version: 1.0 (Apple Message framework v749.3) X-Priority: 3 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <95133C9F-3CC3-4403-8B95-8C2B02232311@mnot.net> Cc: "atom-syntax" Content-Transfer-Encoding: 7bit X-Image-Url: http://www.mnot.net/personal/MarkNottingham.jpg From: Mark Nottingham Subject: Re: Tools that make use of previous/next/first/last links? Date: Sun, 30 Apr 2006 10:43:07 -0700 To: James Holderness X-Mailer: Apple Mail (2.749.3) Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Did you find that algorithm wrong, too hard to understand/implement, or did you just do a different take on it? Does the approach that you took end up having the same result? Any suggestions on how to better document it appreciated. Cheers, On 2006/04/26, at 8:35 PM, James Holderness wrote: > > We added support for next/prev/previous links in version 0.3.0 of > Snarfer [1]. We don't use the reconstruction algorithm suggested in > the Feed History draft, but your example feed seems to work ok for > an initial retrieval. There may be problems with subsequent > updates, though, depending on how you handle items falling out the > bottom of the main feed. > > Regards > James > > [1] http://www.snarfware.com/ > > John Panzer wrote: >> We just deployed support for link@rel="previous" et al. for >> AOL Journals. If anyone has a client that makes use of these >> links, please let me know, I'd love to see if there are any >> interoperability problems. > > -- Mark Nottingham http://www.mnot.net/ From owner-atom-syntax@mail.imc.org Sun Apr 30 14:01:10 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FaGEI-0001AS-NC for atompub-archive@lists.ietf.org; Sun, 30 Apr 2006 14:01:10 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FaGEH-00052R-Ai for atompub-archive@lists.ietf.org; Sun, 30 Apr 2006 14:01:10 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3UHfKJh055356; Sun, 30 Apr 2006 10:41:20 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k3UHfK2A055355; Sun, 30 Apr 2006 10:41:20 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from mxout-03.mxes.net (mxout-03.mxes.net [205.237.194.34]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3UHfIe8055349 for ; Sun, 30 Apr 2006 10:41:19 -0700 (MST) (envelope-from mnot@mnot.net) Received: from [192.168.1.5] (adsl-67-119-69-243.dsl.sntc01.pacbell.net [67.119.69.243]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 31CA8519AB; Sun, 30 Apr 2006 13:41:16 -0400 (EDT) In-Reply-To: <4450200D.1000809@aol.net> References: <4450200D.1000809@aol.net> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <8FEBADFF-E70E-45C0-B301-EB161479B4BC@mnot.net> Cc: atom-syntax Content-Transfer-Encoding: 7bit X-Image-Url: http://www.mnot.net/personal/MarkNottingham.jpg From: Mark Nottingham Subject: Re: Tools that make use of previous/next/first/last links? Date: Sun, 30 Apr 2006 10:41:19 -0700 To: John Panzer X-Mailer: Apple Mail (2.749.3) Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 I ran it through my demo implementation for Feed History: http://www.mnot.net/rss/history/feed_history.py and it worked fine (after I fixed a bug -- thanks!). To use that, just download the .py and run it on the command line like this: ./feed_history.py [filename] [url] where filename is the name of a local file it can store state in (if you run it again in the future, it won't fetch what it's already seen) and url is the feed. One thing I did notice -- you're using URLs like this for your archives: http://journals.aol.com/panzerjohn/abstractioneer/atom.xml? page=2&count=10 Are they really permanent? If they're relative to the current state of the feed (i.e., the above URI means "give me the ten latest entries"), you can get into some inconsistent states; e.g., if somebody adds/deletes an entry between when the client fetches the different archives. Also, if a client doesn't visit for a long time, it will see http://journals.aol.com/panzerjohn/abstractioneer/atom.xml? page=2&count=10 and assume it already has all of the entries in it, because it's fetched that URI before. On 2006/04/26, at 6:36 PM, John Panzer wrote: > We just deployed support for link@rel="previous" et al. for AOL > Journals. If anyone has a client that makes use of these links, > please let me know, I'd love to see if there are any > interoperability problems. > > Example Atom feed: http://journals.aol.com/panzerjohn/ > abstractioneer/atom.xml > > Thanks, > -- > John Panzer > System Architect > http://abstractioneer.org -- Mark Nottingham http://www.mnot.net/ From owner-atom-syntax@mail.imc.org Sun Apr 30 19:53:12 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FaLiy-0004VJ-I3 for atompub-archive@lists.ietf.org; Sun, 30 Apr 2006 19:53:12 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FaLiy-00030Q-G2 for atompub-archive@lists.ietf.org; Sun, 30 Apr 2006 19:53:12 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FaLVs-0001A7-Lw for atompub-archive@lists.ietf.org; Sun, 30 Apr 2006 19:39:43 -0400 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3UNO72M065524; Sun, 30 Apr 2006 16:24:07 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k3UNO7wR065523; Sun, 30 Apr 2006 16:24:07 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from hotmail.com (bay109-dav15.bay109.hotmail.com [64.4.19.87]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k3UNO63o065517 for ; Sun, 30 Apr 2006 16:24:06 -0700 (MST) (envelope-from j4_james@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 30 Apr 2006 16:24:06 -0700 Message-ID: Received: from 81.179.77.76 by BAY109-DAV15.phx.gbl with DAV; Sun, 30 Apr 2006 23:24:02 +0000 X-Originating-IP: [81.179.77.76] X-Originating-Email: [j4_james@hotmail.com] X-Sender: j4_james@hotmail.com From: "James Holderness" To: "atom-syntax" References: <4450200D.1000809@aol.net> <8FEBADFF-E70E-45C0-B301-EB161479B4BC@mnot.net> Subject: Re: Tools that make use of previous/next/first/last links? Date: Mon, 1 May 2006 00:23:52 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-OriginalArrivalTime: 30 Apr 2006 23:24:06.0383 (UTC) FILETIME=[2CD35FF0:01C66CAD] Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: X-Spam-Score: 4.0 (++++) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Mark Nottingham wrote: > Also, if a client doesn't visit for a long time, it will see > http://journals.aol.com/panzerjohn/abstractioneer/atom.xml? > page=2&count=10 > and assume it already has all of the entries in it, because it's fetched > that URI before. Yeah. That's what I was worried about too. The couple of test feeds that I've subscribed to haven't had any new entries yet so I can't be sure, but with urls like that I don't see how it can possibly work. > Did you find that algorithm wrong, too hard to understand/implement, or > did you just do a different take on it? Does the approach that you took > end up having the same result? The problem I had with the algorithm was that it required two passes. The first pass to gather all the links, starting with the current feed document and moving back in time through the archives; the second pass to actually process the documents, starting with the oldest and moving forwards in time. Either this required retrieving everything twice, or caching every document retrieved. Neither of those options sounded particularly appealing to me. My implementation does everything in one pass. I start by processing the current feed document. If it contains a history link which I haven't seen before, I'll retrieve and process that document next. Repeat until there are no more links or I encounter a link that I've seen before. There are subtle differences in the results that you would get from my algorithm, and technically what you're suggesting is more accurate, but I don't think the differences are significant enough to care about. Other than that, I skip steps 1 and 2, and I default to using the "next" link relation (with a fallback to "previous" and "prev"). I may consider adding support for fh:complete at some point, but for now I'm sticking with Microsoft's cf:treatAs. Regards James