Mark Nottingham wrote:
This draft is based on comments received; thanks to everyone. Major
changes;
* Removed 'this' link
* Changed link syntax
* Changed stateful syntax
* Clarified difference between 'subscription' and 'archive' feeds
(note that they're just for the purposes of clarity in this spec)
* Added a bit to the state reconstruction process description
* Added examples
Really good work!
Comments and suggestions welcome as always,
Why not using an xs:boolean for fh:stateful? hence allowing values 0, 1,
true and false.
With the -01 draft (it might have been the same within the -00 one too),
one can't reuse the process to link to archives of "Top Twenty Records"
or "Most Popular Items" (e.g. a monthly "Top Twenty Records" linking to
the previous-month "Top"), because of the "a subscription document whose
fh:stateful element contains "false" MUST NOT contain a fh:prev element".
Why not just stating that if fh:stateful is false then the "prev"-linked
archive feed doesn't not contain a subset of the previous entries but
rather does contain the previous state of the subscription feed. I.e.
the meaning of the fh:prev "link" depends on the value of fh:stateful.
Also, shouldn't there be a note to invite producers to provide an
atom:[EMAIL PROTECTED]"self" referencing the subscription feed?
I also repeat my proposal for an identifier different from an URI for a
reader/aggregator to know whether it has already retrieved an archive
document, e.g. using the "updated" date-time of the "fh:prev"-linked
archive feed.
Example:
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://purl.org/atom/ns#draft-ietf-atompub-format-09";
xmlns:history="[TBD]">
<title>Example Feed</title>
<link href="http://example.org/"/>
<updated>2003-12-13T18:30:02Z</updated>
<author>
<name>John Doe</name>
</author>
<id>urn:uuid:60a76c80-d399-11d9-b93C-0003939e0af6</id>
<history:stateful>true</history:stateful>
<!--
added an "updated" attribute with tha atom:updated value
of the http://example.org/2003/11/index.atom document.
-->
<history:prev updated="2003-11-24T12:00:00Z">
http://example.org/2003/11/index.atom</history:prev>
<entry>
<title>Atom-Powered Robots Run Amok</title>
<link href="http://example.org/2003/12/13/robots_here"/>
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id>
<updated>2003-12-13T18:30:02Z</updated>
<summary>Some text in a new, fresh entry.</summary>
</entry>
</feed>
If I retrieved the feed between 2003-11-24T12:00:00Z and
2003-12-13T18:30:02Z, the fh:prev URI were probably equal to
http://example.org/2003/10/index.atom (october, not november). However,
I didn't miss any entry.
Using the fh:[EMAIL PROTECTED] value, I can know that I didn't miss any entry
and that I then don't need to dereference
http://example.org/2003/11/index.atom (november, the "new" fh:prev URI)
--
Thomas Broyer
