XEP-xxxx: XMPP Service Administrators

2.1 Discovery¶

In order to discover whether a XMPP Service entity has an administrators list configured an entity MUST use Service Discovery (XEP-0030) [2].

To make such discovery possible, we specify a Service Discovery Extensions (XEP-0128) [3] mechanism that a server SHOULD return in response to Service discovery information ("disco#info") requests sent to the bare domain of the server. This information MUST be scoped using a FORM_TYPE of "http://jabber.org/network/serverinfo" (as already specified in Service Discovery Extensions (XEP-0128) [3]) and data form fields registered for this purpose as defined in the XMPP Registrar Considerations section of this document.

<iq from='juliet@example.org/chamber'
    to='example.org'
    id='disco1'
    type='get'>
  <query xmlns='http://jabber.org/protocol/disco#info'/>
</iq>

<iq from='example.org'
    to='juliet@example.org/chamber'
    id='disco1'
    type='result'>
  <query xmlns='http://jabber.org/protocol/disco#info'>
    <identity category='server' type='im'/>
    <feature var='http://jabber.org/protocol/disco'/>
    <x xmlns='jabber:x:data' type='result'>
      <field var='FORM_TYPE' type='hidden'>
        <value>http://jabber.org/network/serverinfo</value>
      </field>
      <field var='administrators'>
        <value>alfred@example.org</value>
        <value>admin@example.org</value>
      </field>
    </x>
  </query>
</iq>

2.2 Service logic¶

An administrator have full administrative access on all the content managed by the Service.

A Multi-User Chat (XEP-0045) [4] Service should consider an administrator as having the same rights as an owner of all the managed rooms.

A Publish-Subscribe (XEP-0060) [5] Service should consider an administrator as having the same rights as an owner of all the managed nodes.

To prevent confusion an administrator SHOULD NOT be listed as owner of a room or a node. However the rooms and nodes SHOULD expose the same features as owners if the entity sends a Service discovery information ("disco#info"). This way the entity can adapt its interface to expose all the administration features.

2.3 Entity logic¶

When a JID declared as an administrator is shown or is having interactions in the context of the service, a connected entity SHOULD display it in a distinctive way (eg. a specific icon or color). This way the users are better aware of the moderations or interactions done by the administrators in the service.

5.1 Field Standardization¶

Field Standardization for Data Forms (XEP-0068) [8] defines a process for standardizing the fields used within Data Forms qualified by a particular namespace, and Service Discovery Extensions (XEP-0128) [3] describes how to use field standardization in the context of Service discovery. This section registers fields for server information scoped by the "http://jabber.org/network/serverinfo" FORM_TYPE.

<form_type>
  <name>http://jabber.org/network/serverinfo</name>
  <doc>XEP-0157</doc>
  <desc>
    Forms enabling the communication of administrators
    and other server information.
  </desc>
  <field
      var='administrators'
      type='list-multi'
      label='One or more JIDs listing the administrators of the service'/>
</form_type>

Copyright

This XMPP Extension Protocol is copyright © 1999 – 2024 by the XMPP Standards Foundation (XSF).

Permissions

Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.

Disclaimer of Warranty

## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. ##

Limitation of Liability

In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.

IPR Conformance

This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which can be found at <https://xmpp.org/about/xsf/ipr-policy> or obtained by writing to XMPP Standards Foundation, P.O. Box 787, Parker, CO 80134 USA).

Visual Presentation

The HTML representation (you are looking at) is maintained by the XSF. It is based on the YAML CSS Framework, which is licensed under the terms of the CC-BY-SA 2.0 license.

1. XEP-0050: Ad-Hoc Commands <https://xmpp.org/extensions/xep-0050.html>.

2. XEP-0030: Service Discovery <https://xmpp.org/extensions/xep-0030.html>.

3. XEP-0128: Service Discovery Extensions <https://xmpp.org/extensions/xep-0128.html>.

4. XEP-0045: Multi-User Chat <https://xmpp.org/extensions/xep-0045.html>.

5. XEP-0060: Publish-Subscribe <https://xmpp.org/extensions/xep-0060.html>.

6. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>.

7. The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <https://xmpp.org/registrar/>.

8. XEP-0068: Field Data Standardization for Data Forms <https://xmpp.org/extensions/xep-0068.html>.