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

Florian Schmaus flo at geekplace.eu
Thu Jun 15 14:45:49 UTC 2017

On 15.06.2017 16:24, Steve Kille wrote:
> Florian,
> Ooops and thanks.
> Fixed by:
>   https://github.com/stevekille/xeps/commit/6779a94b0e5257c94dadd4a6d13aefaa21d2068a

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

-------------- 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/d541d5ec/attachment.sig>

More information about the Standards mailing list