School of Specs Inside one plenary: TSG SA#112Overview

The meeting and its shape · chapter 2 of 7 · 5 minutes

2 This meeting in numbers

346 documents, 20 kinds, 62 senders and 689 change requests — the size and the shape of one plenary, and where two honest counts of the same thing disagree.

2.1 The size of it

A plenary is a large object, and the fastest way to get the measure of one is to count what it handled rather than to read what it said.

What How many
Documents 346 [1]
Kinds of document 20 [2]
Different sources submitting 62 [3]
Top-level agenda items 23 [4]
Individual change requests 689 [5]
Specifications changed 114 [6]
Registered 568 [7]
Checked in 365 [8]
Registered to attend online 110 [9]

Four days and 346 documents. That ratio explains most of how a plenary reads: almost nothing gets a long discussion, because almost nothing can.

The attendance numbers are worth reading as a pair rather than one at a time. 568 people registered but only 365 checked in, and checking in is the step that keeps a member company's voting rights alive.

2.2 What kind of documents they were

The 346 fall into 20 kinds. Ten of them carry almost everything, and the shape is worth memorising: a plenary is mostly corrections to existing work, plus proposals to start new work.

Kind How many What it is
CR pack 120 [10] many change requests under one document number
WID new 53 [11] a new work item description — a proposal to start work
Report 29 [12] a report brought to the meeting
Draft TR 28 [13] a draft technical report
Discussion 20 [14] a paper arguing a case, with nothing to approve
LS in 18 [15] a letter from another body — a liaison statement
CR 14 [16] a single change request, not in a pack
Other 13 [17] typed only "other"
SID new 10 [18] a new study item description — a proposal to study something
SID revised 9 [19] a study item description resubmitted under a new number

The report's own annex lists those 120 change-request packs, the biggest kind of document at this meeting [20].

2.3 Who sent them

62 different sources submitted something. The five busiest are all SA working groups, and no single company comes close to them.

Source Documents
SA WG5 66 [21]
SA WG3 57 [22]
SA WG6 41 [23]
SA WG2 33 [24]
SA WG4 28 [25]

That is the plenary's own structure showing up in the post: the groups do the work all year and arrive at the plenary carrying it.

What each group works on can be read off the specifications its change requests touch — and this record says nothing more than that about any of them:

  • SA WG5 owns TS 28.552, "5G performance measurements", and TS 28.312, "Intent driven management services" TS 28.552, TS 28.312

  • SA WG2 owns TS 23.501, the system architecture of the 5G system TS 23.501

  • SA WG6 owns TS 23.482, the architecture for the AI/ML enablement service TS 23.482

2.4 Where the same thing is counted twice

Two numbers in this data describe the change requests of this meeting, and they do not match. Both are right, because they are answers to different questions.

  • 689 comes from splitting the specification column of every change request and every pack

  • The four release counts added together come to less, and those only look inside the packs

Release Change requests inside packs
Release 20 487 [26]
Release 19 143 [27]
Release 18 36 [28]
Release 17 7 [29]

Neither is a mistake and neither should be quietly preferred. The habit worth building is to say which count you mean whenever you quote one.

2.5 Where each number came from

None of the figures on this page was typed by hand. Each one is a count made over the meeting's own files — the document list and the draft report — and each carries with it the question that produced it and the day the question was asked.

That is why the two change-request counts can both stand. They are two different questions, both recorded, rather than one question answered twice.

It is also why a number here can be checked. Click any of them and the entry behind it names the file or the database row it was read out of, so a reader who disagrees has something to disagree with.

2.6 What the numbers are not

Every figure on this page is read out of the meeting's own paperwork, and the narrative part of that paperwork — the secretary's report — is a draft that says so on its cover [30].

Two limits follow from the counting itself, and they hold however clean the final report turns out to be:

  • Size is not importance. A specification with 29 change requests against it had 29 changes proposed, and that is the whole of what the number says.

  • The senders are not a league table. 66 documents from one working group is a measure of how much paperwork that group produced for this meeting, not of how much of 5G it owns.

The next chapter takes the same 346 documents and sorts them the way the meeting itself did: by agenda item.

Where the numbers in this chapter come from

  1. 346 documents at SA#112 sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112';", read 2026-08-04
  2. 20 different kinds of document distinct values of tdoctype over the same 346 rows, read 2026-08-04
  3. 62 different sources submitted documents distinct values of source over the same 346 rows. A source is a working group or a company, and one entry may name several, read 2026-08-04
  4. 23 top-level agenda items rows of the agenda table in SP-260361_SA112_Agenda_v2.md whose item number has no dot in it, read 2026-08-04
  5. 689 individual change requests the crspec column of every CR and CR pack row of tdoc for meeting='SP-112', split on spaces and counted. Each token is one change request against one specification, read 2026-08-04
  6. 114 specifications were changed distinct tokens of the crspec column over the same CR and CR pack rows, read 2026-08-04
  7. 568 people registered for the meeting the '568 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04
  8. 365 people checked in and so kept their voting rights the '365 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04
  9. 110 people registered to attend online the '110 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04
  10. 120 documents of type 'CR pack' sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='CR pack';", read 2026-08-04
  11. 53 documents of type 'WID new' sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='WID new';", read 2026-08-04
  12. 29 documents of type 'report' sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='report';", read 2026-08-04
  13. 28 documents of type 'draft TR' sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='draft TR';", read 2026-08-04
  14. 20 documents of type 'discussion' sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='discussion';", read 2026-08-04
  15. 18 documents of type 'LS in' sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='LS in';", read 2026-08-04
  16. 14 documents of type 'CR' sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='CR';", read 2026-08-04
  17. 13 documents of type 'other' sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='other';", read 2026-08-04
  18. 10 documents of type 'SID new' sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='SID new';", read 2026-08-04
  19. 9 documents of type 'SID revised' sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and tdoctype='SID revised';", read 2026-08-04
  20. 120 change-request packs the '120 Entries' line closing the matching annex table of SP-112_Draft_Report_v005.md, read 2026-08-04
  21. 66 documents came from SA WG5 sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and source="SA WG5";", read 2026-08-04
  22. 57 documents came from SA WG3 sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and source="SA WG3";", read 2026-08-04
  23. 41 documents came from SA WG6 sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and source="SA WG6";", read 2026-08-04
  24. 33 documents came from SA WG2 sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and source="SA WG2";", read 2026-08-04
  25. 28 documents came from SA WG4 sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and source="SA WG4";", read 2026-08-04
  26. 487 change requests in packs belong to Rel-20 the crrelease field of every entry of the crsinpack list inside the line column of tdoc for meeting='SP-112', read 2026-08-04
  27. 143 change requests in packs belong to Rel-19 the crrelease field of every entry of the crsinpack list inside the line column of tdoc for meeting='SP-112', read 2026-08-04
  28. 36 change requests in packs belong to Rel-18 the crrelease field of every entry of the crsinpack list inside the line column of tdoc for meeting='SP-112', read 2026-08-04
  29. 7 change requests in packs belong to Rel-17 the crrelease field of every entry of the crsinpack list inside the line column of tdoc for meeting='SP-112', read 2026-08-04
  30. SP-112 draft meeting report, version 0.0.5

Every source this course is built on

Check yourself

Answers appear when you pick one, with where they come from.

Q2.1 How many documents were handled at SA#112?

Q2.2 Which kind of document was the most common at this meeting?

Q2.3 Of the 62 sources that submitted documents, which five sent the most?

Q2.4 This data counts the meeting's change requests two ways, and the two totals differ. Which is wrong?

Q2.5 How many specifications did this meeting's change requests land on?

This chapter was built from a source register generated 2026-08-04. A fresher build of the register may hold different numbers.