0.0.2

inbox/pubsub-since.xml

@@ -22,6 +22,12 @@
   <shortname>NOT_YET_ASSIGNED</shortname>
   &hildjj;
   &stpeter;
+  <revision>
+    <version>0.0.2</version>
+    <date>2012-02-29</date>
+    <initials>psa</initials>
+    <remark><p>Addressed some feedback from the XMPP Council.</p></remark>
+  </revision>
   <revision>
     <version>0.0.1</version>
     <date>2012-02-27</date>
@@ -35,7 +41,7 @@
 </section1>
 
 <section1 topic='How It Works' anchor='feature'>
-  <p>As described in XEP-0256, a subscriber can indicate its last logout time when sending initial presence.</p>
+  <p>As described in XEP-0256, a subscriber (i.e., a subscriber's specific full JID) can indicate its last logout time when sending initial presence.</p>
   <example caption='Last Indication in Initial Presence'><![CDATA[
 <presence from='juliet@capulet.com/balcony'>
   <query xmlns='jabber:iq:last' seconds='86511'/>
@@ -43,13 +49,14 @@
   ]]></example>
   <p>Upon receiving such an indication, a pubsub or PEP service that supports presence-based notifications and the "pubsub-since" feature defined herein would behave as follows:</p>
   <ol>
-    <li>The service MUST send to the subscriber all of the notifications stored in the relevant node's history that were generated since the last logout time.</li>
+    <li>The service MUST send to the subscriber's full JID all of the notifications stored in the relevant node's history that were generated since the last logout time.</li>
     <li>The service MAY adjust its definition of "interim notification" to account for reasonable clock skew (e.g., including notifications up to five minutes older than the subscriber's last logout time).</li>
     <li>The service SHOULD include only the final version of each pubsub notification (e.g., in case of items that were updated during the period when the subscriber was offline).</li>
     <li>The service SHOULD NOT include items that were removed from the node.</li>
     <li>The service MAY limit the number of notifications that it sends to avoid resource contraints.</li>
-    <li>The service MAY include &xep0059; data so that the subscriber can page through the set of interim notifications.</li>
+    <li>The service MAY include &xep0059; data so that the subscriber can page through the set of interim notifications, as described in Section 6.5.3 of XEP-0060.</li>
   </ol>
+  <p>If the pubsub service receives subsequent available presence from that full JID (even a presence update that includes the last availability indication), it MUST behave according to the rules in XEP-0060 or XEP-0163 (typically this means it would do nothing, since presence-based notifications toggle notifications on when receiving initial presence and toggling notifications off when receiving unavailable presence).</p>
 </section1>
 
 <section1 topic='Determining Support' anchor='disco'>
@@ -86,6 +93,10 @@
   <p>This document requires no interaction with &IANA;.</p> 
 </section1>
 
+<section1 topic='Implementation Notes' anchor='impl'>
+  <p>The Last Activity extension (XEP-0012) notates time in seconds before the moment of stanza generation. Although some commenters have suggested that it would be easier to implement last activity notations in terms of UTC timestamps, clients can mitigate some implementation problems by storing the last activity time in UTC instead of local time (in case the device is moved across time zones) and by using standard technologies for clock synchronization such as &rfc1305; and &xep0202;. The five-minute grace period is merely an implementation suggestion; implementation and deployment experience might indicate that other values are more prudent.</p>
+</section1>
+
 <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
   <section2 topic='Service Discovery Features' anchor='registrar-features'>
     <p>Support for the feature defined in this document is advertised by the ""http://jabber.org/protocol/pubsub#since"" Service Discovery feature.</p>