From 8ff8a3b4b22dac1e93407455b5206d607d7fd798 Mon Sep 17 00:00:00 2001
From: Matthew Wild <mwild1@gmail.com>
Date: Thu, 9 Mar 2023 10:55:13 +0000
Subject: [PATCH] XEP-0313 v1.1.0: Clarify a couple of edge cases

---
 xep-0313.xml | 19 ++++++++++++++++++-
 1 file changed, 18 insertions(+), 1 deletion(-)

diff --git a/xep-0313.xml b/xep-0313.xml
index fd74d9fa..f247e68b 100644
--- a/xep-0313.xml
+++ b/xep-0313.xml
@@ -15,6 +15,7 @@
   <lastcall>2017-11-15</lastcall>
   <type>Standards Track</type>
   <sig>Standards</sig>
+  <approver>Council</approver>
   <dependencies>
     <spec>XMPP Core</spec>
     <spec>XEP-0030</spec>
@@ -29,6 +30,17 @@
   </schemaloc>
   &mwild;
   &ksmith;
+  <revision>
+    <version>1.1.0</version>
+    <date>2023-03-09</date>
+    <initials>mw</initials>
+    <remark>
+      <ul>
+        <li>Clarify archive metadata response in the case of an empty archive.</li>
+        <li>Clarify query response in the case of no matching results.</li>
+      </ul>
+    </remark>
+  </revision>
   <revision>
     <version>1.0.1</version>
     <date>2022-02-16</date>
@@ -373,6 +385,10 @@
     consistent with the format defined in &xep0068;. Servers MUST NOT mark any fields in the form as
     being required (i.e. with the data forms &lt;required/&gt; element), regardless of whether they are
     defined in this document or elsewhere.</p>
+
+    <p>Except where explicitly noted below (i.e. 'Limiting results by id'), a query is still considered successful even
+    if the archive is empty or if no messages match the filter criteria - such queries simply return no results.</p>
+
     <section3 topic='Filtering by JID' anchor='filter-jid'>
       <p>If a 'with' field is present in the form, it contains a JID against which to match messages. The
       server MUST only return messages if they match the supplied JID. A message in a user's archive matches if the JID matches either the to or from of the message. An item in a MUC archive matches if the publisher of the item matches the JID; note that this should only be available to entities that would already have been allowed to know the publisher of the events (e.g. this could not be used by a visitor to a semi-anonymous MUC).</p>
@@ -803,8 +819,9 @@
 </iq>
 ]]></example>
 
-  <p>The server response includes a &lt;metadata/&gt; element containing information about the archive. This element MUST include &lt;start/&gt; and &lt;end/&gt;
+  <p>The server response includes a &lt;metadata/&gt; element containing information about the archive. If the archive is not empty, this element MUST include &lt;start/&gt; and &lt;end/&gt;
      elements, which each have an 'id' and XEP-0082 formatted 'timestamp of the first and last messages in the archive respectively.</p>
+  <p>If the archive is empty, the server MUST instead send an empty &lt;metadata/&gt; element.</p>
 </section1>
 
 <section1 topic='Business Rules' anchor='business_rules'>