XMPP Extension Protocol (XEP)

IndustryXEP

Description

XMPP Extension Protocols published by the XSF. Each XEP extends the core XMPP specifications with a specific feature (multi-user chat, publish-subscribe, file transfer, signaling, etc.). The number is zero-padded to 4 digits. XEPs progress through a maturity lifecycle: Experimental (work-in-progress) → Proposed (under review) → Draft (stable, widely implemented) → Final (mature, no further changes). Retired XEPs are marked Deprecated and eventually Obsolete.

Syntax

XSF identifiers use a single document type: XEP (XMPP Extension Protocol). The identifier is 'XEP-<number>' where the number is zero-padded to 4 digits ('XEP-0001', not 'XEP-1'). The XSF never prints its publisher name in the identifier — the leading token is always 'XEP'.

Examples 5

XEP-0001

XEP-0045

XEP-0060

XEP-0166

XEP-0352

Components Used

XSF XMPP Extension Protocol (XEP) identifiers are composed of these elements:

Type

Always 'XEP' — the XSF never prints its publisher name in the identifier

e.g.XEP

Number

XEP number, zero-padded to 4 digits ('0001', not 1). Kept as a string to preserve padding.

e.g.0045

:number

Algebraic Relations

Relations that can involve XMPP Extension Protocol (XEP) identifiers:

Relation	Description	Syntax	Example
XEP Reference	Canonical form: 'XEP-' + 4-digit zero-padded number	`XEP-<number>`	`XEP-0045`
Maturity Stage	XEPs carry maturity metadata (Experimental, Proposed, Draft, Final, Deprecated, Obsolete) outside the identifier	`XEP-<number> [<stage>]`	`XEP-0045 [Draft]`

URN Mapping

Patternurn:xsf:xep:[number]