[Standards] XEP-0072 si-pub namespace inconsistency

Georg Lukas georg at op-co.de
Thu Mar 10 09:46:33 UTC 2022


I've been looking into our legacy namespaces recently (the ones starting
with `http://jabber.org/`), with a goal to implement HTTP Redirects to
the respective XEPs (first map at https://op-co.de/tmp/namespacemap.txt)

I identified a bunch of inconsistencies in examples, for some of which
I've already opened PRs. One of the things that I'm not sure about is
XEP-0072, where two different SI-Pub namespaces are used:

Within a message element, only mentioned in the example:


<sipub xmlns='http://jabber.org/protocol/si-pub' />

And within an IQ element, mentioned in normative text and in an example:


<start xmlns='http://jabber.org/protocol/sipub' />

I assume that having two different namespaces was not a deliberate
design decision, but my question is:

Do these examples reflect the actual in-the-wild use?

Can we harmonize them / fix the examples?

At least in https://xmpp.org/extensions/xep-0137.html#example-1 and
https://xmpp.org/extensions/xep-0332.html#example-13 it looks
like <sipub xmlns='http://jabber.org/protocol/sipub' /> is actually a

Kind regards,

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20220310/372016e4/attachment.sig>

More information about the Standards mailing list