On 2 Mar 2017, at 21:02, Jonas Wielicki <[email protected]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On Donnerstag, 23. Februar 2017 08:05:23 CET XMPP Extensions Editor wrote: >> Version 0.8.1 of XEP-0369 (Mediated Information eXchange (MIX)) has been >> released. >> >> […] >> >> URL: https://xmpp.org/extensions/xep-0369.html > > This version still has Example 40 as follows: > > <iq type='result' > to='[email protected]/d104f6a7-97e9-477f-8947-e4a37691d7ee/ > 7533375f-2cd1-4455-a311-494bab21f9f0' > from='mix.shakespeare.example' > id='7nve413p'> > <query xmlns='http://jabber.org/protocol/disco#info'/> > <feature xmlns='urn:xmpp:mix:0' var='mix_nick_register'/> > </query> > </iq> > > The use of a different namespace on <feature/> in a disco#info reply worries > me. This doesn’t work with XEP-0115 (I hope, because <{urn:xmpp:mix:0}feature/ >> and <{http://jabber.org/protocol/disco#info}feature/> are fundamentally > different elements) and is, as far as I know, specified nowhere as a valid > use > of disco#info. Of course, disco#info permits additional elements as > extension, > but I don’t know whether that was intended here. > > I think the cleaner way would be to use > var='urn:xmpp:mix:0#mix_nick_register' > like like many other XEPs do. That way other protocols relying on all > features > being available in {http://jabber.org/protocol/disco#info}feature elements > won’t break. > > I feel this hasn’t got enough discussion yet, which is why I’m bringing it up > once more in a separate thread.
This is clearly a typo. /K _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
