> > Hmm, I’m not sure we’re on the same page here. I was talking about the > participants node, [Steve Kille]
Sorry - you just triggered a random related thought. Hope not too confusing which, in my understanding, has nothing to do with the > presence of the participants. So to show participants which are currently not > online, a client would subscribe to the *participants* node, not the > *presence* node, right? > [Steve Kille] Right. > > Please do not do that. <item xmlns='http://jabber.org/protocol/pubsub'/> > (with the xmlns inherited from the <pubsub/> element) and <item > xmlns='urn:xmpp:mix: > 0'/> are entirely different elements. The former is part of the PubSub > protocol as specified in XEP-0060, the latter is not. Using the latter, while > being arguably shorter, breaks compatibility with existing pubsub > implementations. The specified way to put a payload into a pubsub <item/> > is to make it a child element of that item. > [Steve Kille] Ah - I learn more about XML Namespaces the whole time!! I believe this needs fixing up in several places in MIX. Will check For here, how about: <items node='urn:xmpp:mix:nodes:participants'> <item id='123456#[email protected]' > <nick xmlns='urn:xmpp:mix:0'>thirdwitch</nick> </item> </items> Regards Steve _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
