Skip to content

XEP-0060: Describe the 'http://jabber.org/protocol/pubsub' disco#info feature #1468

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
iNPUTmice merged 3 commits into from
Nov 11, 2025
Merged

XEP-0060: Describe the 'http://jabber.org/protocol/pubsub' disco#info feature #1468

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bebbe71
XEP-0060: Describe the 'http://jabber.org/protocol/pubsub' disco#info…
guusdk Oct 6, 2025
2ad60bf
Update xep-0060.xml - apply review suggestion
guusdk Oct 9, 2025
4b09d38
Merge branch 'master' into XEP-0060_base-feature
iNPUTmice Nov 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 21 additions & 1 deletion xep-0060.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,14 @@
&pgmillard;
&stpeter;
&ralphm;
<revision>
<version>1.30.0</version>
<date>2025-11-11</date>
<initials>gdk</initials>
<remark>
<p>Describe the 'http://jabber.org/protocol/pubsub' disco#info feature.</p>
</remark>
</revision>
<revision>
<version>1.29.0</version>
<date>2025-11-11</date>
Expand Down Expand Up @@ -1060,6 +1068,7 @@ And by opposing end them?
</iq>
]]></example>
<p>The possible pubsub features are noted throughout this document and have been registered as described in the <link url='#registrar'>XMPP Registrar Considerations</link> section of this document. For information regarding which features are required, recommended, and optional, see the <link url='#features'>Feature Summary</link> section of this document.</p>
<p>Note: The value 'http://jabber.org/protocol/pubsub' is historically commonly advertised as a feature for a pubsub service. Although it has been used in examples of previous versions of this specification, it is not a feature that was previously normatively defined. It is RECOMMENDED that services include that value as feature for compatibility, but entities should not depend on it being advertised. To identify a pubsub service, entities can depend on the advertised service discovery identity.</p>
</section2>

<section2 topic='Discover Nodes' anchor='entity-nodes'>
Expand Down Expand Up @@ -5207,14 +5216,20 @@ And by opposing end them?

<section1 topic='Feature Summary' anchor='features'>
<p>This section summarizes the features described herein, specifies the appropriate requirements level for each feature (REQUIRED, RECOMMENDED, or OPTIONAL), and provides cross-references to the section of this document in which each feature is described.</p>
<p>Note: The feature names are all of the form "http://jabber.org/protocol/pubsub#name", where "name" is the text specified in the first column below.</p>
<p>Note: Except for the first entry, the feature names are all of the form "http://jabber.org/protocol/pubsub#name", where "name" is the text specified in the first column below.</p>
<table caption='Service Discovery Features'>
<tr>
<th>Name</th>
<th>Description</th>
<th>Support</th>
<th>Section</th>
</tr>
<tr>
<td>http://jabber.org/protocol/pubsub</td>
<td>Identification for generic pubsub capabilities.</td>
<td>RECOMMENDED</td>
<td><link url='#entity-features'>Discover Features</link></td>
</tr>
<tr>
<td>access-authorize</td>
<td>The default access model is "authorize".</td>
Expand Down Expand Up @@ -6145,6 +6160,11 @@ xmpp:pubsub.shakespeare.lit?pubsub;action=retrieve;node=princely_musings;item=ae
<section2 topic='Service Discovery Features' anchor='registrar-features'>
<p>The XMPP Registrar maintains a registry of service discovery features (see &DISCOFEATURES;), which includes a number of features that may be returned by pubsub services. The following registry submission has been provided to the XMPP Registrar for that purpose.</p>
<code><![CDATA[
<var>
<name>http://jabber.org/protocol/pubsub</name>
<desc>Identification for generic pubsub capabilities</desc>
<doc>XEP-0060</doc>
</var>
<var>
<name>http://jabber.org/protocol/pubsub#access-authorize</name>
<desc>The default node access model is authorize.</desc>
Expand Down