From 67e4b5621eef15393ab797c32a3935d52d4ccb08 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Poisson?= <goffi@goffi.org>
Date: Sat, 6 Nov 2021 15:03:21 +0100
Subject: [PATCH] XEP-0060: Explicitely say that items are returned in
 chronological order.

---
 xep-0060.xml | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/xep-0060.xml b/xep-0060.xml
index 09638a6bc..b2b49ce42 100644
--- a/xep-0060.xml
+++ b/xep-0060.xml
@@ -49,6 +49,12 @@
   &pgmillard;
   &stpeter;
   &ralphm;
+  <revision>
+    <version>1.22.1</version>
+    <date>2021-11-06</date>
+    <initials>jp</initials>
+    <remark><p>Explicitely say that items are returned in chronological order.</p></remark>
+  </revision>
   <revision>
     <version>1.22.0</version>
     <date>2021-09-07</date>
@@ -2215,6 +2221,7 @@ And by opposing end them?
     </section3>
     <section3 topic='Returning All Items' anchor='subscriber-retrieve-returnall'>
       <p>The service then SHOULD return all available items at the node, although it MAY truncate the result set if a large number of items has been published (see next section) and naturally it cannot return items that have been deleted, expired, etc.</p>
+      <p>By default, items are returned in chronological order (from oldest published to most recent published). This order can be explicitely modified by an extensions like &xep0413;.</p>
       <example caption='Service returns all items'><![CDATA[
 <iq type='result'
     from='pubsub.shakespeare.lit'
@@ -2291,6 +2298,7 @@ And by opposing end them?
     <section3 topic='Returning Some Items' anchor='subscriber-retrieve-returnsome'>
       <p>A node may have a large number of items associated with it, in which case it may be problematic to return all of the items in response to an items request. In this case, the service SHOULD return some of the items and note that the list of items has been truncated by including a &xep0059; notation.</p>
       <p>A Pubsub entity supporting &xep0059; SHOULD include a feature of "http://jabber.org/protocol/pubsub#rsm" in its disco#info response, to make it clear that the RSM feature is for PubSub, and not for e.g., &xep0313;.</p>
+      <p>In the same way as for <link url="#subscriber-retrieve-returnal">Returning All Items</link>, items are by default returned in chronological order globally and inside pages. This order can be modified by extensions such as &xep0413;.</p>
       <example caption='Service returns some items via result set management'><![CDATA[
 <iq type='result'
     from='pubsub.shakespeare.lit'
@@ -2439,6 +2447,7 @@ O, what a rogue and peasant slave am I!
     </section3>
     <section3 topic='Requesting the Most Recent Items' anchor='subscriber-retrieve-requestrecent'>
       <p>A service MAY allow entities to request the most recent N items by using the 'max_items' attribute. When max_items is used, implementations SHOULD return the N most recent (as opposed to the N oldest) items. (Note: A future version of this specification may recommend the use of <cite>XEP-0059</cite> instead of the 'max_items' attribute.)</p>
+      <p>Like for <link url="#subscriber-retrieve-returnal">Returning All Items</link> and <link url="#subscriber-retrieve-returnsome">Returning Some Items</link>, items are returned in chronological order.</p>
       <example caption='Subscriber requests two most recent items'><![CDATA[
 <iq type='get'
     from='francisco@denmark.lit/barracks'