School of Specs How standards actually get madeIn depth

TR 21.900 v20.0.0 · How standards actually get made

The whole document

97 clauses in the order they appear. The bar shows how much text each part holds. Open one to see what is inside it and which chapter teaches it.

Words · Every version · Documents around it

Foreword Foreword 128 words · taught in Reading a 3GPP number — the series, the version, the file name Introduction Introduction 165 words · taught in Why anybody writes a standard down 1 Scope 113 words · taught in Why anybody writes a standard down 1A References 178 words · taught in Why anybody writes a standard down 2 Definitions and abbreviations 493 words · taught in The shape of 3GPP, and what the record does not say about it, Why the documents read the way they do
3 General responsibilities of the Support Team 167 words · 3 of 3 clauses taught
4 Handling of Specifications 6,998 words · 39 of 40 clauses taught
5 Availability and distribution of specifications 264 words · 2 of 3 clauses taught
5A File naming conventions 763 words · taught in Reading a 3GPP number — the series, the version, the file name, Reading either body's paper trail from a cold start 5B Availability and distribution of OpenAPI specification files 481 words · taught in The two cultures, side by side and on the evidence 5C Normative availability and distribution of stage 3 specification files 187 words
6 Work Items 4,595 words · 21 of 22 clauses taught
7 Management documents and tools 229 words · 9 of 9 clauses taught
8 Email decisions 529 words · 8 of 8 clauses taught
9 Meeting contribution document types and status values 1,371 words · 3 of 3 clauses taught
Annex A Change history 904 words · taught in Reading either body's paper trail from a cold start