Le vendredi 3 octobre 2025, 20:21:41 heure d’été d’Europe centrale Guus der
Kinderen a écrit :
Hi all,
After some more discussion in the chat room, I am proposing to remove the
ambiguity in XEP-0060 by:
1. replacing the usage of the 'http://jabber.org/protocol/pubsub'
feature with that of 'http://jabber.org/protocol/pubsub#subscribe'
(which is a feature that is defined to be REQUIRED in section 10);
2. add a note to document this change and recommend advertisement of '
http://jabber.org/protocol/pubsub' for compatibility;
3. with regards to another feature, '
http://jabber.org/protocol/pubsub#publish'#39;, to no longer define that as
being REQUIRED in section 10, as section 7.1.1 clearly defines it to be
optional.
Kind regards,
Guus
Sorry my previous message has been delayed.
Your solution seems sensible.
However, regarding subscription, a service may not support it, as specified in
§ 6.1.3.10 . This is actually exploited in XEP-0498 (Pubsub File Sharing) § 9
(Business Rules).
It feels a bit weird to have the feature exposed by disco#info then return a
'feature-not-implemented' error. I guess that we can live with that, but
ideally, I would replace REQUIRED by OPTIONAL for subscribe in XEP-0060 §10.
Best,
Goffi