GateTrue

What each generator documents about marking its output

The marking register as a file, not a page

The whole register is published as one file. Each row is a single recorded field with the vendor page it came from and the day that page was read. As of 2026-09-12.

How one vendor sentence becomes one row in the fileA row begins as a sentence on a vendor page. It is assigned to one of the four fields, given a stable identifier, and stamped with the address it came from and the day it was read. Nothing between the page and the file adds information.A publishedsentenceOn a pricinggrid or a helppage written bythe vendor.Assigned a fieldOne of fourfieldsFree tier, paidtier, control,machine-readablemarking.Given anidentifierA stable idKept acrosscorrections, soa changed valuestaystraceable.StampedAddress anddateThe page itcame from andthe day it wasread.
Fig. 1 The identifier is what makes a correction visible later: the row keeps its name while its value changes.

The file exists because the tables on this site are readings, and a reading should be checkable without a browser. Anyone can open the file, sort it by source, and go to the vendor page behind any line they doubt.

Rows are added when a vendor's own pages state something about marking, and rewritten when those pages change. Nothing is inferred from how a product behaves, so a row that says nothing is documented means the pages are silent, not that the product does nothing.

The identifier column is stable. A row keeps its identifier when its value is corrected, which is what makes it possible to track a vendor changing a statement rather than only seeing the statement it has now.

Reuse is allowed under the licence named below, including commercially. The one thing asked in return is that the attribution travels with the data, because a figure quoted without its source and date is exactly what this file exists to avoid.

1What each column holds

The seven columns in the published file, in the order they appear. Recorded 2026-09-12.
ColumnWhat it holds
fact_idA stable handle for the row; corrections to the value leave it alone.
valueThe statement as recorded, in the wording used across every generator here.
applies_toThe field the row fills, and how the reading was taken.
source_urlThe vendor page the statement was read from.
source_nameThe vendor's own title for that page.
value_sinceThe date the statement is known to hold from.
verifiedThe day that page was last read.

Inclusion rule. Every recorded field is exported; there is no subset and no editorial selection at export time. Order. Rows follow the order facts were recorded, which groups them by generator.

The file is at /datasets/fields.csv, licensed CC BY 4.0. Attribution should name the site and the reading date, not this page.

The rest of the register: Generators, Fields, Readings, Side by side, Implementers, Questions, Findings, Source documents, Terms, Learn, and the field definitions on the protocol page.