Skip to content
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

Jump to bottom

XEP-0060: Add pubsub#public in Publish-Subscribe features #824

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

XEP-0060: Add pubsub#public in Publish-Subscribe features #824

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
16 changes: 16 additions & 0 deletions xep-0060.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -927,6 +927,7 @@ And by opposing end them?
<section2 topic='Discover Nodes' anchor='entity-nodes'>
<p>If a service implements a hierarchy of nodes (by means of <link url='#collections'>Collection Nodes</link>), it MUST also enable entities to discover the nodes in that hierarchy by means of the <strong>Service Discovery</strong> protocol, subject to the recommendations in <cite>XEP-0030</cite> regarding large result sets (for which &xep0055; or some other protocol SHOULD be used). The following examples show the use of service discovery in discovering the nodes available at a hierarchical pubsub service.</p>
<p>Note: Node hierarchies and collection nodes are OPTIONAL. For details, refer to the <link url='#impl-semantics'>NodeID Semantics</link> and <link url='#collections'>Collection Nodes</link> sections of this document.</p>
<p>The service SHOULD return a full list of the public nodes it hosts (i.e., not return any nodes that don't contain the "http://jabber.org/protocol/pubsub#public" feature or that have the feature set to false).</p>
<p>In the first example, an entity sends a service discovery items ("disco#items") request to the root node (i.e., the service itself), which is a <link url='#collections'>Collection Node</link>:</p>
<example caption='Entity asks service for all first-level nodes'><![CDATA[
<iq type='get'
Expand Down Expand Up @@ -1073,6 +1074,9 @@ And by opposing end them?
<field var='pubsub#contact' label='People to contact with questions' type='jid-multi'>
<value>[email protected]</value>
</field>
<field var='pubsub#public' label='Make node publicly searchable' type='boolean'>
<value>1</value>
</field>
<field var='pubsub#access_model' label='Access model' type='list-single'>
<value>open</value>
</field>
Expand Down Expand Up @@ -5237,6 +5241,12 @@ And by opposing end them?
<td>RECOMMENDED</td>
<td><link url='#auto-subscribe'>Auto-Subscribe</link></td>
</tr>
<tr>
<td>public</td>
<td>Public searching for a node is supported.</td>
<td>OPTIONAL</td>
<td><link url='#entity-nodes'>Discover Nodes</link></td>
</tr>
<tr>
<td>publish</td>
<td>Publishing items is supported.</td>
Expand Down Expand Up @@ -6123,6 +6133,11 @@ xmpp:pubsub.shakespeare.lit?pubsub;action=retrieve;node=princely_musings;item=ae
<desc>Implicit presence-based subscriptions are supported.</desc>
<doc>XEP-0060</doc>
</var>
<var>
<name>http://jabber.org/protocol/pubsub#public</name>
<desc>Public searching for a node is supported.</desc>
<doc>XEP-0060</doc>
</var>
<var>
<name>http://jabber.org/protocol/pubsub#publish</name>
<desc>Publishing items is supported.</desc>
Expand Down Expand Up @@ -6945,6 +6960,7 @@ xmpp:pubsub.shakespeare.lit?pubsub;action=retrieve;node=princely_musings
<xs:enumeration value='persistent-items'/>
<xs:enumeration value='presence-notifications'/>
<xs:enumeration value='presence-subscribe'/>
<xs:enumeration value='public'/>
<xs:enumeration value='publish'/>
<xs:enumeration value='publish-options'/>
<xs:enumeration value='publish-only-affiliation'/>
Expand Down