moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

Merge branch 'xep-0004' into premerge

This commit is contained in:
Jonas Schäfer 2022-02-15 18:12:41 +01:00
parent 15d89d7dc2 69b8363215
commit 7cd6489aa5
1 changed files with 9 additions and 0 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.0</version>
<date>2022-01-21</date>
<initials>melvo</initials>
<remark><p>Add incomplete submission form handling</p></remark>
</revision>
<revision>
<version>2.12.1</version>
<date>2021-06-08</date>
@ -340,6 +346,9 @@
]]></code>
<p>Each of these &lt;item/&gt; elements and the &lt;reported/&gt; element MUST contain one or more &lt;field/&gt; children. The &lt;reported/&gt; element defines the data format for the result items by specifying the fields to be expected for each item; for this reason, its &lt;field/&gt; elements SHOULD possess a 'type' attribute and 'label' attribute in addition to the 'var' attribute, and SHOULD NOT contain a &lt;value/&gt; element. Each &lt;item/&gt; element defines one item in the result set, and MUST contain each field specified in the &lt;reported/&gt; element (although the XML character data of the &lt;value/&gt; element MAY be null).</p>
</section2>
<section2 topic='Incomplete Submission Form Handling' anchor='incomplete-submission-form-handling'>
<p>An incomplete submission form is a data form of the type "submit" that contains all required fields but some optional fields are omitted. The receiving entity of an incomplete submission form SHOULD only process (e.g., apply) the submitted fields. If applicable, the values of the omitted fields SHOULD keep their current value. The current value is often the value found in the corresponding form of the type "form".</p>
</section2>
</section1>
<section1 topic='Data Validation' anchor='validation'>
<p>Data validation is the responsibility of the form-processing entity (commonly a server, service, or bot) rather than the form-submitting entity (commonly a client controlled by a human user). This helps to meet the requirement for keeping client implementations simple. If the form-processing entity determines that the data provided is not valid, it SHOULD return a "Not Acceptable" error, optionally providing a textual explanation in the XMPP &lt;text/&gt; element or an application-specific child element that identifies the problem (see &xep0086; for information about mappings and formats).</p>