On 23/5/05 3:18 PM, "Roger B." <[EMAIL PROTECTED]> wrote: > With that in mind, what are the actual benefits of atom:modified over > atom:updated? The end result will always be identical, unless I'm > missing a crucial, well-hidden point.
atom:updated is predicated on a new feature yet to be built into common blogging tools -- the concept of specifying if this change is a "significant" change. Most tools just proffer something approximating atom:modified, some tools provide a user-editable date which could be used as a round about way of signifying a "significant" change. theoretically, we're hoping that people won't just smush atom:modified types of values into atom:updated (since it is a required element), preferring to leave atom:updated with it's initial value (effectively atom:published). If common practice is to dump an automated "last modified" value into atom:updated, then the intent and purpose of atom:updated will have been defeated by all that pollution. Which would be sad. e.
