<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="+1"><tt>HI Tim</tt></font><br>
<br>
<div class="moz-cite-prefix">On 07/05/2015 09:55, Tim Bruijnzeels
wrote:<br>
</div>
<blockquote cite="mid:8F49CA1A-CF97-48CC-A921-290A7F26CB8F@ripe.net"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=windows-1252">
Dear working group,
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 06 May 2015, at 18:14, denis <<a
moz-do-not-send="true"
href="mailto:ripedenis@yahoo.co.uk" class="">ripedenis@yahoo.co.uk</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">
<blockquote
cite="mid:499D7D01-B473-46B0-8576-3717D580974D@ripe.net"
type="cite" class="">
<div class="">If an object is submitted without any
changes it will always result in an update, because
when we compare the object the "last-modified:"
value will typically not match.(unless the update is
done at sub-second speed) In other words what should
be a "no-op" now results in a "touch" operation
where only the "last-modified:" attribute is
changed.</div>
</blockquote>
<br class="">
<span class="">Just an observation. This might actually
be a useful side effect. It allows maintainers of
objects to 'touch' their objects and show they are
alive and actively maintaining their data even when
nothing needs to change. I am sure some people in the
community who are going to start monitoring
"last-changed:" attributes to argue that data is out
of date would appreciate that, or even request it.</span></div>
</div>
</blockquote>
</div>
<br class="">
</div>
<div class="">Sure, there is something to be said for this, but
the downside of this is that the version history of the object
becomes very large, which may not be desired.</div>
<div class=""><br class="">
</div>
<div class="">As far as I know this was not explicitly specified
beforehand, so it would be good to have a clear WG consensus
call on this now.</div>
<div class=""><br class="">
</div>
<div class="">For the moment we feel that it's probably best to
apply the planned 'fix' because the behaviour will then be
consistent with no-ops until now, but we can always revert this
change when we get a clear direction from the WG.</div>
</blockquote>
<br>
It was just one of my crazy ideas that came to mind as I read your
comment. Don't hold back on your 'fix' just on my comment.<br>
<br>
cheers<br>
denis<br>
<blockquote cite="mid:8F49CA1A-CF97-48CC-A921-290A7F26CB8F@ripe.net"
type="cite">
<div class=""><br class="">
</div>
<div class="">Kind regards,</div>
<div class=""><br class="">
</div>
<div class="">Tim Bruijnzeels</div>
<div class=""><br class="">
</div>
<div class="">Assistant Manager Software Engineering</div>
<div class="">RIPE NCC</div>
</blockquote>
<br>
</body>
</html>