From 11b59727a2ad3fd0e142fbec44569e3984c121df Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre <stpeter@jabber.org>
Date: Tue, 29 Jul 2008 03:40:27 +0000
Subject: [PATCH] corrected send_last_published_item description

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2104 4b5297f7-1745-476d-ba37-a9c6900126ab
---
 xep-0163.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xep-0163.xml b/xep-0163.xml
index fb7e639a..1645ccc2 100644
--- a/xep-0163.xml
+++ b/xep-0163.xml
@@ -447,7 +447,7 @@
     <li>Support the "open", "roster", and "whitelist" access models.</li>
     <li>Treat the account owner's bare JID &BAREJID; as a collection node (i.e., as the root collection node for the account's virtual pubsub service).</li>
     <li>Default the 'deliver_notifications' configuration option to true (i.e., deliver payloads by default).</li>
-    <li>Default the 'send_last_published_item' configuration option to true (i.e., send the last publish item by default).</li>
+    <li>Default the 'send_last_published_item' configuration option to on_sub_and_presence (i.e., send the last published item on subscription and on receipt of presence). <note>Because subscriptions are implicit in PEP rather than explicit as in generic pubsub, the on_sub_and_presence setting effectively means sending on presence.</note></li>
   </ul>
   <p>A PEP service MAY support other use cases, affiliations, access models, and features, but such support is OPTIONAL.</p>
 </section1>