Hi, what exactly was the reason for a namespace bump for urn:xmpp:hashes:1 => urn:xmpp:hashes:2 ?
I couldn’t find any discussion about it in the Last Call [1], nor do I see any real difference to the previous version 0.4 [2]. The only difference I see is, that the document now explicitly mentions the base64 encoding, but I think it was clear enough before (due to samples). Is that worth a namespace bump? Are there any interoperability issues otherwise? The XML schema is still the same and it still says „xs:string“, although it should probably say „xs:base64binary“ then!? As a side node, XEP-0264: Jingle Content Thumbnails still refers to the old namespace (although XEP-0234 has been updated). Kind regards, — Christian [1]: https://mail.jabber.org/pipermail/standards/2016-November/031594.html [2]: https://xmpp.org/extensions/attic/xep-0300-0.4.html _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
