From 12bd6f5a15063b792ba6810159bf4fc7cdf09977 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Fri, 10 Aug 2007 17:17:22 +0000 Subject: [PATCH] 1.1pre6 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1138 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0163.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/xep-0163.xml b/xep-0163.xml index 4bc0d3d0..79c6743e 100644 --- a/xep-0163.xml +++ b/xep-0163.xml @@ -27,10 +27,10 @@ &stpeter; &ksmith; - 1.1pre5 - in progress, last updated 2007-07-17 + 1.1pre6 + in progress, last updated 2007-08-10 psa -

In accordance with XMPP Council consensus (1) explicitly defined auto-create, auto-subscribe, filtered-notifications, and last-published features, (2) moved them to XEP-0060, and (3) added appropriate references to XEP-0060 throughout; also added friendly but non-normative How It Works section and removed references to private data storage; updated to reflect changes to entity capabilities.

 +

In accordance with XMPP Council consensus (1) explicitly defined auto-create, auto-subscribe, filtered-notifications, and last-published features, (2) moved them to XEP-0060, and (3) added appropriate references to XEP-0060 throughout; also added friendly but non-normative How It Works section and removed references to private data storage; updated to reflect changes to entity capabilities and pubsub.

 1.0 @@ -261,7 +261,7 @@ ]]> -

But how do Romeo and the Nurse tell your server that they are interested in knowing what you're listening to? In generic pubsub they need to explicitly subscribe to your "http://jabber.org/protocol/tune" node. That is still necessary for open access model nodes in PEP if another user does not have a subscription to your presence, such as benvolio@montague.lit in our scenario. But PEP services support two special features:

+

But how do Romeo and the Nurse tell your server that they are interested in knowing what you're listening to? In generic pubsub they typically need to explicitly subscribe to your "http://jabber.org/protocol/tune" node. That may still be necessary for open access model nodes in PEP if another user does not send you presence, such as benvolio@montague.lit in our scenario. But PEP services support two special features:

  1. "auto-subscribe" -- because they are subscribed to your presence, they automatically receive your events (see Use Presence).
  2. "filtered-notification" -- they can include some special flags in their &xep0115; information to specify which event types (payloads) they want to receive (see Filtered Notifications).
    3. @@ -360,7 +360,7 @@

    An entity shall receive event notifications if:

      -
    1. The node has an open access model and the entity has explicitly discovered and subscribed to the node as explained in XEP-0060.
      2. +
    2. The node has an open access model and the entity has explicitly or implicitly subscribed to the node as explained in XEP-0060.
    3. The entity shares presence with the account owner (see Presence Sharing), is authorized to receive events from the node in accordance with the node access model (see XEP-0060), and advertises an interest in the payload type (see Notification Filtering).
    4. 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).