On 08/05/13 23:30, XMPP Extensions Editor wrote:
URL: http://xmpp.org/extensions/inbox/jidprep.html
From ยง4 Implementation Notes:
> In order to reduce the number of queries made by clients, the server
SHOULD ensure that any JID slots understood by the server (e.g. the to
and from attributes, roster item JIDs, etc) are properly normalized.
This feels a bit fuzzy to me. As a client author, how am I meant to know
whether my server is smart/kind enough to normalize (say) the JID in <x
xmlns='http://jabber.org/protocol/muc#user'><item jid=''>? Or even know
whether the server obeys that SHOULD for roster items?
Perhaps the XEP could instead state that services implementing this XEP
MUST normalize JIDs in slots defined by other extensions they implement
(so, if the service offers up rosters, they MUST be normalized; if the
service is a MUC server, it MUST normalise <item jid=''>; etc)?
Or, to keep it simple, define normalizing to/from/roster items as MUSTs,
and say that clients SHOULD NOT in general assume other JIDs are
normalized, unless they know (by means outside the scope of this XEP)
that a particular server normalizes them.
--
Will
