> On Jul 10, 2017, at 3:11 PM, Kerim Aydin <ke...@u.washington.edu> wrote: > > > > On Mon, 10 Jul 2017, Alex Smith wrote: >> On Mon, 2017-07-10 at 11:42 -0700, Kerim Aydin wrote: >>> >>> [Keep in mind I meant well...] >>> >>> Default is a Switch switch tracked by the tracker of that switch >>> with possible values 'default' (default) and any rules-specified >>> default for that switch. If the rules specify a default for a >>> switch, that switch's default switch value is set to that rules- >>> specified default. Otherwise the value of the default switch of >>> that switch is 'Default'. The default value of a switch is the >>> value of its default switch. >> >> This requires each officer who tracks a switch to report an infinite >> amount of data, per the fact that switch switches apply to the switch >> switches themselves, and rule 2379. >> >> Of course, it's possible to report an infinite amount of data in a >> single message, via describing it rather than explicitly listing it, >> but needing to report on the default switches at all is a fairly >> obnoxious requirement. > > We had switch switches before (and acknowledged their infinite nature) > and we're saved in reporting by the fact that other than the top set, > they're all in default: > That officer's (weekly, if not specified > otherwise) report includes the value of each instance of that > switch whose value is not its default value;
More generally, that only a finite number of them can ever be in non-default states, as a side effect of the proscription on using summaries for impractically-large or impossibly-large sequences of actions. -o
signature.asc
Description: Message signed with OpenPGP
