From fc81b38d47a87e36d4f10308e69c66ad81272f47 Mon Sep 17 00:00:00 2001 From: Kevin Smith Date: Mon, 16 Jul 2018 11:10:16 +0100 Subject: [PATCH] Tweak the 'complete' wording to reflect intent --- xep-0313.xml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/xep-0313.xml b/xep-0313.xml index 558cb13a..c638bc80 100644 --- a/xep-0313.xml +++ b/xep-0313.xml @@ -28,6 +28,12 @@ &mwild; &ksmith; + + 0.6.3 + 2018-07-16 + ks + Tweak the 'complete' wording to more clearly reflect original intent + 0.6.2 2018-07-05 @@ -422,7 +428,7 @@ ]]>

Note: There is no concept of an "open query", and servers MUST be prepared to receive arbitrary page requests at any time.

If the UID contained within an <after> or <before> element is not present in the archive, the server MUST return an item-not-found error in response to the query.

-

When the results returned by the server are complete (that is: when they are the last page of the result set), the server MUST include a 'complete' attribute on the <fin> element, with a value of 'true'. If it is not the last page of the result set, the server MUST either omit the 'complete' attribute, or give it a value of 'false'.

+

When the results returned by the server are complete (that is: when they have not been limited by the maximum size of the result page (either as specified or enforced by the server)), the server MUST include a 'complete' attribute on the <fin> element, with a value of 'true'; this informs the client that it doesn't need to perform further paging to retreive the requested data. If it is not the last page of the result set, the server MUST either omit the 'complete' attribute, or give it a value of 'false'.