diff --git a/xep-0004.xml b/xep-0004.xml index 6aad5342..7fb91a1e 100644 --- a/xep-0004.xml +++ b/xep-0004.xml @@ -27,6 +27,12 @@ &jer; &temas; &stpeter; + + 2.13.1 + 2022-07-25 + ssw +

Clarify elements allowed in multi-item data forms

 + 2.13.0 2022-01-21 @@ -318,9 +324,10 @@
  • One and only one <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 inside the <x/> element.

    +

    The <reported/> element MUST appear before any <item/> element inside the <x/> element. Forms of this type MUST NOT contain any top-level fields other than <reported/> and <item/>.

    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. + Similarly, revisions of this XEP before 2.13.1 were ambiguous about whether <reported/> and <item/> elements could co-exist with other top level elements such as <field/> and <title/> and various implementations are known to have handled this in different ways.

    The syntax is as follows: