[Standards] Proposed XMPP Extension: PubSub Namespaces

Jonas Schäfer jonas at wielicki.name
Tue Jan 11 16:33:17 UTC 2022

Hi pep., list,

On Sonntag, 9. Januar 2022 00:02:22 CET Maxime Buquet wrote:
> On 2022/01/08, Dave Cridland wrote:
> > The canonical example given was microblogging with Atom, where you don't
> > just want random Atom payloads - the node might require Atom to work, but
> > it has additional semantics around it that can be expected. IOW, the need
> > is to know it's a microblog node, and not just an Atom node. So this isn't
> > really about payload formats, it's about node semantics, and that's a
> > radically different thing. And definitely not a "namespace".
> Yes! I think you captured very well what we wanted to say! We do want
> a way to express semantics.
> “Payload” may not be the word, then we'll change it. “Namespace” annoys
> people, we're also happy to change it. Suggestions welcome for a
> field(?) name, and also another XEP name!

To join the bikeshedding, for the XEP name I'd suggest "PubSub Node Semantics 
Information" or similar. That would be descriptive and clearer than 

I concur with Dave that this should just reuse the #type field, it seems to 
fit the definition neatly enough.

kind regards,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.jabber.org/pipermail/standards/attachments/20220111/ea67d530/attachment.sig>

More information about the Standards mailing list