[uf-discuss] Next/Prev [was Rationale for providing hAtom instead of Atom/RSS feeds]

Thu May 29 07:46:20 PDT 2008

Oh, I see. Thanks for clearing that up Toby.

Still, do you see any way of tieing two hFeeds on separate pages
together? Any way at all? I'm thiking in terms of data portability...
If the service X doesn't provide an EXPORT your data but marks up
content with hAtom, some parser could export all the archive by
following that feed through multiple pages.

--
André

On Thu, May 29, 2008 at 1:01 PM, Toby Inkster <mail at tobyinkster.co.uk> wrote:
> Two example pages:
>
>  <html>
>    <title>Page 1</title>
>    <link rel="next" rev="prev" href="page-2">
>    <body>
>      <div class="hentry">
>        <h1 class="entry-title">Entry 1</h1>
>        <p class="entry-content">Content.</p>
>      </div>
>    </body>
>  </html>
>
>  <html>
>    <title>Page 2</title>
>    <link rel="prev" rev="next" href="page-1">
>    <body>
>      <div class="hentry">
>        <h1 class="entry-title">Entry 2</h1>
>        <p class="entry-content">Content.</p>
>      </div>
>    </body>
>  </html>
>
> As I understand the semantics of next/prev, they indicate links to
> separate resources - not a continuation of the current resource. i.e.
> These pages represent two separate feeds, each of which contains a single
> entry.
>
> The reason some XFN parsers will recurse to rel="me next" and rel="me
> prev" links is not the next/prev relations, but rel="me" -- they can
> spider rel="me" links (presumably constrained to a particular depth limit)
> and consolidate the information into a single unified profile.
>
> -Toby
> _______________________________________________
> microformats-discuss mailing list
> microformats-discuss at microformats.org
> http://microformats.org/mailman/listinfo/microformats-discuss
>