Zhang Zhen wrote:
rel=next is a relationship between two documents, as well as
*between two hfeed*.
Yes, but rel=next is a relationship between two documents, as well
as between *two hfeeds*. ;-)
--
Toby A Inkster
mailto:[EMAIL PROTECTED]
http://tobyinkster.co.uk
Toby, wasn't that what Zhang said? or did you just move the emphasis? :P
I was trying to come up with some situations where people would put a
link to the next page within a document with an hAtom feed and NOT
want to mean the next page (linked in the link) is also the next
page of hatom. I
Toby, wasn't that what Zhang said? or did you just move the
emphasis? :P
Yes, the emphasis -- that rel=next/prev indicates relationships
between *two* hAtom feeds.
I was trying to come up with some situations where people would put a
link to the next page within a document with an hAtom
2008/5/31 Toby A Inkster [EMAIL PROTECTED]:
Yes, the emphasis -- that rel=next/prev indicates relationships between
*two* hAtom feeds.
Indeed, but rel=next/prev should indicate the next and previous feeds, not a
continuation of the current feed. This would be more in line with the
current
Two example pages:
html
titlePage 1/title
link rel=next rev=prev href=page-2
body
div class=hentry
h1 class=entry-titleEntry 1/h1
p class=entry-contentContent./p
/div
/body
/html
html
titlePage 2/title
link rel=prev rev=next href=page-1
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
André Luís wrote:
Still, do you see any way of tieing two hFeeds on separate pages
together? Any way at all?
The best way that I can come up with involves a slight extension to
hAtom. The current hAtom spec only covers a subset of the full Atom
spec. In particular, to cover feed
