On 03.10.2017 13:43, Matthew Wild wrote:
>> On 29 Aug 2017, at 13:27, Kim Alvefur <[email protected]> wrote:
>>> On Mon, Aug 28, 2017 at 12:03:37PM +0200, Daniel Gultsch wrote:
>>>> Now that the PR regarding publish-options has been merged into
>>>> XEP-0060 I want to bump this thread and ask if anyone objects to that
>>>> proposal (making persistent-items, node-config and publish-options
>>>> mandatory). Otherwise I would go ahead and create a PR for that and
>>>> let council vote on this next Wednesday.
>>>
>>> I'm sceptical. I would rather see an even smaller mandated feature set.
>>> Preferably exactly as much as required for extended presence (user tune
>>> etc) and *nothing* else. These features you want to make mandatory ought
>>> to be in XEP-0222 or XEP-0223 instead. Or perhaps a new XEP, the
>>> full-blown-pubsub-on-your-jid XEP you always dreamed about.
> 
> I agree with that. I don't really care where the note is. Clearly PEP
> has proven a success, and it seems fine that people want to grow and
> extend that with more features so we can grow and extend XMPP.
> 
> But mandating these features in XEP-0163 is not a sensible solution.
> There are many use cases that are served quite comfortably by the
> original scope of PEP. The additional features we are talking about
> are not necessarily possible in certain environments, and there's no
> reason to make it "all or nothing". That's why we have feature
> discovery!
> 
> But again, I'm not opposed to a newly-defined PEP profile that
> requires these features. Define a new feature, put it in the
> compliance suite XEPs, etc. I'm fine with that. I think it makes
> sense, because many modern protocols are depending on them.

I also think that newly-defined PEP profile(s), which are discoverable,
are the way to go.

- Florian

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________

Reply via email to