From a372c1920d1e5b422f518c0c732189382a2fc915 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20Sch=C3=A4fer?= Date: Tue, 2 Mar 2021 17:39:16 +0100 Subject: [PATCH] XEP-0004: Add note about compatibility for element ordering After some discussion on-list [1] and in the council [2], we agreed that an informational box would be best to convey the change. [1]: https://mail.jabber.org/pipermail/standards/2021-February/038148.html [2]: https://logs.xmpp.org/council/2021-02-17#2021-02-17-f706cab427273ca0 --- xep-0004.xml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/xep-0004.xml b/xep-0004.xml index f503d324..ca02ae80 100644 --- a/xep-0004.xml +++ b/xep-0004.xml @@ -295,8 +295,10 @@
  • One and only <reported/> element, which can be understood as a "table header" describing the data to follow.
  • Zero or more <item/> elements, which can be understood as "table cells" containing data (if any) that matches the request.
    • -

    The <reported/> element MUST appear before any - <item/> element in the XML document.

    +

    The <reported/> element MUST appear before any <item/> element inside the <x/> element.

    +

    + Older revisions of this XEP (before 2.12.0) did not contain an explicit requirement for the ordering between <reported> and <item>. Implementations are therefore encouraged to be flexible when processing incoming data, as there might still be implementations which do not implement a strict ordering when generating reports. +

    The syntax is as follows: