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

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
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 811 bytes
Desc: not available
URL: </ripe/mail/archives/db-wg/attachments/20140417/78796dca/attachment.sig>