On 16/5/05 8:31 PM, "Graham" <[EMAIL PROTECTED]> wrote: > The only properties of atom:modified we're interested in are: > 1) That different versions have different dates > 2) Sorting chronologically puts the versions in the correct order > > This is to say, the absolute value of the date is irrelevant. The > only thing that matters is whether it is before, after or the same as > other dates that have appeared on a particular entry.
what about comparing that entry against other entries? how do you sort a set of entries into chrono order? > The value does not need to correspond to any particular event in an > entries life-cycle. Suitable values include date of last > modification, or the date the atom:entry is generated by an Atom > producer. does this mean that a dynamic system could cause the same entry to have a new modification date on every retrieval? -1 e.
