Mark Nottingham

- [ ] cache may store incomplete 200, serve 206 from it - [ ] cache must not store incomplete if it doesn't support Range/Content-Range - [ ] cache must...

@domenic if another community (like people doing serverless) is able to achieve what they want as separate extension specs, that makes total sense. Of course that means that specs need...

@othermaciej that makes sense. It seems like this is going to drive non-browser folks to decide to adopt a WHATWG API only if it's *very* close to what they need...

yeah, user agent != browser implementation. There's one user (well, there are potentially billions, but this is our anchor) and they can have many different agents at the same time....

If you're going to expand the size of the TAG, it should be explicitly re-fashioned as a review board (e.g., "Specification Review and Coordination Directorate") and NOT be able to...

The dynamics of a large board are well-known to be different -- including an increased tendency towards compromise. Combined with a pool of candidates that may not be very deep...

@michaelchampion correct, apologies for the ambiguity. @cwilso I found some pretty easily, e.g., Shijun Cheng, "Board size and the variability of corporate performance" [2008] 87(1) _Journal of Financial Times_. The...

> We have decades of actual experience where people formally object. Web stakeholders may formally object to Working Group decisions about what goes into a spec. AC reps may formally...

> We'll need to ensure in other ways that objections to chair appointments are always done professionally. Very much agreed - I think the W3C is already on the right...

Whether or not we define CGs/BGs in this process, we need to reconsider them urgently. People now regularly confuse them with the standards-setting activities of the W3C, and may not...