I have just submitted https://github.com/xsf/xeps/pull/1275
I remember first mentioning it here[0] and jonas giving me a quick answer[1] at the time. I've seen this happen again recently and I decided to give it some time. What happens when a client publishes on a full node seems to be unspecified at the moment. This change proposes to add a new configuration option to specify new behaviour, namely retraction, or rejection. Please do provide suggestions for better naming. When configured to "reject", I propose to have the service return cancel/conflict. It seems conflict is already returned on publish-options error so a <node-full/> element SHOULD be returned alongside to differenciate. When configured to "retract", I propose to allow the item to be published, retracting an existing item beforehand. It is currently worded as "the item with the earliest creation date MUST be retracted", but I wonder there should be more options for this, such as "retract_created", "retract_updated", etc. For backwards compatibility, which is implementation defined, this option simply won't be set. I am not sure there is a way to unset a node option though, so maybe there should be a "¯\_(ツ)_/¯" (shrug) variant to this new option. I have also added a disco feature for discoverability. Have a missed a place to edit in the spec? Feedback welcome! [0]: https://mail.jabber.org/pipermail/standards/2019-October/036503.html [1]: https://mail.jabber.org/pipermail/standards/2019-October/036506.html
signature.asc
Description: PGP signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
