[Standards] RFC: Make projects publish a DOAP file to get listed at xmpp.org

Emmanuel Gil Peyrot linkmauve at linkmauve.fr
Mon Aug 21 04:08:32 UTC 2017


For quite a long time I’ve been trying to design a format that would
describe XMPP software, while being useful to most (all?) consumers of
this document, be it simple client listings like at xmpp.org, wikis
about projects wanting to stay up to date, feature matrices comparing
multiple implementations, or even authors who’d like to know who
implemented their specifications.

Attached are an example of an XMPP software (poezio, a client), and of
a consumer (xmpp.org, a simple website).

The format itself still has a lot of TODOs, most of which have been
reported to the DOAP project[1], while the XMPP specific parts still
lack a schema entirely.

The consumer Python script parses the file quite defensively, and then
generates the HTML you could have seen on xmpp.org (for the clients
page[1] and for a XEP page[2]).  The XEP page would require some
changes to the way XEPs are processed, since it generates the change
log itself, inserting implementations there.  Another way would be to
generate JavaScript code that would insert the DOM nodes at runtime.

There is also still the issue of having a place where all of these DOAP
URIs would be linked from, I think xmpp.org could act as such even for
projects unlisted from the main pages, but this remains to be decided.

Please tell me whether you think it is a good idea, whether you would
integrate it with your website/wiki/feature matrix/other, and any
improvement you could think of!


[1] https://github.com/ewilderj/doap/issues
[2] https://xmpp.org/software/clients.html
[3] https://xmpp.org/extensions/xep-0380.html

Emmanuel Gil Peyrot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: poezio.xml
Type: application/xml
Size: 12313 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20170821/29dc8a58/attachment.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: parser.py
Type: text/x-python
Size: 7867 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20170821/29dc8a58/attachment.py>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20170821/29dc8a58/attachment.sig>

More information about the Standards mailing list