moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 16:55:07 -05:00
Code Issues Releases Wiki Activity

Merge branch 'xep-0004' into premerge

Browse Source
This commit is contained in:
Jonas Schäfer 2022-12-13 18:24:22 +01:00
commit da8bed50e4
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
xep-0004.xml
View File

@ -27,6 +27,12 @@
&jer;
&temas;
&stpeter;
<revision>
<version>2.13.1</version>
<date>2022-07-25</date>
<initials>ssw</initials>
<remark><p>Clarify elements allowed in multi-item data forms</p></remark>
</revision>
<revision>
<version>2.13.0</version>
<date>2022-01-21</date>
@ -318,9 +324,10 @@
<li>One and only one &lt;reported/&gt; element, which can be understood as a "table header" describing the data to follow.</li>
<li>Zero or more &lt;item/&gt; elements, which can be understood as "table cells" containing data (if any) that matches the request.</li>
</ol>
<p>The &lt;reported/&gt; element MUST appear before any &lt;item/&gt; element inside the &lt;x/&gt; element.</p>
<p>The &lt;reported/&gt; element MUST appear before any &lt;item/&gt; element inside the &lt;x/&gt; element. Forms of this type MUST NOT contain any top-level fields other than &lt;reported/&gt; and &lt;item/&gt;.</p>
<p class="box info">
Older revisions of this XEP (before 2.12.0) did not contain an explicit requirement for the ordering between &lt;reported&gt; and &lt;item&gt;. 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 &lt;reported/&gt; and &lt;item/&gt; elements could co-exist with other top level elements such as &lt;field/&gt; and &lt;title/&gt; and various implementations are known to have handled this in different ways.
</p>
<p>The syntax is as follows:</p>
<code><![CDATA[