[Standards] Clarify meaning of pubsub#item_expire: creation or modification?

Martin debacle at debian.org
Fri Sep 17 09:29:17 UTC 2021


this question came up when discussing the server side implementation of
pubsub#item_expire: Is expiry relative to original creation or to last

It looks like both options can make sense, but in most cases, last
modification is more useful, e.g. when a singleton node is updated or in
case of redacted blog posts.

Also, the standard already says, that re-publication were equivalent to

> Note: If a publisher publishes an item with an Item ID and the ItemID
> matches that of an existing item, the pubsub service MUST NOT fail the
> publication but instead MUST overwrite the existing item and generate
> a new event notification (i.e., re-publication is equivalent to
> modification).

To implement an absolute deadline of an item, the expiry time is not
useful anyway, because it is a per node option, not a per item one. In
such cases, the publisher should remove the node when time comes.

In any case, the standard should clear about what is intended.
Patch attached.

Cheers, Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xep-0060.patch
Type: text/x-diff
Size: 1895 bytes
Desc: xep-0060.patch
URL: <http://mail.jabber.org/pipermail/standards/attachments/20210917/5146cf48/attachment.patch>

More information about the Standards mailing list