From 1c26c9f2edf49e457f79371157bf9d1de74e0ad2 Mon Sep 17 00:00:00 2001 From: Sam Whited Date: Sun, 28 Aug 2016 11:35:51 -0500 Subject: [PATCH] Let's not be redundant and repeat ourselves --- xep-0369.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xep-0369.xml b/xep-0369.xml index ff5ed87f..71f91482 100644 --- a/xep-0369.xml +++ b/xep-0369.xml @@ -570,7 +570,7 @@
  • The nick is registered with the user account in some way, for example as part of user provisioning with nick configured as an attribute in a directory service. This may be chosen by corporate services that wish to ensure consistent nick values for a set of users and channels.
  • The nick is registered with the MIX service, as described in Registering a Nick .
  • The user explicitly sets the nick, as described in this section.
    • -
  • The MIX service generates the nick. In this case it is recommended that the assigned nick is a UUID unique identifier following &rfc4122;.
    • +
  • The MIX service generates the nick. In this case it is recommended that the assigned nick is a UUID following &rfc4122;.

    • AUTHOR'S NOTE AND QUESTION: REVIEW use of UUID. Can it make sense for other algorithms, such as a string from the JID

    @@ -655,7 +655,7 @@ ]]> -

    If the register request does not contain a <nick/> element, then the MIX service assigns one. It is recommended that the assigned nick is a UUID unique identifier following &rfc4122;. +

    If the register request does not contain a <nick/> element, then the MIX service assigns one. It is recommended that the assigned nick is a UUID following &rfc4122;.