Gathering information on many implementations has always been a chore, there exist various lists or comparisons for XMPP clients, servers and libraries, but these are often out of date, inaccurate, incomplete, or generally unmaintained.
This specification aims at solving this problem by putting the work of publishing and keeping up to date said information onto the maintainers of the software. Given many already do maintain this kind of list, the inconvenience should be minimal.
The information listed SHOULD include, but isn’t limited to, the project name, homepage, description, logo, screenshots if relevant, specifications supported (RFCs and XEPs). A full list of supported properties is described in RDF format at http://usefulinc.com/ns/doap#.
A central point should be defined to gather the list of implementations publishing their information, this specifications proposes xmpp.org for this purpose.
Creating, publishing and maintaining a project description should be as easy as possible for producers.
Fetching, parsing and using a project description should be as easy as possible for consumers.
These two requirements have oriented the choice of technologies towards being as restrictive as possible:
A user might want to know which compliance suite level a given client supports before choosing it.
A sysadmin might want to know which compliance suite level a given server supports before choosing it.
An XMPP service might want to propose clients based on their advertised support of what they consider a modern client.
A specification author might want to know the list of projects implementing this specification, their support level and version.
An XMPP enthousiast website might want to automatically update their XMPP comparison page with up to date information.
This specification won’t list every property one could add to their DOAP file, that is the role of the DOAP specification, so it will start with examples.
Here is a minimal DOAP file, containing the same data as the XMPP Software Listing:
But a lot more information can be added:
It is recommended to start from such an example and tweak it to correspond to your project.
As per the requirements, and as you may have seen in the previous example, we want to know the implementation status of each relevant XMPP specification, which isn’t covered by the DOAP specification.
In order to support that, the https://linkmauve.fr/ns/xmpp-doap# namespace defines the
<SupportedXep/> element, which sports a few properties:
|xep||The URL to the XEP document.||Required|
|status||The support status by this project, can be 'complete', 'partial', 'planned', 'deprecated', 'removed' or 'wontfix'.||Required|
|version||XEP version implemented by this software.||Optional|
|since||Software version this support first appeared in.||Optional|
|note||Any implementation note the project deems relevant.||Optional|
A project SHOULD publish the information it deems relevant in the format defined in this specification.
A project MAY maintain this information in another serialisation (JSON-LD, Turtle…), but MUST submit it in RDF/XML serialisation.
Once satisfied with it, a project SHOULD submit their DOAP file to xmpp.org following this process.
xmpp.org SHOULD cache and host the given files on the behalf of projects, so that if their website goes down for whichever reason other consumers can keep working as usual.
Projects with an existing internationalization process are encouraged to use it to translate user-facing strings in the DOAP file.
This document introduces no additional security considerations above and beyond those defined in the documents on which it depends.
This document requires no interaction with the Internet Assigned Numbers Authority (IANA) .
This document requires no interaction with the XMPP Registrar .
https://schema.org/ was also considered, given the considerable overlap in features with DOAP, but it didn’t contain many properties useful for software projects. Parts of its properties are reused in this specification, where DOAP was lacking (namely for the logo, screenshot and documentation properties).
AppStream was also considered, but it lacks the extensibility and existing tooling of RDF, while being limited to being a description for software installers instead of a generic software description.
This document in other formats: XML PDF
This XMPP Extension Protocol is copyright © 1999 – 2020 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 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 <email@example.com> discussion list.
Discussion on other xmpp.org discussion lists might also be appropriate; see <http://xmpp.org/about/discuss.shtml> for a complete list.
Errata can be sent to <firstname.lastname@example.org>.
The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".
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 http://xmpp.org/extensions/attic/