mirror of
https://github.com/moparisthebest/xeps
synced 2024-10-31 15:35:07 -04:00
XEP-0004: clarify rules for multi-item forms
Signed-off-by: Sam Whited <sam@samwhited.com>
This commit is contained in:
parent
7c46fc60c0
commit
5c0c7cd8c5
@ -27,6 +27,12 @@
|
|||||||
&jer;
|
&jer;
|
||||||
&temas;
|
&temas;
|
||||||
&stpeter;
|
&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>
|
<revision>
|
||||||
<version>2.13.0</version>
|
<version>2.13.0</version>
|
||||||
<date>2022-01-21</date>
|
<date>2022-01-21</date>
|
||||||
@ -318,9 +324,10 @@
|
|||||||
<li>One and only one <reported/> element, which can be understood as a "table header" describing the data to follow.</li>
|
<li>One and only one <reported/> element, which can be understood as a "table header" describing the data to follow.</li>
|
||||||
<li>Zero or more <item/> elements, which can be understood as "table cells" containing data (if any) that matches the request.</li>
|
<li>Zero or more <item/> elements, which can be understood as "table cells" containing data (if any) that matches the request.</li>
|
||||||
</ol>
|
</ol>
|
||||||
<p>The <reported/> element MUST appear before any <item/> element inside the <x/> element.</p>
|
<p>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/>.</p>
|
||||||
<p class="box info">
|
<p class="box info">
|
||||||
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.
|
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.
|
||||||
</p>
|
</p>
|
||||||
<p>The syntax is as follows:</p>
|
<p>The syntax is as follows:</p>
|
||||||
<code><![CDATA[
|
<code><![CDATA[
|
||||||
|
Loading…
Reference in New Issue
Block a user