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.
cheers Daniel 2017-07-13 11:51 GMT+02:00 Daniel Gultsch <[email protected]>: > Hi, > > multiple XEPs are making extended use of PEP that requires to change > the access_model. The Bookmark XEP for example requires us to change > it to whitelist and the upcoming OMEMO XEP recommends us to change it > to open. The PEP XEP is a bit vague about the access_model. While it > says a service MUST support whitelist, open and presence it doesn't > explicitly say that a service must provide node configuration (which > is it's own pubsub feature > 'http://jabber.org/protocol/pubsub#config-node') > Furthermore to handle access model modifications in any reasonable way > the PEP service will also need publish-options. > And last but not least; For some XEPs like Bookmarks it is absolutely > crucial that a PEP service will also support persistent-items. (The > avatar XEP will also benefit from this.) > > I would like to modify XEP-0163 to make it more clear that the service > MUST support persistent-items, node-config and publish-options. (And > also announce their respective features) > > This way the Compliance Suite and the compliance tester can test if a > server has a PEP implementation that is actually capable of handling > today's demands that the bookmark, avatar and omemo XEPs have. > > cheers > Daniel _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
