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

Dear Janos

As Job pointed out we can phase in such a change. So if it is decided to 
remove the "changed:" atribute, as well as communicating such a change 
by various means, we could adjust the software so that any object 
submitted for update containing a "changed:" attribute will have it 
stripped out by the software with a Warning message added to the ack 
response. This would prevent any update script from failing.

If anyone has scripts that read the "changed:" values and expect to find 
them, these scripts would break anyway if the attribute is made optional 
and someone chooses to remove them from their data.

Regards
Denis Walker
Business Analyst
RIPE NCC Database Team

On 17/04/2014 15:25, Janos Zsako wrote:
> Dear all,
>
>> Making changed: entirely optional, and possibly recommend against 
>> using it
>> for new entries, that is something I would be fine with.
>
> I fully agree with Gert here. I am sure deleting the "changed:" attribute
> would break quite a few scripts.
>
> Best regards,
> Janos
>
>
>
>> Gert Doering
>>          -- NetMaster
>>
>
>

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