PubIDPubID

XSF

XMPP Standards Foundation

The XMPP Standards Foundation (XSF) is the foundation chartered to define and publish the open protocols of the Extensible Messaging and Presence Protocol (XMPP) — the XML-based instant-messaging and presence protocol that powers Jabber and many real-time communication systems. Founded in 2002 as the Jabber Software Foundation, the XSF publishes XMPP Extension Protocols (XEPs) that extend the core XMPP specifications (RFC 6120 and RFC 6121) with new features: multi-user chat, publish-subscribe, file transfer, voice/video signaling, and many others. XEPs follow a documented maturity process: Experimental → Proposed → Draft → Final (or Deprecated → Obsolete for retired extensions).

IndustrySyntax 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'. Website
1
Doc Types
2
Components
2
Relations
0
Stages

Document Types 1

Components 2

Structured elements that make up a XSF identifier:

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

PubID Algebra 2

Relationships between XSF identifiers:

RelationDescriptionSyntaxExample
XEP ReferenceCanonical form: 'XEP-' + 4-digit zero-padded numberXEP-<number>XEP-0045
Maturity StageXEPs carry maturity metadata (Experimental, Proposed, Draft, Final, Deprecated, Obsolete) outside the identifierXEP-<number> [<stage>]XEP-0045 [Draft]