Re: a methodical approach to defining what date elements we need

[Tim Bray <Tim.Bray@xxxxxxx>]

On Jul 14, 2004, at 8:34 PM, Roger B. wrote:

> So I am most definitely *not* arguing in favor of forcing aggregator 
> authors
> to figure out how to sort arbitrary strings masquerading as dates. 
> What I
> *am* arguing for are:

My best take at this time from following these threads, although this 
isn't at the front of our work queue, is that I do not see much chance 
of getting consensus on any dates other than these two, which (if I 
understand correctly) are the same two that Sam and Dare have been 
arguing for. -Tim

> (1) The Atom-equivalent of RSS pubDate. Meaning, a date that indicates 
> where
> an entry falls within the chronological flow of a blog/feed.
>
> (2) An understanding that (1) may be user-defined (see above), and 
> that the
> user may change the value of (1) at whim.
>
> (3) A "this entry was last updated at this time" element, usually 
> referred
> to in Atom terms as "modified" and usually machine-defined.
>
> If necessary, I can also provide a distinct "created" date, but 
> outside of
> migration between tools, there's not much value in it.
>
> --
> Roger Benningfield
> JournURL: http://journurl.com/
> blog: http://admin.support.journurl.com/