From cd0ebbe317a28f768fa70bfe5ee81d9f536233e0 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Mon, 13 Oct 2008 18:14:58 +0000 Subject: [PATCH] reference fix git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2370 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0163.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xep-0163.xml b/xep-0163.xml index fb79e999..9bf9dc18 100644 --- a/xep-0163.xml +++ b/xep-0163.xml @@ -366,10 +366,10 @@
  • The entity is the account owner itself, in which case the PEP service shall send notifications to all of the account owner's available resources (subject to notification filtering).
    • -

    A PEP service MUST support the "auto-subscribe" feature defined in Section 10.1 of XEP-0060. This implies that when a user has an XMPP presence subscription to the account owner's presence, the user automatically also has a pubsub subscription account owner's root collection node (i.e., bare JID), with a subscription_type of "items" and a subscription_depth of "all".

    +

    A PEP service MUST support the "auto-subscribe" feature defined in Section 9.1 of XEP-0060. This implies that when a user has an XMPP presence subscription to the account owner's presence, the user automatically also has a pubsub subscription account owner's root collection node (i.e., bare JID), with a subscription_type of "items" and a subscription_depth of "all".

     -

    A PEP service MUST support the "filtered-notifications" feature defined in Section 10.2 of XEP-0060. This implies that when an automatic subscriber can specify which event payloads it wants to receive by including appropriate feature bundles in the XEP-0115 information it broadcasts.

    +

    A PEP service MUST support the "filtered-notifications" feature defined in Section 9.2 of XEP-0060. This implies that when an automatic subscriber can specify which event payloads it wants to receive by including appropriate feature bundles in the XEP-0115 information it broadcasts.