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

Florian Schmaus flo at geekplace.eu
Thu Jun 15 15:15:25 UTC 2017

On 15.06.2017 16:55, Kevin Smith wrote:
> On 15 Jun 2017, at 15:30, Steve Kille <steve.kille at isode.com> wrote:
>>>> <iq from='juliet at example.com/balcony'
>>>>          id='bv1bs71f'
>>>>          type='get'>
>>>>       <query xmlns='jabber:iq:roster'>
>>>>         <mix-info-request xmlns=‘urn:xmpp:mix:0'/>
>>>>       </query>
>>>> </iq>
>>> I'd also s/mix-info-request/mix/.
>> [Steve Kille] 
>> <mix/> is already used to encode MIX extension to a message, so I would prefer to not use the same element name here. 
> Re-using the same element in different contexts can be problematic, but

Like when? Most, if not all, things in XMPP are context sensitive, and
we already re-use the same element in different contexts in XEPs.

- Florian

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

More information about the Standards mailing list