From 577ae7fa5b511feec62c43d010503e9500ba5a9f Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre <stpeter@stpeter.im>
Date: Fri, 1 Mar 2013 14:18:53 -0700
Subject: [PATCH] added note about directed presence

---
 xep-0316.xml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/xep-0316.xml b/xep-0316.xml
index e0908a75..5cf2591d 100644
--- a/xep-0316.xml
+++ b/xep-0316.xml
@@ -185,7 +185,6 @@
   </section2>
   <section2 topic='Use Presence' anchor='approach-presence'>
     <p>By definition, a chatroom has presence information about the occupants, because they use directed presence to join the room.</p>
-    <p class='box'>Note: It is strongly NOT RECOMMENDED to use directed presence with Entity Capabilities data that differs from the data included in broadcast presence for the purpose of establishing implicit PEP subscriptions to another entity, because the directed presence information will be overwritten by any subsequent presence broadcast.</p>
   </section2>
   <section2 topic='Filtered Notifications' anchor='approach-filter'>
     <p>By default, the use of directed presence is used to establish a MEP subscription to the chatroom's eventing data. In order to filter which notifications are sent by the MEP service, the contact's client includes extended &xep0115; information in the directed presence notifications it sends to the chatroom. Because the MEP-enabled room supports the "filtered-notifications" feature, it sends only those notifications that match the occupant's expressed notification preferences.</p>