From cd5a2ae0418c236a2d51c03b71235b54903fe995 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Fri, 17 Aug 2007 18:30:16 +0000 Subject: [PATCH] 1.10pre7 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1165 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0060.xml | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/xep-0060.xml b/xep-0060.xml index f38032da..8ed4ae90 100644 --- a/xep-0060.xml +++ b/xep-0060.xml @@ -49,8 +49,8 @@ &ralphm; - 1.10pre6 - in progress, last updated 2007-08-16 + 1.10pre7 + in progress, last updated 2007-08-17 psa
    @@ -60,6 +60,7 @@
  • Added publish-options functionality
  • Added developer-friendly How It Works section
  • Split several long sections into smaller sub-sections.
    • +
  • Clarified that a pubsub service must generate an ItemID if the publisher does not provide one.
 @@ -2251,8 +2252,14 @@ And by opposing end them? -

Any entity that is allowed to publish items to a node (i.e., a publisher or an owner) may do so at any time by sending an IQ-set to the service containing a pubsub element with a <publish/> child; the <publish/> element MUST possess a 'node' attribute and depending on the node configuration MAY contain no &ITEM; elements, one &ITEM; element, or (for Batch Processing) more than one &ITEM; element.

-

Note: It is not necessary for a publication request to include a payload or even an &ITEM; element in order to trigger a notification. For example, the result of publishing to a transient, notification-only node will be a notification that does not include even an &ITEM; element (as shown in the Motivating Example section of this document). However, for the sake of convenience we refer to the act of publication as "publishing an item" (rather than, say, "triggering a notification") even though a publication request will not always contain an &ITEM; element.

+

Any entity that is allowed to publish items to a node (i.e., a publisher or an owner) may do so at any time by sending an IQ-set to the service containing a pubsub element with a <publish/> child.

+

The syntax is as follows:

+
    +
  • The <publish/> element MUST possess a 'node' attribute, specifying the NodeID of the node.
    • +
  • Depending on the node configuration, the <publish/> element MAY contain no &ITEM; elements, one &ITEM; element, or (for Batch Processing) more than one &ITEM; element. It is not necessary for a publication request to include a payload or even an &ITEM; element in order to trigger a notification. For example, the result of publishing to a transient, notification-only node will be a 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 a notification") even though a publication request will not always contain an &ITEM; element.
    • +
  • 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.
    • +
+

An example follows.