Eric Scheid wrote:
On 10/8/05 12:46 PM, "James M Snell" <[EMAIL PROTECTED]> wrote:
This is fairly quick and off-the-cuff, but here's an initial draft to
get the ball rolling..
http://www.snellspace.com/public/draft-snell-atompub-feed-expires.txt
Looks good, I think it does need a little bit of prose explaining that this
has nothing to do with caching, and should not be used in scheduling when to
revisit/refresh/expire local copies of the resource.
Absolutely. I put this together rather quickly fully knowing that I
would need to revisit the text to fully explain the use of the
extension. I'll be taking a few whacks at that over the coming days as
time allows.
Similarly, if I understand correctly, when you write
"The 'max-age' extension element is used to indicate
the maximum age of a feed or entry."
you are referring to the max-age until the informational content of the
respective feed or entry expires. And similarly with age:expires. Yes?
Yes. I will be clarifying this in the draft. The extensions are really
only reflective of the informational content in individual entries. As
we do with the atom:author element, expires and max-age can be specified
at the feed or source level, but apply to the content of individual
entries. e.g.
<feed>
<expires>...</expires>
<entry></entry>
<entry></entry>
</feed>
is equivalent to
<feed>
<entry><expires>...</expires></entry>
<entry><expires>...</expires></entry>
</feed>
Aside: a perfect example of what sense of 'expires' is in the I-D itself...
Network Working Group
Internet-Draft
Expires: January 2, 2006
Excellent point :-)
- James
