[Standards] XEP-0300 and a future without reading tea leaves

Tobias Markmann tmarkmann at googlemail.com
Thu Jan 12 09:48:57 UTC 2017

Hi all,

This can be seen as a continuation of my classic thread on this very
channel from 2014 titled "File Hashes in XEP-0234". It was so popular, that
even I did lost interest in it. :D

Back to the future, today. XEP-0300 doesn't specify an encoding, the
examples clearly use Base64, specifically Base64 as defined in
https://www.w3.org/TR/xmlschema-2/#base64Binary and used by many other XML
schema. Originally XEP-0234 used to use hex encoding, and still does in its
examples. This lead to, for example, Gajim using hex encoding in its code
for XEP-0300 representation and Swiften using Base64. What a wonderful

Some people might suggest using heuristics, reading tea leaves, use an
algorithm depending on the moon phase, or similar approaches. That does not
sound like an appealing solution to a standard.

My suggestion, as already explained in
https://github.com/xsf/xeps/issues/349 , is pumping the version of the
namespace, and explicitly stating that the encoding MUST be Base64 as
described in
https://www.w3.org/TR/xmlschema-2/#base64Binary .

What do you folks think about this solution? Any suggestions or problems
you see with this approach?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20170112/06d09117/attachment.html>

More information about the Standards mailing list