[Standards] roster schema

[Michal 'vorner' Vaner]

Hello

On Fri, Jul 06, 2007 at 10:54:01AM +0100, Richard Dobson wrote:
>  It would be handy to also specify an extended additional error along with 
>  the <not-allowed/> so that the client can know what part of the roster item 
>  is wrong which would add to the flexibility, e.g. <name-limit-exceeded 
>  xmlns="urn:xmpp:roster:errors"/> and <groupname-limit-exceeded 
>  xmlns="urn:xmpp:roster:errors"/>.

Maybe even add the longest allowed item in the error so the client can
know how much it must restrict the user?

Like <name-limit-exceeded xmlns="urn:xmpp:roster:errors" max-len="511"/>

-- 
A nuclear war can ruin your whole day.

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.jabber.org/pipermail/standards/attachments/20070706/4ded0814/attachment.pgp