From 5569bdec3dc141654f577e522e33526fd472dfb6 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Wed, 20 Aug 2008 19:18:03 +0000 Subject: [PATCH] removed Notifying Owners use case git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2167 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0060.xml | 24 ------------------------ 1 file changed, 24 deletions(-) diff --git a/xep-0060.xml b/xep-0060.xml index c14bf971..53d27536 100644 --- a/xep-0060.xml +++ b/xep-0060.xml @@ -4452,30 +4452,6 @@ And by opposing end them? - - ]]> - - -

If the node is configured to support the "pubsub#notify_sub" option, the service MUST send to the node owners notifications regarding new subscribers, SHOULD send notifications regarding unsubscribe actions, and MAY send notifications regarding other subscription changes. The relationship between these notifications and the retrieval of the subscriptions list as described under Retrieve Subscriptions List is similar to the relationship between a "roster get" and a "roster push" as described in &xmppim;.

-

In particular, the notification consists of a &MESSAGE; stanza containing a <pubsub/> element qualified by the 'http://jabber.org/protocol/pubsub#owner' namespace, which contains a <subscriptions/>l element whose 'node' attribute specifies the NodeID of the relevant node; this <subscriptions/> element in turn contains one <subscription/> element whose 'jid' attribute specifies the address of the subscriber and whose 'subscription' attribute specifies the suubscription state.

-

For instance, the following example shows a new subscriber notification.

- - - - - - - - ]]> -

The following example shows an unsubscribe notification.

- - - - - - ]]>