Re: Tools that make use of previous/next/first/last links?

Mark Nottingham <[EMAIL PROTECTED]> wrote: > On 2006/05/01, at 12:55 AM, James M Snell wrote: > > > As it stands now, a single feed > > cannot implement APP, OpenSearch AND Feed History. > > Please describe the scenario where you'd want that to happen -- show > the feed. I don't use APP, but th

Re: Tools that make use of previous/next/first/last links?

Mark Nottingham <[EMAIL PROTECTED]> wrote: > Can you expand upon "being more precise about exactly what is needed"? I don't have time to go into very much detail right now, but basically it's about what people are calling 'stable urls' in another part of this thread. The draft calls feeds where

Re: Tools that make use of previous/next/first/last links?

nt'. E.g. the history spec (or something else) would define an element or whatever, that publishers could set and consumers would be required to check. Regards, Peter -- Peter Robinson <http://www.ticketswitch.com/> Concerts, sport and theatre tickets

Re: Tools that make use of previous/next/first/last links?

Mark Nottingham <[EMAIL PROTECTED]> wrote: > 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.,

Re: New Link Relations -- Last Call

Hi Mark, Mark Nottingham <[EMAIL PROTECTED]> wrote: > On 23/10/2005, at 1:04 PM, Peter Robinson wrote: > > > I prefer 'subscribe' because it better describes the meaning and > > intention behind the link, but I can live with 'current' if that is >

Re: New Link Relations -- Last Call

since it is not the natural interpretation if you come at this purely from the standpoint of blog history. On the other hand, if that is *not* the intention then paging for history and paging for OpenSearch will be incompatible. Regards, Peter -- Peter Robinson <http://www.ticketswitch.com/> Concerts, sport and theatre tickets

Re: New Link Relations -- Ready to go?

; current document's URI. +1 I am happy with that wording, though it may have been improved later in the thread. Whatever may have been the original intention, the Atom spec is very clear that rel=self is very different from any possible rel=subscribe. Regards, Peter -- Peter Robinson <http://www.ticketswitch.com/> Concerts, sport and theatre tickets

Re: Feed History -04

ference. Playing devil's advocate for a minute, is it very wrong to use atom:link for feed history in *RSS2*? Regards, Peter -- Peter Robinson <http://www.ticketswitch.com/>

Re: Extensions at the feed level (Was: Re: geolocation in atom:author?)

. I agree. Once you've accepted that there's a difference between "the feed itself" and "the set of all past, present and future articles in the feed" (which there certainly is in the general case) then you really have to accept e) as the only pos

Re: geolocation in atom:author?

Peter Robinson <[EMAIL PROTECTED]> wrote: > I do something similar, intending it to mean "the location of the items > described by this feed" (when there is a single location). > <http://www.ticketswitch.com/cgi-bin/atom_feed.exe?s_geo=53.82:-3.05:10> To the per

Re: geolocation in atom:author?

is a single location). I don't know whether any software understands my intent... <http://www.ticketswitch.com/cgi-bin/atom_feed.exe?s_geo=53.82:-3.05:10> Regards, Peter -- Peter Robinson <http://www.ticketswitch.com/>

Re: OpenSearch and Atom Prototype

as already generating, including OpenSearch. I don't know if any feed consumers actually support it in atom of course... I did noticed just now that OpenSearch 1.1 proposes an OpenSearch autodiscovery mechanism (amongst other things). Regards, Peter [1] <http://www.ticketswitch.com/cgi-bin/atom

Re: round 2: Proposed Changes for format-11

Robert Sayre <[EMAIL PROTECTED]> wrote: > The diffs linked below should reflect comments on the first round. A few more minor nits I'm afraid. (I don't think I've seen these discussed before.) > http://www.franklinmint.fm/2005/08/02/draft-ietf-atompub-format-11.txt | Atom allows the use of IR

Re: Atom Index Extension Proposal

James M Snell <[EMAIL PROTECTED]> wrote: > FYI: http://www.snellspace.com/wp/?p=193 > > Abstract: Proposes two new elements that allow entries to be ordered > within a feed. [xml condensed:] > http://www.w3.org/2005/Atom"; > xmlns:o="http://www.snellspace.com/atom/extensions/proposed

Re: The Atomic age

Tim Bray <[EMAIL PROTECTED]> wrote: > Paul assures me that the remaining IETF process steps will not > introduce material technical changes, and so format-10 is appropriate > as a basis for implementors to go to work. Excellent! > So, implementors... to work. Just to show willing: