[Standards] OTR

Bartosz Małkowski bmalkowski at tigase.pl
Tue Dec 23 10:41:40 UTC 2014

> Wiadomość napisana przez Florian Schmaus <flo at geekplace.eu> w dniu 23 gru 2014, o godz. 11:14:
> I see two design issues. You already mentioned the custom type value.
> Never invent new values for defined (top level) elements or new
> attributes (XEP-0134 § 2.1).
> Also your custom (OTR) payload should (must?) be encapsulated into a
> extension element. So your example becomes:
> <message to='user at example.org'>
>  <otr xmlns='urn:xmpp:otr:1'>
>    <!-- OTR payload here -->
>  </otr>
> </message>

Don’t shoot!
I assume that it was just example to illustrate solution.

Bartosz Małkowski
Tigase Polska
xmpp:bmalkow at malkowscy.net

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 486 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.jabber.org/pipermail/standards/attachments/20141223/65dafbc5/attachment.sig>

More information about the Standards mailing list