Re: [Standards] XEP-0227 update

2021-07-14 Thread Kim Alvefur

On Wed, Jul 14, 2021 at 02:13:19PM +0100, Matthew Wild wrote:

On Wed, 14 Jul 2021 at 12:12, Matthew Wild  wrote:

I think your point and Kev's are somewhat related. The current
proposal does not allow for preservation of explicit subscriptions or
affiliations. I think today's reality is that everyone is doing full
pubsub on the account JID, and it makes sense to preserve this
information as well.

If there are no objections, I'll add some text about this, and allow
for inclusion of a single  and  element,
as documented in:

 - https://xmpp.org/extensions/xep-0060.html#example-25 (subscriptions)
 - https://xmpp.org/extensions/xep-0060.html#example-27 (affiliations)

It's awkward that it's a single element rather than one per node (as
with items and configure), but there we are.


Never mind. Elsewhere in XEP-0060 I found more appropriate elements
that list subscriptions/affiliations for an individual node.

I've updated the PR, and pushed a rendered copy here:
https://matthewwild.co.uk/uploads/xep-0227.html#pep

There is a minor addition to 4.10 about non-PEP features, but most of
the new text is in 4.10.1, and I updated the example to show the new
elements.


LGTM

--
Kim "Zash" Alvefur
XSF Council


signature.asc
Description: PGP signature
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


Re: [Standards] XEP-0227 update

2021-07-14 Thread Matthew Wild
On Wed, 14 Jul 2021 at 12:12, Matthew Wild  wrote:
> I think your point and Kev's are somewhat related. The current
> proposal does not allow for preservation of explicit subscriptions or
> affiliations. I think today's reality is that everyone is doing full
> pubsub on the account JID, and it makes sense to preserve this
> information as well.
>
> If there are no objections, I'll add some text about this, and allow
> for inclusion of a single  and  element,
> as documented in:
>
>  - https://xmpp.org/extensions/xep-0060.html#example-25 (subscriptions)
>  - https://xmpp.org/extensions/xep-0060.html#example-27 (affiliations)
>
> It's awkward that it's a single element rather than one per node (as
> with items and configure), but there we are.

Never mind. Elsewhere in XEP-0060 I found more appropriate elements
that list subscriptions/affiliations for an individual node.

I've updated the PR, and pushed a rendered copy here:
https://matthewwild.co.uk/uploads/xep-0227.html#pep

There is a minor addition to 4.10 about non-PEP features, but most of
the new text is in 4.10.1, and I updated the example to show the new
elements.

Regards,
Matthew
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


Re: [Standards] XEP-0227 update

2021-07-14 Thread Matthew Wild
On Tue, 29 Jun 2021 at 13:40, Kim Alvefur  wrote:
>
> Hi,
>
> On Wed, Jun 02, 2021 at 04:59:40PM +0100, Matthew Wild wrote:
> >I've prepared an update that adds some of the missing features:
> >  - PEP nodes (configuration and items)
>
> What about explicit subscriptions and affiliations relevant? While not
> strictly required for basic PEP, there are implementations that support
> more optional (for PEP) PubSub features including support for
> subscriptions and affiliations that aren't attached to presence
> subscriptions. And with that covered by XEP-0227 then it might not be
> far from being usable for PubSub (components etc) exports as well.

I think your point and Kev's are somewhat related. The current
proposal does not allow for preservation of explicit subscriptions or
affiliations. I think today's reality is that everyone is doing full
pubsub on the account JID, and it makes sense to preserve this
information as well.

If there are no objections, I'll add some text about this, and allow
for inclusion of a single  and  element,
as documented in:

 - https://xmpp.org/extensions/xep-0060.html#example-25 (subscriptions)
 - https://xmpp.org/extensions/xep-0060.html#example-27 (affiliations)

It's awkward that it's a single element rather than one per node (as
with items and configure), but there we are.

Regards,
Matthew
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___