Extensible Messaging and Presence Protocol (XMPP) is traditionally implemented in code, using XML stanzas transmitted over TCP/IP. However, such implementations lack artistic flair and are poorly suited for environments with no network connectivity but ample interpretive energy.
This XEP defines how to implement XMPP entirely through human movement. By encoding message, presence, and iq stanzas into gestures, jumps, and rhythmic flourishes, XMPP can finally achieve its destiny as both a communication protocol and a performative art form.
An interpretive XMPP implementation MUST include:
This document expires when all participants are too exhausted to continue.
Each XMPP entity is represented by a dancer. Stanzas are represented as dance motifs. Transmission occurs when a dancer performs a motif directed toward another dancer.
<message type='chat'> - A gentle twirl followed by direct eye contact.<message type='groupchat'> - The dancer spins outward, gesturing inclusively toward all other dancers.<message type='error'> - Collapse to the floor dramatically.<message type='headline'> - A short, declarative arm thrust followed by stillness.<presence/> - A calm, open posture, hands at sides.<show>away</show> - Slow backward steps.<show>dnd</show> - Crossed arms with stern gaze.<show>xa</show> - Exit the dance floor entirely.<status> - text may be mouthed silently or whispered to nearby participants.IQ ("Inquisitive Questioning") exchanges are structured duets:
<auth/> by extending both hands in supplication.<success/> by raising one arm triumphantly.<message/> exchange sequence until network fatigue sets in.Note: The dance steps illustrated in the example session are non-normative and provided for demonstrative purposes only. Implementers MUST NOT assume that pirouettes, leaps, or interpretive hand-flutters described herein correspond to any formally defined XMPP stanzas, nor that they are executable by untrained engineers. The XSF recognizes that different implementations MAY employ alternative gestures, including but not limited to jazz hands, body rolls, or small interpretive shrugs. Such variations are considered interoperable provided all participants agree on tempo and dramatic intent.
All communication occurs via line-of-sight. Dancers MUST NOT rely on TCP/IP, though rhythmic clapping MAY be used as an unreliable transport layer for synchronization.
Gestures SHOULD be culturally sensitive. For example, <presence type='subscribe'/> should not involve invasive proximity in cultures where personal space is highly valued.
End-to-end encryption MAY be achieved by performing in total darkness.
TLS handshakes can be mimed by elaborate finger-interlocking rituals.
SASL negotiation involves mutual nodding until both dancers feel emotionally authenticated.
This document requires no interaction with the Internet Assigned Numbers Authority (IANA) [1]. Attempting to assign a formal IANA registry entry to gestures, pirouettes, or dramatic pauses would likely result in specification drift, spontaneous applause, or outright audience revolt. IANA involvement is therefor unnecessary, and frankly, unsafe.
Upon advancement of this document to a status of Draft, the XMPP Registrar [2] includes the following namespace in its registry of protocol namespaces (see <https://xmpp.org/registrar/namespaces.html>):
Upon advancement of this document to a status of Draft, the XMPP Registrar [2] shall add a category of 'dance' to its registry of service discovery identities, with one associated types: 'interpretive', described as "Entity capable of sending/receiving XMPP stanzas via physical movement rather than XML serialization."
The author would like to thank the XMPP Standards Foundation for maintaining a sense of humor, and every dancer who has ever debugged XML with their body.
<?xml version='1.0' encoding='UTF-8'?>
<!--
XEP-XXXX: XMPP as Interpretive Dance
XML Schema Definition (non-normative, rhythmically flexible)
-->
<!-- Root element for an interpretive stanza -->
<xs:element name='performance'>
<xs:complexType>
<xs:sequence>
<xs:element ref='dancer' maxOccurs='unbounded'/>
</xs:sequence>
<xs:attribute name='tempo' type='xs:string' default='moderato'/>
<xs:attribute name='time-signature' type='xs:string' default='4/4'/>
</xs:complexType>
</xs:element>
<!-- Definition of a dancer -->
<xs:element name='dancer'>
<xs:complexType>
<xs:sequence>
<xs:element name='move' type='movementType' maxOccurs='unbounded'/>
</xs:sequence>
<xs:attribute name='jid' type='xs:string' use='required'/>
<xs:attribute name='role' type='xs:string' default='client'/>
<xs:attribute name='attitude' type='xs:string' default='expressive'/>
</xs:complexType>
</xs:element>
<!-- Movement primitives -->
<xs:simpleType name='movementType'>
<xs:restriction base='xs:string'>
<xs:enumeration value='pirouette'/>
<xs:enumeration value='leap'/>
<xs:enumeration value='gesture'/>
<xs:enumeration value='collapse'/>
<xs:enumeration value='nod'/>
<xs:enumeration value='twirl'/>
<xs:enumeration value='dramatic-pause'/>
</xs:restriction>
</xs:simpleType>
<!-- Optional error stanza for failed synchronization -->
<xs:element name='misstep'>
<xs:complexType>
<xs:attribute name='type' type='xs:string' default='minor'/>
<xs:attribute name='severity' type='xs:integer' default='1'/>
<xs:attribute name='description' type='xs:string'/>
</xs:complexType>
</xs:element>
</xs:schema>
This document in other formats: XML PDF
This XMPP Extension Protocol is copyright © 1999 – 2024 by the XMPP Standards Foundation (XSF).
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.
## 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. ##
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.
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).
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.
The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.
The primary venue for discussion of XMPP Extension Protocols is the <standards@xmpp.org> discussion list.
Discussion on other xmpp.org discussion lists might also be appropriate; see <https://xmpp.org/community/> for a complete list.
Errata can be sent to <editor@xmpp.org>.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
1. 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/>.
2. 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/>.
Note: Older versions of this specification might be available at https://xmpp.org/extensions/attic/
@report{der kinderen2026dance,
title = {XMPP as Interpretive Dance},
author = {der Kinderen, Guus},
type = {XEP},
number = {0512},
version = {5.6.7.8},
institution = {XMPP Standards Foundation},
url = {https://xmpp.org/extensions/xep-0512.html},
date = {2026-04-01/2026-04-01},
}END