[Standards] pubsub simplification
dave at cridland.net
Tue Jul 29 09:55:38 CDT 2008
On Tue Jul 29 15:18:01 2008, Peter Saint-Andre wrote:
> Ralph Meijer wrote:
>> Dave Cridland wrote:
>>> On Tue Jul 29 06:49:41 2008, Kevin Smith wrote:
>>>> On Mon, Jul 28, 2008 at 9:58 PM, Peter Saint-Andre
>>>> <stpeter at stpeter.im> wrote:
>>>> > In accordance with XMPP Council consensus, I have
>>>> provisionally separated
>>>> > all the information about pubsub collections into a new spec:
>>>> > I wonder if at the same time we might want to move the
>>>> information about
>>>> > presence integration from XEP-0060 back to XEP-0163?
>>>> I'm in favour of splitting collections, but not so much of
>>>> out presence - we spent quite a long time deciding that 163
>>>> only be a profile of 60, from what I recall.
>>> As a suggestion - and I'm only highlighting options - we could
>>> split out the fancier things into one or more new specifications,
>>> leaving XEP-0060 as a core, with extra XEPs holding additional
>>> features, and XEP-0163 binds XEP-0060 and a selection of brightly
>>> coloured coat hangers into the profile that is PEP.
>>> I'm not sure if this is a good idea, mind - it's not clear to me
>>> if this gives a net benefit or not - but it would keep XEP-0163's
>>> "profile" status.
>> I was thinking the same thing, indeed.
> Right. So not all pubsub-related features would be defined in
> XEP-0060, because certain "profiles" (the only example we have so
> far is PEP) would define new node configuration options and the
> like. The result would be that XEP-0060 defines the core (is that
> just "pub" and "sub"?) whilst other specs define things like
> collections, presence integration, filtered notifications,
> subscription options, management of subscription requests by the
> node owner and other such administrative tasks, etc. So we'd have a
> stripped-down XEP-0060 and a bunch of extensions to the pubsub core.
But, in this scenario - and I reiterate, I'm not sold on it yet
myself - XEP-0163 would remain just a profile, gathering together a
set of mandatory options and default behaviours, rather than defining
anything new itself.
Another profile would probably appear which described a different set
for "traditional pubsub".
Dave Cridland - mailto:dave at cridland.net - xmpp:dwd at dave.cridland.net
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
More information about the Standards