You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: xep-0060.xml
+46-1
Original file line number
Diff line number
Diff line change
@@ -50,6 +50,14 @@
50
50
&pgmillard;
51
51
&stpeter;
52
52
&ralphm;
53
+
<revision>
54
+
<version>1.25.1</version>
55
+
<date>2023-09-07</date>
56
+
<initials>melvo</initials>
57
+
<remark>
58
+
<p>Add examples for publishing item without ID</p>
59
+
</remark>
60
+
</revision>
53
61
<revision>
54
62
<version>1.25.0</version>
55
63
<date>2023-03-22</date>
@@ -2761,7 +2769,6 @@ And by opposing end them?
2761
2769
<li>Depending on the node configuration, the <publish/> element MAY contain no &ITEM; elements or one &ITEM; element. <note>The inclusion of more than one &ITEM; element is no longer allowed, given the removal of batch publishing from version 1.13 of this specification.</note> <note>It is not necessary for a publication request to include a payload or even an &ITEM; element in order to trigger an event notification. For example, the result of publishing to a transient, notification-only node will be an event notification that does not include even an &ITEM; element. However, for the sake of convenience we refer to the act of publication as "publishing an item" (rather than, say, "triggering an event notification") even though a publication request will not always contain an &ITEM; element.</note></li>
2762
2770
<li>The <item/> element provided by the publisher MAY possess an 'id' attribute, specifying a unique ItemID for the item. If an ItemID is not provided in the publish request, the pubsub service MUST generate one and MUST ensure that it is unique for that node.</li>
2763
2771
</ul>
2764
-
<p>An example follows.</p>
2765
2772
<examplecaption='Publisher publishes an item with an ItemID'><![CDATA[
0 commit comments