From 5a7c5610b43c2432fbccc9b7028272bb485560f7 Mon Sep 17 00:00:00 2001 From: Florian Schmaus Date: Mon, 21 Aug 2017 00:05:31 +0200 Subject: [PATCH 1/2] XEP-0300: Clarify textual content of the element. --- xep-0300.xml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/xep-0300.xml b/xep-0300.xml index aba2df22..eb5d2404 100644 --- a/xep-0300.xml +++ b/xep-0300.xml @@ -24,6 +24,12 @@ &mwild; &ksmith; &tobias; + + 0.5.2 + 2017-08-20 + fs +

Clarify textual content of the <hash/> element.

 + 0.5.1 2017-03-17 @@ -117,7 +123,7 @@ &rfc7693; -

The CDATA of the <hash/> element MUST conform to the base64Binary datatype See <http://www.w3.org/TR/xmlschema-2/#base64Binary>. 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.

+

The digest produced by the used hash algorithm is included as the XML character data of the <hash/> after being encoded as Base64 as specified in Section 4 of &rfc4648;. Thus the character data MUST conform to the base64Binary datatype See <http://www.w3.org/TR/xmlschema-2/#base64Binary>. as defined in &w3xmlschema2;.

@@ -399,7 +405,7 @@

Thanks to Dave Cridland, Waqas Hussain, Glenn Maynard, Remko - Tronçon, and Christian Schudt for their input.

+ Tronçon, Christian Schudt, and Florian Schmaus for their input.

 From 97454eb280845f9e4fa5ae55b12de43b14ce8669 Mon Sep 17 00:00:00 2001 From: Florian Schmaus Date: Wed, 14 Feb 2018 22:48:36 +0100 Subject: [PATCH 2/2] XEP-0300: Address feedback from PSA --- xep-0300.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xep-0300.xml b/xep-0300.xml index 86d4f227..87e48e5a 100644 --- a/xep-0300.xml +++ b/xep-0300.xml @@ -26,7 +26,7 @@ &tobias; 0.5.3 - 2017-10-04 + 2018-02-14 fs

Clarify textual content of the <hash/> element.

 @@ -131,7 +131,7 @@ &rfc7693; -

The digest produced by the used hash algorithm is included as the XML character data of the <hash/> after being encoded as Base64 as specified in Section 4 of &rfc4648;. Thus the character data MUST conform to the base64Binary datatype See <http://www.w3.org/TR/xmlschema-2/#base64Binary>. as defined in &w3xmlschema2;.

+

The digest produced by the used hash algorithm is included as the XML character data of the <hash/> element after being encoded using Base64 as specified in Section 4 of &rfc4648;. Thus the character data MUST conform to the base64Binary datatype See <http://www.w3.org/TR/xmlschema-2/#base64Binary>. as defined in &w3xmlschema2;. The Base64 output MUST NOT include whitespace and MUST set padding bits to zero.