From 6627f58b8d143fab93570854aca730703ec4dc8f Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Tue, 29 May 2012 10:32:00 -0600 Subject: [PATCH] 0.3 --- xep-0312.xml | 28 +++++++++++++++++----------- 1 file changed, 17 insertions(+), 11 deletions(-) mode change 100644 => 100755 xep-0312.xml diff --git a/xep-0312.xml b/xep-0312.xml old mode 100644 new mode 100755 index fc80a650..81ab110c --- a/xep-0312.xml +++ b/xep-0312.xml @@ -22,6 +22,12 @@ NOT_YET_ASSIGNED &hildjj; &stpeter; + + 0.3 + 2012-05-29 + psa +

Corrected namespace to use namespace versioning; tweaked some of the delivery rules.

 + 0.2 2012-03-08 @@ -53,22 +59,22 @@ -

When sending initial presence, A subscriber (more precisely, a subscriber's specific full JID) can indicate how long ago it last logged out by including an <ago/> element qualifed by the 'urn:xmpp:ago' namespace; the 'secs' attribute indicates the number of seconds since this resource was last online.

+

When sending initial presence, a subscriber (more precisely, a subscriber's specific full JID) can indicate how long ago it last logged out by including an <ago/> element qualifed by the 'urn:xmpp:ago:0' namespace; the 'secs' attribute indicates the number of seconds since this resource was last online.

- + ]]>

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:

    -
  1. 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.
    2. -
  2. 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).
    3. +
  3. 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 (although see the rule #2 and rule #5 below).
    4. +
  4. The service SHOULD NOT include items that were deleted from the node, and MAY purge the node if items are deleted (naturally, if the node is purged then the service would not be able to meet rule #1 above).
  5. 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).
    6. -
  6. The service SHOULD NOT include items that were removed from the node.
    7. +
  7. 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).
  8. The service MAY limit the number of notifications that it sends to avoid resource contraints.
  9. The service MAY include &xep0059; data so that the subscriber can page through the set of interim notifications.
-

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).

+

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 delivery toggles notifications "on" when receiving initial presence and toggles notifications "off" when receiving unavailable presence).

 @@ -106,12 +112,12 @@ -

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.

+

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 a suggestion for developers; implementation and deployment experience might indicate that other values are more prudent.

 -

The ®ISTRAR; shall add 'urn:xmpp:ago' to its registry at &NAMESPACES;.

+

The ®ISTRAR; shall add 'urn:xmpp:ago:0' to its registry at &NAMESPACES;.

Support for the feature defined in this document is advertised by the "http://jabber.org/protocol/pubsub#since" Service Discovery feature.

@@ -123,7 +129,7 @@ The pubsub or PEP service sends interim notifications upon receiving initial presence containing the subscriber's last logout time. - XEP-xxxx + XEP-0312 ]]> @@ -135,8 +141,8 @@