I was wondering if someone might be able to summarize the issues associated with a <link rel="next"> and <link rel="previous">? What were the primary objections?
I ask because it seems like a very logical core component for the spec, especially as a link relation. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James M Snell Sent: Sunday, October 09, 2005 9:06 PM To: James Holderness Cc: Syntax Atom Subject: Re: Feed History -04 I've been considering asking the Opensearch folks if they would be willing to separate their next/previous/first/last link relations out to a separate spec that could be made a working group draft. The paging functionality they offer provides a solution to paging in the protocol and are generally useful across a broad variety of feed application cases. Regardless, it would be very good to see these registered. - James James Holderness wrote: > > In case anyone is interested, the OpenSearch Response draft can be > found here: > > http://opensearch.a9.com/spec/opensearchresponse/1.1/ > > The rel values they support include next, previous (not prev), start > and end. They have a note next to each saying "This value is pending > IETF registration". Does that mean they've actually started some kind > of registration process or they're just hoping to do so at some point > in the future? > > Another issue worth noting is that their example RSS feed is also > using atom:link to provide this functionality. > > Robert Sayre wrote: > >> No, but Amazon OpenSearch has been threatening to register it, FWIW. :) > > >
