# Standards Governance Benefits From Categorical Precision Over Comprehensive Definition Brian Kardell's move in "Fine. What Is the Web?" is to refuse the totalizing definition and pick the useful one instead. Rather than litigate what "the web" *is* in full, he argues the load-bearing category is **"the Web Platform" = what lives inside a web engine** — and that the genuinely different things (ActivityPub, JSON-LD, XML) deserve their own category ("an Embedded Web") rather than being force-fit into one definition or excluded from relevance. The governance payoff is concrete: categories, not a grand definition, decide "what belongs as a W3C Recommendation, and more broadly, what belongs at the W3C at all." Precision about *kinds* does the prioritization that a comprehensive definition can't. The reason browser tech forms its own category is that it **carries unique obligations** — privacy, security, internationalization, accessibility — and runs on nearly every device. Those obligations, not the technology's web-ness, are what justify a special standards bar. Things adjacent-but-different ("totally relevant, and totally the web") are better served by a category scoped to their actual concerns than by membership in an over-broad set that imports obligations they don't share. ## Why This Matters For **open-source and standards governance**, this is a reusable governance instinct: when a boundary fight stalls ("is X really part of Y?"), the productive move is to *split the category*, not win the definition. It connects to [[3. Resources/Permanent Notes/The Maker-Taker Frame Confuses Two Different Scarcities]] — both notes diagnose a governance error rooted in a too-coarse category, and both resolve it by distinguishing kinds that were wrongly merged. For **commons design**, it pairs with [[3. Resources/Permanent Notes/Permissive Licenses Define a Floor But Don't Constitute a Community]]: a license (or a definition) sets a minimal boundary but doesn't capture the differentiated obligations that actually govern behavior. Categories scoped to obligations carry the governance weight that broad definitions can't. ## Counterpoints to Hold - **Categories can ossify and gatekeep.** "That's not the Web Platform" can become an exclusion that starves a legitimately web-adjacent technology of standards attention. - **Boundary-drawing is itself political.** Who decides the categories inherits the power the definition fight was really about; precision relocates the contest, it doesn't end it. - **Over-splitting fragments.** Too many categories reproduce the coordination problem a shared standard was meant to solve. <!-- atomicity: 1 idea ✓ --> ## Links - [[3. Resources/Literature Notes/Lit · What is the Web Platform — categorical precision]] — the Web Platform case grounds the claim that categories assign governance obligations - [[3. Resources/Permanent Notes/The Maker-Taker Frame Confuses Two Different Scarcities]] — same shape: a governance error from a too-coarse category, fixed by distinguishing kinds - [[3. Resources/Permanent Notes/Permissive Licenses Define a Floor But Don't Constitute a Community]] — a boundary that's minimal-but-real; obligations live above the floor - [[3. Resources/Permanent Notes/Parallel Cross-Camp Accusations Often Encode a Vocabulary Mismatch Not a Real Disagreement]] — applies-in: categorical precision tests whether a heated dispute is a real conflict or two vocabularies partitioning the same practice differently ## Open Questions - What's the test for "deserves its own category" vs. "is a sub-case" — obligations carried? device reach? something else? - Who legitimately draws standards categories, and how is that power held accountable? ## Source - [[3. Resources/Readwise/Articles/Fine. What Is the Web|Fine. What Is the Web?]] — "Web Platform" = inside a web engine; Embedded Web for adjacent tech; categories decide W3C Recommendation scope; browser tech carries unique privacy/security/i18n/a11y obligations - See also: [[Open Source Governance MOC]], [[Commons & Community Governance MOC]]