On 11/7/06 10:17 AM, "Joe Gregorio" <[EMAIL PROTECTED]> wrote:
>> so, atom:updated will be redefined to mean app:modified > > There is no such thing as app:modified. literally? pedantically? no. not defined in any spec. is there a concept under discussion which has been referred to as app:modified with meaning of "any change results in this timestamp being updated"? yes. >> ... and then somehow >> we update the format spec > > I said no such thing. I said we give a concrete definition > of "significant" in the APP, so that in the APP context > we have something useful to work with. I see no reason > to extend or expand the concrete definition of "significant" > beyond the APP at this point. It was implied in what you did say though: since any change increments atom:updated, despite any author/client directions to the contrary, we then need to either discard the functionality/description in the format spec for atom:updated, or we define a new element for the format spec with the old definition but a new name. Unless you meant something else, such as limiting your definition to APP collections ... thus atom:updated in an entry in an app collection reflects the last modified datestamp, but the atom:updated element in the same entry in the subscription feed (or directly retrieved for editing) reflects the atom:updated value supplied by the author? e.
