[Standards] Proposed XMPP Extension: PubSub Namespaces
stpeter at stpeter.im
Sat Jan 8 23:16:48 UTC 2022
On 1/8/22 4:02 PM, Maxime Buquet wrote:
> On 2022/01/08, Dave Cridland wrote:
>> On Tue, 4 Jan 2022 at 17:55, Jonas Schäfer <jonas at wielicki.name> wrote:
>>> The XMPP Extensions Editor has received a proposal for a new XEP.
>>> Title: PubSub Namespaces
>>> This extension defines a new PubSub node attribute to specify the type
>>> of payload.
>> Oh no it doesn't!
>>> URL: https://xmpp.org/extensions/inbox/pubsub-ns.html
>> What this extension appears to be trying to do, based on the (entirely
>> unreferenced and unmentioned on this list) Github discussion, is to define
>> the pubsub node *semantics*. That's a different thing to a namespace, and
>> certainly different from the "type of payload".
> Indeed, this is based off a PR that I made a while back on 277, that
> got somewhat-rejected-but-not-really by one of its authors (stpeter). I
> got asked to go to standards but I thought that would get no interest as
> pubsub stuff usually does and we would redo the same discussion just the
> two of us. So I gave up, until this.
>> 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.
Yes, that's what I was trying to say in the GitHub thread.
More information about the Standards