Accept inbox/doap-usage-in-xmpp.xml as XEP-0453

Jonas Schäfer 2021-01-26 16:48:37 +01:00
parent c1bffb2104
commit e3f28140ae
2 changed files with 226 additions and 0 deletions

xep-0453.xml Normal file
View File

@ -0,0 +1,225 @@
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM 'xep.ent'>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<title>DOAP usage in XMPP</title>
<abstract>This specification defines how XMPP projects can provide a machine-readable description of their abilities, and how external entities can interact with it.</abstract>
<firstname>Emmanuel Gil</firstname>
<initials>XEP Editor (jsc)</initials>
<remark>Accepted by vote of Council on 2021-01-13.</remark>
<remark><p>First draft.</p></remark>
<section1 topic='Introduction' anchor='intro'>
<p>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.</p>
<p>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.</p>
<p>The information listed SHOULD include, but isnt 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 <link url=''></link>.</p>
<p>A central point should be defined to gather the list of implementations publishing their information, this specifications proposes <link url=''></link> for this purpose.</p>
<section1 topic='Requirements' anchor='reqs'>
<p>Creating, publishing and maintaining a project description should be as easy as possible for producers.</p>
<p>Fetching, parsing and using a project description should be as easy as possible for consumers.</p>
<p>These two requirements have oriented the choice of technologies towards being as restrictive as possible:</p>
<li>The chosen RDF serialisation format MUST be RDF/XML, assuming XMPP project authors are already familiar with XML as a serialisation format.</li>
<li>The resulting file should be published over HTTPS, without access restrictions.</li>
<section1 topic='Glossary' anchor='glossary'>
<dd>Description of a Project, the chosen RDF format used by this specification to describe the various properties of a project.</dd>
<dd>Resource Description Framework, a generic data model framework, supporting many serialisation formats and conversions between them. For the purpose of this specification we will only consider RDF/XML, an XML serialisation format, with the rationale that all XMPP authors are already familiar with this serialisation format.</dd>
<section1 topic='Use Cases' anchor='usecases'>
<p>A user might want to know which compliance suite level a given client supports before choosing it.</p>
<p>A sysadmin might want to know which compliance suite level a given server supports before choosing it.</p>
<p>An XMPP service might want to propose clients based on their advertised support of what they consider a modern client.</p>
<p>A specification author might want to know the list of projects implementing this specification, their support level and version.</p>
<p>An XMPP enthousiast website might want to automatically update their XMPP comparison page with up to date information.</p>
<section2 topic='Examples' anchor='examples'>
<p>This specification wont list every property one could add to their DOAP file, that is the role of the <link url=''>DOAP specification</link>, so it will start with examples.</p>
<p>Here is a minimal DOAP file, containing the same data as the <link url=''>XMPP Software Listing</link>:</p>
<example caption='A Minimal DOAP File'><![CDATA[
<?xml version='1.0' encoding='UTF-8'?>
<rdf:RDF xmlns:rdf=''
<Project xml:lang='en'>
<homepage rdf:resource=''/>
<p>But a lot more information can be added:</p>
<example caption='A More Featureful DOAP File'><![CDATA[
<?xml version='1.0' encoding='UTF-8'?>
<rdf:RDF xmlns:rdf=''
<shortdesc xml:lang='en'>Free console XMPP client</shortdesc>
<shortdesc xml:lang='fr'>Client XMPP libre en console</shortdesc>
<description xml:lang='en'>Free and modern console XMPP client written in Python with the ncurses library</description>
<description xml:lang='fr'>Client console XMPP libre et moderne, écrit en Python avec la bibliothèque ncurses</description>
<homepage rdf:resource=''/>
<schema:documentation rdf:resource=''/>
<download-page rdf:resource=''/>
<bug-database rdf:resource=''/>
<developer-forum rdf:resource=''/>
<support-forum rdf:resource=''/>
<license rdf:resource=''/>
<schema:logo rdf:resource=''/>
<schema:screenshot rdf:resource=''/>
<category rdf:resource=''/>
<browse rdf:resource=''/>
<location rdf:resource=''/>
<implements rdf:resource=''/>
<implements rdf:resource=''/>
<implements rdf:resource=''/>
<implements rdf:resource=''/>
<xmpp:xep rdf:resource=''/>
<xmpp:note xml:lang='en'>The 'disco' plugin can be loaded to make manual queries.</xmpp:note>
<xmpp:note xml:lang='fr'>Le plugin 'disco' peut être chargé pour faire des requêtes manuellement.</xmpp:note>
<!-- And a lot more! -->
<file-release rdf:resource=''/>
<p>It is recommended to start from such an example and tweak it to correspond to your project.</p>
<section2 topic='Extensions Specific to XMPP' anchor='extensions'>
<p>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 isnt covered by the DOAP specification.</p>
<p>In order to support that, the <link url=''></link> namespace defines the <tt>&lt;SupportedXep/&gt;</tt> element, which sports a few properties:</p>
<td>The URL to the XEP document.</td>
<td>The support status by this project, can be 'complete', 'partial', 'planned', 'deprecated', 'removed' or 'wontfix'.</td>
<td>XEP version implemented by this software.</td>
<td>Software version this support first appeared in.</td>
<td>Any implementation note the project deems relevant.</td>
<section1 topic='Business Rules' anchor='rules'>
<p>A project SHOULD publish the information it deems relevant in the format defined in this specification.</p>
<p>A project MAY maintain this information in another serialisation (JSON-LD, Turtle…), but MUST submit it in RDF/XML serialisation.</p>
<p>Once satisfied with it, a project SHOULD submit their DOAP file to following <link url=''>this process</link>.</p>
<p> 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.</p>
<section1 topic='Internationalization Considerations' anchor='i18n'>
<p>Projects with an existing internationalization process are encouraged to use it to translate user-facing strings in the DOAP file.</p>
<section1 topic='Security Considerations' anchor='security'>
<p>This document introduces no additional security considerations above and beyond those defined in the documents on which it depends.</p>
<section1 topic='IANA Considerations' anchor='iana'>
<p>This document requires no interaction with &IANA;.</p>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<p>This document requires no interaction with the &REGISTRAR;.</p>
<section1 topic='Design Considerations' anchor='design'>
<p><link url=''></link> was also considered, given the considerable overlap in features with DOAP, but it didnt 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).</p>
<p><link url=''>AppStream</link> 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.</p>

View File

@ -1617,3 +1617,4 @@ IANA Service Location Protocol, Version 2 (SLPv2) Templates</link></span> <note>
<!ENTITY xep0450 "<span class='ref'><link url=''>Automatic Trust Management (ATM) (XEP-0450)</link></span> <note>XEP-0450: Automatic Trust Management (ATM) &lt;<link url=''></link>&gt;.</note>" >
<!ENTITY xep0451 "<span class='ref'><link url=''>Stanza Multiplexing (XEP-0451)</link></span> <note>XEP-0451: Stanza Multiplexing &lt;<link url=''></link>&gt;.</note>" >
<!ENTITY xep0452 "<span class='ref'><link url=''>MUC Mention Notifications (XEP-0452)</link></span> <note>XEP-0452: MUC Mention Notifications &lt;<link url=''></link>&gt;.</note>" >
<!ENTITY xep0453 "<span class='ref'><link url=''>DOAP usage in XMPP (XEP-0453)</link></span> <note>XEP-0453: DOAP usage in XMPP &lt;<link url=''></link>&gt;.</note>" >