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

XEP-0300: Clarify textual content of the <hash/> element.

Browse Source
This commit is contained in:
Florian Schmaus 2017-08-21 00:05:31 +02:00
parent a4f01fabf3
commit 5a7c5610b4
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
xep-0300.xml
View File

@ -24,6 +24,12 @@
&mwild;
&ksmith;
&tobias;
<revision>
<version>0.5.2</version>
<date>2017-08-20</date>
<initials>fs</initials>
<remark><p>Clarify textual content of the &lt;hash/&gt; element.</p></remark>
</revision>
<revision>
<version>0.5.1</version>
<date>2017-03-17</date>
@ -117,7 +123,7 @@
<td>&rfc7693;</td>
</tr>
</table>
<p>The CDATA of the &lt;hash/&gt; element MUST conform to the base64Binary datatype <note>See &lt;<link url='http://www.w3.org/TR/xmlschema-2/#base64Binary'>http://www.w3.org/TR/xmlschema-2/#base64Binary</link>&gt;.</note> and thus be encoded in accordance with Section 6.8 of &rfc2045;, which recommends that base64 data should have lines limited to at most 76 characters in length. However, any whitespace characters (e.g., '\r' and '\n') MUST be ignored.</p>
<p>The digest produced by the used hash algorithm is included as the XML character data of the &lt;hash/&gt; after being encoded as Base64 as specified in Section 4 of &rfc4648;. Thus the character data MUST conform to the base64Binary datatype <note>See &lt;<link url='http://www.w3.org/TR/xmlschema-2/#base64Binary'>http://www.w3.org/TR/xmlschema-2/#base64Binary</link>&gt;.</note> as defined in &w3xmlschema2;.</p>
</section1>
<section1 topic='Hash Functions' anchor='hashes'>
@ -399,7 +405,7 @@
<section1 topic='Acknowledgements' anchor='ack'>
<p>Thanks to Dave Cridland, Waqas Hussain, Glenn Maynard, Remko
Tronçon, and Christian Schudt for their input.</p>
Tronçon, Christian Schudt, and Florian Schmaus for their input.</p>
</section1>
</xep>