<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <tt>Dear Job If we implement attributes with generated values is there any point in keeping the "changed:" attribute at all? It: -is user set to a vast range of dates (user's choice) with as many or few instances as you wish -is unreliable and possibly miss-leading to anyone else -will become, even if correct, a duplication of both the generated values and --list-versions output -requires mandatory email address -invites abuse Maybe it could be deprecated if the proposed attributes are implemented? Regards Denis Walker Business Analyst RIPE NCC Database Team </tt> <div class="moz-cite-prefix">On 17/04/2014 13:38, Job Snijders wrote: </div> <blockquote cite="mid:20140417113847.GO14466@Eleanor.local" type="cite"> <pre wrap="">On Wed, Apr 16, 2014 at 04:33:12PM +0200, Marco d'Itri wrote: </pre> <blockquote type="cite"> <pre wrap="">On Apr 15, Job Snijders <a class="moz-txt-link-rfc2396E" href="mailto:job@instituut.net"><job@instituut.net></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">I look forward to the group's feedback! Also, I'm interested in how people would use this attribute in their workflows or automation. </pre> </blockquote> </blockquote> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap="">No objections to an automatically enforced last-modified attribute, but then I would demote changed to an optional attribute to allow removing duplicate information. I already use changed this way, by only keeping the last one. </pre> </blockquote> <pre wrap=""> I think making changed: optional is good addition to the proposal. Kind regards, Job </pre> </blockquote> </body> </html>