Registries

[frivoal]

Add process for Registries based on #168 and TPAC discussions.

---

Preview | Diff

[frivoal]

Notes:

• This includes (in two separate commits) the variant where the rules and the tables are together in one document, and the one where everything is inside the section of a REC. It does not include the variant where the rules and the tables could live in separate documents: this is more complicated to define, and there wasn't much appetite for it at TPAC.
• An explainer and/or material for /guide will also need to be developed, but this is just the process part. Let's take one thing at a time.
• This does not include the rules / guidance on where and how editors drafts should be developed. We need that too, but process-wise, it's a separate edit/issue (see What are the rules for where/how W3C publications are developed? #322)

[dwsinger]

There was a spirited discussion at TPAC that the tables should not be required even to be in /TR, let alone required to be in the same document. Were we even in the same meeting?

[fantasai]

There was a lot of confusion about that part, concerns that updating would be the same convoluted process as trying to publish a new FPWD or CR or something like that, or that machine-readable formats wouldn't be allowed, and so there was a lot of pushback at the start of the discussion portion. But once we explained that you can publish the tables in a machine-readable file associated with the publication not necessarily inline with the HTML, and that the entire process can be automated from accepting a GH pull request to posting on /TR using Echidna (which is a tooling that some groups are using already for their specs), people seemed to be on board afaict.

[wseltzer]

Comments inline to permit links to outside material.

[wseltzer]

or as a link to a document or documents published elsewhere.