Re: SIMPLE chat: Internationalization and normalization of nicknames
Ben Campbell <[email protected]>
| Newsgroups | gmane.ietf.simple |
|---|---|
| Message-ID | <[email protected]> |
On Mar 1, 2012, at 4:26 PM, Peter Saint-Andre wrote: > On 3/1/12 3:12 PM, Ben Campbell wrote: >> >> [...] >> (as individual) >> >> I concur with this approach in general, although I think we will find >> some differences between the Resource parts in 6122/6122bis and the >> use of nicknames in simple-chat. In particular: >> >> 1) A resource part identifies something. That makes uniqueness and >> comparisons fairly important. OTOH, a nickname is really for human >> display purposes. We still need to be able to compare them for >> reservations to work. And the human readability part means we should >> at least mention character confusion issues. > > In the chatroom context, XMPP resourceparts are mostly used for display > purposes but also for some authorization decisions (e.g., we can kick > people based on their nickname). As far as I understand it, the uses are > really quite similar in XMPP chatrooms and SIMPLE chatrooms. > My understanding of simple-chat is that the participant that you make policy decisions about would be identified by a bona-fide URI. For example, if we kick someone, we would supply the URI. The nickname is a data attribute associated with the URI, and really is a display name for most practical purposes. Of course, you might select the nickname in a GUI in order to get you client to do the right thing. >> 2) The 6122bis resource parts live inside URIs, while simple-chat >> nicknames are just strings. > > Well, we don't really use URIs in XMPP. Probably you mean JIDs > (JabberIDs). In that case, yes, they are used sometimes for addressing > in XMPP chatrooms (e.g., to send a private message to another occupant). You are right of course :-) I mean JIDs. > >> I'm not sure that these differences really change the outcome >> much--they're just things to think about. > > Although I think that XMPP resourceparts *as they are used in chatrooms* > are quite similar to SIMPLE nicknames, resourceparts are used in other > contexts (e.g., as device/connection identifiers) so the resourceprep > replacement that's developed in the XMPP WG won't be quite what you need > anyway. However, there probably is value in thinking about nicks in > general, because it's possible that we could define the same PRECIS > profile for use in both XMPP chatrooms (XEP-0045) and SIMPLE chatrooms. > A common approach might be good. Agreed. Also, since simple-chat uses the nickname from the XCON common data model, other clients of that data model may have similar issues. > > Peter > > -- > Peter Saint-Andre > https://stpeter.im/ > >