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

Steve Kille steve.kille at isode.com
Thu Jun 15 15:06:12 UTC 2017



> -----Original Message-----
> From: Standards [mailto:standards-bounces at xmpp.org] On Behalf Of Florian
> Schmaus
> Sent: 15 June 2017 15:46
> To: XMPP Standards
> Subject: Re: [Standards] Dealing with the choice to have a different MIX
> roster format
> 
> On 15.06.2017 16:24, Steve Kille wrote:
> > Florian,
> >
> > Ooops and thanks.
> >
> > Fixed by:
> >
> >
> https://github.com/stevekille/xeps/commit/6779a94b0e5257c94dadd4a6d13
> a
> > efaa21d2068a
> 
> Now the sentence is broken. It states
> 
> """
> The request is made by extending the standard roster get request by adding
> a sub-element <mix-info-request/> to the <query/> element
> qualified by the ‘urn:xmpp:mix:0' namespace.
> """
> 
> - It reads like the <query/> element is qualified by the MIX namespace.
> - The term 'sub-element' is far less common as "child element". For example,
> the xeps repo currently has 322 matches for "child element", but only 23 for
> "sub(-)element". An unified nomenclature would be nice.
> 
> - Florian
[Steve Kille] 

Sorry about that.   Fix in:
  https://github.com/stevekille/xeps/commit/57d2379701013c0adcf5736cb194ee64d831041e


Steve




More information about the Standards mailing list