[db-wg] last-modified:, a succesor to changed:

Dear Gert

There is one downside to keeping the "changed:" attribute as optional. 
The RIPE NCC can remove all "changed:" attributes from all objects if 
required. But we can't easily do a selective removal for some users and 
not for others. So if it is kept as optional, those users who might 
prefer to clean the RIPE Database of many email addresses in possibly 
tens of thousands of objects will basically have to do it themselves.

Regards
Denis Walker
Business Analyst
RIPE NCC Database Team


On 17/04/2014 15:20, Gert Doering wrote:
> Hi,
>
> On Thu, Apr 17, 2014 at 02:55:44PM +0200, Job Snijders wrote:
>> On Thu, Apr 17, 2014 at 01:58:39PM +0200, Denis Walker wrote:
>>
>>> If we implement attributes with generated values is there any point in
>>> keeping the "changed:" attribute at all?
>> You are right. "last-modified:" makes "changed:" entirely redundant,
>> would only serve to still my sense of nostalgia. I support removing the
>> "changed:" attribute from all RIPE objects.
> Nah, I do not support that.  Leave my objects alone, if only for my nostalgia.
>
> Making changed: entirely optional, and possibly recommend against using it
> for new entries, that is something I would be fine with.
>
> Gert Doering
>          -- NetMaster

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/db-wg/attachments/20140417/ec491b09/attachment.html>