On Wed, 15 Dec 2021 at 16:14, Florian Schmaus <f...@geekplace.eu> wrote:
> On 15/12/2021 15.41, Dave Cridland wrote: > > For the benefit of others wanting context, this is XEP-0060 section > > 8.2.4. The existing SHOULD in this section is probably wrong, in as much > > as it's either meaningless (to configure a node, obviously you send the > > form) or else egregious (if you pull the form and the node seems to be > > set right, why reconfigure it?). > > +1 > > > On Wed, 15 Dec 2021 at 04:38, Travis Burtrum <tra...@burtrum.org > > <mailto:tra...@burtrum.org>> wrote: > > > > > The submitted configuration form MAY contain a subset of possible > > configuration options. In that case, the service MUST only change the > > submitted configuration options. > > > > > > I don't think that text expresses what is actually intended. I think > > what you want to say is that if a client doesn't provide all the > > options, the server fills in the "missing" values from the configuration > > form defaults, and not global defaults or something. > > No, I think this is not why the motivation and intention behind the > proposed change is. "Filling unspecified values with the configuration > form defaults" does not sound sensible, assuming that it means > unspecified values could potentially be reset to their initial default > values if they have been modified afterwards. By "the configuration form defaults", I mean the defaults in the configuration form from 8.2.2, which "SHOULD" be the current node configuration values, and not any kind of global defaults. So I think you're agreeing with me, aren't you? Dave.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
