diff --git a/xep-0060.xml b/xep-0060.xml index b8e98acd..74307931 100644 --- a/xep-0060.xml +++ b/xep-0060.xml @@ -58,6 +58,7 @@
Add data model informational text in Implementation Notes.
Provide a way for a PubSub service to tell a client when a node is full.
Clarify behaviour and current usage of the 'pubsub#itemreply' option.
Fix spec approver
If configured to do so, the service can include the publisher of the item when it generates event notifications.
+If configured to do so (see Associating Events and Payloads with the Generating Entity), the service can include the publisher of the item when it generates event notifications.
Therefore we define the "itemreply" node configuration option, with two possible values:
+Therefore we define the "itemreply" node configuration option, with three possible values:
A node owner MUST NOT define more than one of these options.
-An example is shown below.
+Interoperability note: As of March 2023, the value of "owner" is not widely supported in generic implementations, and clients may choose to avoid it. In contrast, the value of "none" was not specified in previous versions of this document but has been added retrospectively due to implementation support. Therefore, the primary use of the 'pubsub#itemreply' option is to allow node owners to determine whether the server will include a 'publisher' attribute in items or not.
+The JID associated with an item is conveyed via the 'publisher' attribute on the <item/> element, as demonstrated in the below example: