On 8 Dec 2017, at 13:20, Daniel Gultsch <[email protected]> wrote: > > 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.
From a ‘not breaking xep60’ point of view, could one reasonably argue that the latter is equivalent in effect to registering a whole load of publish options, which implementations must be happy with already? /K _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
