Bumping this thread. If you know anyone who has stakes in pubsub but might not read this list please refer them to this thread or this PR.
Feedback is very welcome. I'm not 100% sure myself which of the three PRs is the best solution; But we have to do something. (At least merge #555 which has the lowest of all impacts) Personally I think #557 is the way to go and I would like council to vote on that next week. cheers Daniel 2017-12-12 17:44 GMT+01:00 Daniel Gultsch <dan...@gultsch.de>: > After some discussion on the XSF MUC I created a third alternative > which has the added benefit of making the language in that section a > lot clearer. > > https://github.com/xsf/xeps/pull/557 > > 2017-12-08 14:20 GMT+01:00 Daniel Gultsch <dan...@gultsch.de>: >> Hi, >> >> XEP-0048, XEP-0223 and possibly others are referencing a >> publish-option called 'persist-item'. XEP-0060 says that any >> publish-options MUST be registered. This hasn't happened yet. >> >> Here is a pull request that does: https://github.com/xsf/xeps/pull/555 >> (editors will still have to pull this into the registry) >> >> as an alternative approach we could agree that every registered >> node-configuration double acts as a publish-options PRECONDITION with >> the same name. >> >> Here is a pull request that adds such wording to XEP-0060. >> >> https://github.com/xsf/xeps/pull/556 >> >> This pull request also removes the possibility of registering >> publish-options as OVERRIDE (They would probably have to share the >> same name as the node-configuration publish-options and confuse >> people. >> >> These two PR are mutually exclusive. >> Pick your poison. PR#555 is a pretty simple and required for 0223 (or >> else the XEP wont work). PR#556 is a more fundamental change but >> arguably the 'saner' choice. >> >> cheers >> Daniel _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
