[Standards] OTR

Florian Schmaus flo at geekplace.eu
Tue Dec 23 11:32:07 UTC 2014


On 23.12.2014 11:41, Bartosz Małkowski wrote:
> 
>> 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.
> :-)

Of course. I just don't want to leave those examples uncommented,
otherwise people may start considering that as a good/valid example.

- Florian


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 668 bytes
Desc: OpenPGP digital signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20141223/a295852d/attachment.sig>


More information about the Standards mailing list