That's the wrong question. W3C itself is relatively tiny, and has fairly ordinary (albeit well tuned) software/server infrastructure. Reproducing the legal fram

That's the wrong question. W3C itself is relatively tiny, and has fairly ordinary (albeit well tuned) software/server infrastructure. Reproducing the legal framework would be more of a pain, but even that could probably be done. But W3C is mostly its member companies, and the're not switching, since the majority of them, including all browsers, were in favor of this. So if all existing specifications continue to reside on W3C's web site, and all new specifications continue to be produced (by member companies) in the same place, there's not meaningful forking possible. If members are disgruntled, you can fork. That's happened before when there was disagreement about what to do with HTML, and it led to the creation of the WHATWG. By and large, members this time are supportive. Not all, mind you, but all the large players.