This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

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

Previous message (by thread): [db-wg] last-modified:, a succesor to changed:
Next message (by thread): [db-wg] last-modified:, a succesor to changed:

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Job Snijders job at instituut.net
Thu Apr 17 13:38:47 CEST 2014

On Wed, Apr 16, 2014 at 04:33:12PM +0200, Marco d'Itri wrote:
> On Apr 15, Job Snijders <job at instituut.net> wrote:
> 
> > I look forward to the group's feedback! Also, I'm interested in how
> > people would use this attribute in their workflows or automation. 

> 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.

I think making changed: optional is good addition to the proposal. 

Kind regards,

Job

Previous message (by thread): [db-wg] last-modified:, a succesor to changed:
Next message (by thread): [db-wg] last-modified:, a succesor to changed:

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]