diff --git a/xep-0133.xml b/xep-0133.xml index 22d82585..8ab41427 100644 --- a/xep-0133.xml +++ b/xep-0133.xml @@ -21,71 +21,65 @@ admin &stpeter; - - 1.2pre1 - in progress, last updated 2008-06-10 - psa -

Added use cases for deleting logs and emptying cache.

 - 1.1 2005-08-19 psa -

Added use cases for getting list of idle users and of active users (where online = active + idle), getting number (rather than list) of registered/disabled/online/active/idle users, getting list of disabled users, getting user statistics.

 + Added use cases for getting list of idle users and of active users (where online = active + idle), getting number (rather than list) of registered/disabled/online/active/idle users, getting list of disabled users, getting user statistics. 1.0 2004-12-09 psa -

Per a vote of the Jabber Council, advanced status to Active.

 + Per a vote of the Jabber Council, advanced status to Active. 0.8 2004-12-06 psa -

Addressed Council feedback: folded add blacklist use case into edit blacklist use case; folded add whitelist use case into edit whitelist use case; changed jid-single to jid-multi in many of the use cases; added accountjid field to change password use case; removed grant administrative privileges and revoke administrative privileges use cases (need edit admin list use case only); added max_items field to get active users and get registered users use case.

 + Addressed Council feedback: folded add blacklist use case into edit blacklist use case; folded add whitelist use case into edit whitelist use case; changed jid-single to jid-multi in many of the use cases; added accountjid field to change password use case; removed grant administrative privileges and revoke administrative privileges use cases (need edit admin list use case only); added max_items field to get active users and get registered users use case. 0.7 2004-12-02 psa -

Added use case for editing message of the day.

 + Added use case for editing message of the day. 0.6 2004-11-19 psa -

Further clarified message of the day per list discussion.

 + Further clarified message of the day per list discussion. 0.5 2004-11-17 psa -

Changed firstname to given_name.

 + Changed firstname to given_name. 0.4 2004-11-02 psa -

Added note clarifying concept of message of the day.

 + Added note clarifying concept of message of the day. 0.3 2004-09-30 psa -

Changed command naming requirement from MUST to SHOULD.

 + Changed command naming requirement from MUST to SHOULD. 0.2 2004-07-22 psa -

Added several more use cases; defined complete protocol flows; specified XMPP Registrar considerations.

 + Added several more use cases; defined complete protocol flows; specified XMPP Registrar considerations. 0.1 2004-04-25 psa -

Initial version.

 + Initial version. @@ -1229,7 +1223,7 @@ ]]> -

It may be helpful to enable an administrator to retrieve the number of registered users who are online at any one moment. By "online user" is meant any user or account that currently has at least one active or connected resource as defined in &rfc3920bis; and &rfc3921bis; (whether that user is actively sending XML stanzas or is idle). The command node for this use case SHOULD be "http://jabber.org/protocol/admin#get-online-users-num".

+

It may be helpful to enable an administrator to retrieve the number of registered users who are online at any one moment. By "online user" is meant any user or account that currently has at least one connected or available resource as specified in RFC 3920 and RFC 3921, whether that user is actively sending XML stanzas or is idle. The command node for this use case SHOULD be "http://jabber.org/protocol/admin#get-online-users-num".

A sample protocol flow for this use case is shown below.

- - ]]> - - -

A service may allow an administrator to delete a log related to the service (e.g., a server log, a personal conversation log, or a discussion log from a multi-user chat room). The command node for this use case SHOULD be "http://jabber.org/protocol/admin#deletelog".

-

A sample protocol flow for this use case is shown below.

- - - - ]]> -

Unless an error occurs (see the Error Handling section below), the service SHOULD return the appropriate form.

- - - - Deleting a Log - Fill out this form to delete logs. - - http://jabber.org/protocol/admin - - - - - - - - - - - - - - - ]]> - - - - - http://jabber.org/protocol/admin - - - 20080610 - - - - - ]]> - - - - ]]> - - -

A service may allow an administrator to empty cached information related to a service (e.g., the history of a chat room). The command node for this use case SHOULD be "http://jabber.org/protocol/admin#emptycache".

-

A sample protocol flow for this use case is shown below.

- - - - ]]> -

Unless an error occurs (see the Error Handling section below), the service SHOULD return the appropriate form.

- - - - Emptying the Cache - Fill out this form to empty the cache. - - http://jabber.org/protocol/admin - - - - - - - - - ]]> - - - - - http://jabber.org/protocol/admin - - - someroom - - - - - ]]> - - ]]> @@ -2687,7 +2527,7 @@ The ad-hoc commands protocol is not supported. -

For the syntax of these errors, see &xmppcore;. Naturally, other errors may be returned as well (e.g., &internalserver; if the service cannot be shut down).

+

For the syntax of these errors, see &xep0086;. Naturally, other errors may be returned as well (e.g., &internalserver; if the service cannot be shut down).

The ability to complete the administrative tasks specified herein MUST NOT be granted to users who lack service-level administrative privileges.

@@ -2755,9 +2595,6 @@ -