1
0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 16:55:07 -05:00

XEP-0313 v1.1.0: Clarify a couple of edge cases

This commit is contained in:
Matthew Wild 2023-03-09 10:55:13 +00:00
parent d0dba9ccb4
commit 8ff8a3b4b2

View File

@ -15,6 +15,7 @@
<lastcall>2017-11-15</lastcall> <lastcall>2017-11-15</lastcall>
<type>Standards Track</type> <type>Standards Track</type>
<sig>Standards</sig> <sig>Standards</sig>
<approver>Council</approver>
<dependencies> <dependencies>
<spec>XMPP Core</spec> <spec>XMPP Core</spec>
<spec>XEP-0030</spec> <spec>XEP-0030</spec>
@ -29,6 +30,17 @@
</schemaloc> </schemaloc>
&mwild; &mwild;
&ksmith; &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> <revision>
<version>1.0.1</version> <version>1.0.1</version>
<date>2022-02-16</date> <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 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 being required (i.e. with the data forms &lt;required/&gt; element), regardless of whether they are
defined in this document or elsewhere.</p> 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'> <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 <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> 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> </iq>
]]></example> ]]></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> 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>
<section1 topic='Business Rules' anchor='business_rules'> <section1 topic='Business Rules' anchor='business_rules'>