Hi Steve, On Samstag, 1. April 2017 21:20:19 CEST Steve Kille wrote: > Jonas, > > > -----Original Message----- > > From: Standards [mailto:[email protected]] On Behalf Of Jonas > > Wielicki > > Sent: 01 April 2017 20:37 > > To: XMPP Standards > > Subject: Re: [Standards] UPDATED: XEP-0369 (Mediated Information > > eXchange (MIX)) > > > > Hi Steve at al., > > > > I have a few questions about handling of nicknames in MIX. > > > > 1. regarding §6.1.5 Setting a Nick: > > > > There is an example on how to set the nickname. I *assume* that other > > participants are informed about the nickname change as it will be > > published > > in the participants PubSub node, right?. If this is the case, it would be > > great if we could have this clarified in the text. > > [Steve Kille] > > I will put some clarification here. There is an interesting UI question > here. Presence is the natural equivalent to MUC, and I am sure that this > will continue to be shown for MIX channels. However, in MIX, > participants are a superset. A simple UI approach will be simply to > ignore participants. A more sophisticated UI will subscribe to the > presence node, which will enable the client to show channel participants > that are not online. I suspect that the UI will then need to give the > user a choice as to whether to show this or not.
Hmm, I’m not sure we’re on the same page here. I was talking about the participants node, 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? > Looking at this is making me reflect on the participant node XML. > > Currently the participant item syntax is (example): > > <items node='urn:xmpp:mix:nodes:participants'> > <item id='123456#[email protected]'> > <participant xmlns='urn:xmpp:mix:0' > nick='thirdwitch'/> > </item> > </items> > > > I am wondering if it would be better as: > > > <items node='urn:xmpp:mix:nodes:participants'> > <item id='123456#[email protected]' > xmlns='urn:xmpp:mix:0'> <nick>thirdwitch</nick> > </item> > </items> > > > I'd welcome input from those with more XML experience and "XMPP house style" 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. kind regards, Jonas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
