Go to main content

Why Open Data is Crucial for Analyzing Standards Development Participation

Quick Nav

  • Can Researchers See Who Takes Part If the Record Stays Closed?
  • Which Participation Fields Standards Bodies Actually Release
  • Where Missing Fields Bend Claims About Civil Society
  • The Minimum Record a Cross-Body Comparison Needs
  • A Public Standard Is Not a Public Participant List
  • Citations

Can Researchers See Who Takes Part If the Record Stays Closed?

Can participation in standards development be analysed, including whether civil society was present, if the underlying records are not open? It cannot.

Three conditions decide whether that claim is testable, and they have to be met in order. The standards body publishes participant-level records. Those records carry stakeholder role over time. The fields can be compared across bodies.

A constitution can look, at first glance, like a census. A process document can look like a roll. The expectation going into the re-reading was that those instruments would at least show whether civil society could have been in the room.

The check treated them as publication architectures, not attendance censuses. Two texts were set side by side in the 2023 research year: the Constitution of the International Telecommunication Union (1992), and the Internet Engineering Task Force document The Internet Standards Process, Revision 3 (1996). No attendee count was attached to either date. The 1992 constitution organises membership in national and organisational terms. The 1996 process text sets out how Internet Engineering Task Force standards work proceeds, with working documents and much of the discussion oriented toward a public archive. Both are genuine accounts of how a body says it governs. A participation claim does not become testable merely because those texts exist.

Walk the three conditions the way a coder would. First, is there a participant-level record published by the body itself? Second, does that record carry a stakeholder role that can be read at more than one date? Third, can those fields sit next to another body's fields without a private codebook? Internet Engineering Task Force working groups, Internet Research Task Force research groups, and Internet Architecture Board discussions become one comparison only when that third condition is met. Until then they remain neighbouring conversations.

That is where the check held. The instruments explain organisation. An open participant record would make presence researchable. Drafting power, and informal influence that never entered the formal record, would still lie outside that record. Where any of the three conditions is missing, the re-reading stops, and the claim about who shaped the standard stays impressionistic.

Role Before Rhetoric

Commentary on multistakeholderism does not substitute for a record. Without those three conditions, policy analysis of who shaped a standard stays impressionistic.

Which Participation Fields Standards Bodies Actually Release

Start with what a non-member can actually retrieve. The patterns below are release designs. They are not headcounts.

Three publication patterns turned up when standards participation was studied by retrieval, not by reputation.

What a Non-Member Can Retrieve

  • Public-archive pattern. Working documents and much of the discussion are visible to non-members. The 1996 Internet Engineering Task Force process text is the case used here. A non-member can often read the draft and a substantial part of the argument around it. Visibility is a property of the publication design.
  • Member-mediated pattern. Technical work is channelled through national or organisational members, and individual names are rarely released as data. The 1992 constitutional membership architecture of the International Telecommunication Union is the contrast. The member on the public face of the body is a state or an organisation. The person in the meeting does not automatically become a released field.
  • Category-only pattern. A membership class is published. The class sorts members. It is silent on who spoke, who filed a comment, and who held the liaison seat in that same working group. Ask the class to carry those three facts and it breaks: the column was never built to hold them.

Image showing release patterns

Read across the three and the same holes appear together. No stable person identifier across meetings. No dated affiliation. No stakeholder role coded so civil society can be distinguished from industry, government, or academia. No link between attendance and a contribution. Fill one hole and the comparison still breaks on the next.

I kept meeting the same bind in the 2023 research year, re-reading venues against that 1992 to 1996 instrument span. Finished standards were there to be cited. Who was recorded as present could not be lined up across venues and years. No body count was calculated, no sample size, no share of missing fields. The constraint was qualitative, and it was binding.

Where Missing Fields Bend Claims About Civil Society

Earlier work left the person-level question unsettled. A reader in the 2023 research year can sit decades from the meeting: constitutional classes fixed in 1992, process rules revised in 1996, and governance commentary such as Laura DeNardis's The Global War for Internet Governance (2014) already on the shelf. The dated attendance row for that meeting is still absent.

What this reading does instead is keep three layers apart that closed data collapses into one story.

Being in the room is presence. Being labelled a stakeholder is a role code. Leaving a trace on a draft is a comment, a drafting mark, or a liaison. Each layer can be occupied while the others stay empty. A liaison seat can exist without a sustained run of meetings. A single comment can exist without a constituency behind it. Presence can exist with no mark on the draft at all.

Visible Names Mislead

Analysts treat whoever is visible as whoever participated. A public comment list over-represents people allowed to post. A members-only room under-represents them. Civil society is especially exposed to that swing. Affiliation arrives as an employer-based label, a self-declared label, or a blank, and any of those three blocks a clean civil-society coding. An employer string can hide a civil-society role or suggest one that the person never claimed. A self-declared label moves with the form. A blank field removes the person from the stakeholder table entirely.

The policy consequence needs no percentage. From the published standard alone, a government or a civil-society organisation cannot be told whether multistakeholder participation was broad, token, or simply unrecorded. Where a dataset should have been, the analysis borrows anecdote.

One boundary belongs in the method, so it is not mistaken for a finding. Fieldwork for the ESRC-funded study of multistakeholder participation, confined to participant fields a standards body had already released and re-read through the 2023 research year, stays inside those released fields. Chair discretion and pre-tabling work that never entered the formal record sit past that boundary. The reading can describe a gap in the archive. Rebuilding the closed room would be a different project.

The Minimum Record a Cross-Body Comparison Needs

If civil-society participation is to be compared rather than narrated, the open dataset has to hold a minimum set of fields. Walk a release in this order, and stop at the first field that is missing.

  1. Venue and working-group identifier. Name the body and the group: an Internet Engineering Task Force working group, an Internet Research Task Force research group, an Internet Architecture Board discussion, or a Telecommunications Industry Association committee.
  2. Meeting or document date.
  3. A participant identifier that stays stable within that body.
  4. Affiliation as declared on that date.
  5. Stakeholder role as declared, held as its own field beside the employer string.
  6. A contribution pointer, meaning a comment, a draft, or a liaison, kept distinct from mere attendance.

A Role Vocabulary That Travels

The same person moving between bodies can be followed only when each release carries a documented role vocabulary. Harmonised categories matter more than a larger dump of unstructured PDFs. Follow one participant on meeting dates twelve months apart and the vocabulary has to travel with every file. An undated membership class cannot carry that comparison.

Name handling belongs in the publication design. Dated role counts, aggregated, are the research-grade default. Personal names stay in the open dataset only where that body already treats participation as public, as in an open archive of the kind described in the 1996 Internet Engineering Task Force process text.

Three-Layer Read

Read any release by asking which of the three layers it actually contains: presence, role label, contribution. Refuse to collapse a missing layer into influence.

A Public Standard Is Not a Public Participant List

Return to the opening test with the minimum fields in hand. Once those fields exist and can be compared, three things become checkable: presence, continuity across meeting or document dates, and stakeholder mix as declared.

Drafting power stays outside the columns. So does influence that never entered the formal record. A spreadsheet of dated roles leaves both unread.

For a policy reader the change is concrete. The sentence that civil society was at the table becomes a claim about a dated role in a named venue. That claim can be checked, revised, or dropped.

In the 2023 research year a finished standard can already circulate worldwide while attendance, liaison seats, and civil-society affiliation for work governed by the 1992 constitutional classes or the 1996 process rules remain inside a members-only archive, so publication of the text is not evidence of who took part.

Responses

Nothing here yet. Add your opinion.

Your Comment

Subscribe to Updates

Regular updates delivered.

We respect your data privacy.