[Standards] Dealing with the choice to have a different MIX roster format

Steve Kille steve.kille at isode.com
Thu Jun 15 19:44:33 UTC 2017

> -----Original Message-----
> From: Standards [mailto:standards-bounces at xmpp.org] On Behalf Of Sam
> Whited
> Sent: 15 June 2017 20:20
> To: XMPP Standards
> Subject: Re: [Standards] Dealing with the choice to have a different MIX
> roster format
> On Thu, Jun 15, 2017 at 10:38 AM, Florian Schmaus <flo at geekplace.eu>
> wrote:
> > You misunderstood.
> >
> > The point here is that a <mix xmlns='urn:xmpp:mix:1'/> element as
> > child of <query xmlns='jabber:iq:roster'/>, is different than <mix
> > xmlns='urn:xmpp:mix:1'/> as child element of <message
> > xmlns='jabber:client'/>.
> Only by convention or as part of the application logic; as far as a parser is
> concerned those are "the same thing".
> > I can't remember when something like that has ever caused problems, or
> > how I could cause problems in this particular case.
> I think it doesn't cause problems because we normally don't do that.
> An example of somewhere else that we do that would be useful if it exists,
> otherwise I suspect it's just confusing and should probably be avoided.
> —Sam

[Steve Kille] 

Thanks Sam.

This element is NOT going to be called <mix/>.

I'm happy to call it something other than <mix-info-request/> although I think this is a fine choice


More information about the Standards mailing list