[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 15:37:23 CEST 2014
On Thu, Apr 17, 2014 at 03:25:59PM +0200, 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. When an attribute ends up on the to-be-deprecated list, the community would be given ample time and notice before the change would actually be implemented. Like with referral-by, a procedure such as "inform" -> "warn" -> "error" spread over a few months could be used to make the community aware a change is coming. If you have scripts that rely on a modification date as expressed in "changed:", it would be a rather magnificant upgrade to be able to use "last-modified:" as that attribute is truthful and offers higher resolution. :-) 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 ]