Omission reading: a value built from a missing line
An omission reading establishes a value from a line that is not there. On a feature grid that is a legitimate inference, and it is the weakest evidence class this register records. As of 2026-09-22.
| The term | Omission reading |
|---|---|
| What it names | A value established by the absence of a feature line |
| What it is not | A sentence stating what a plan's output carries |
| Where the register uses it | Several free-tier values, labelled as such |
Inclusion rule. Words this site uses in a narrow sense, where the ordinary sense would lead a reader to misread a cell. No vendor statement appears on this page. Order. Fixed order: what the word names, what it excludes, then where it is used here.
1Why the inference is legitimate at all
A feature grid is built to be read by subtraction. A line against one column and not another is the document's own way of saying the second column excludes the feature, and refusing to read it that way would leave most of this register empty while the information sat in plain sight.
So omissions are recorded, and they are labelled. The label is the whole point: a reader can see which values rest on a sentence somebody wrote and which rest on the arrangement of a page, and can discount the second accordingly.
2What makes it weak
A line can vanish for reasons unconnected to a product: a narrower layout, a shorter list, a redesign that moves features into a comparison table elsewhere. None of those changes a file, and all of them change an omission reading, which is why such a value has to be redone rather than checked.
It is also the class most vulnerable to layout tricks. Two of the omission readings here come from grids whose shape inverts a naive reading, one through a glyph and one through inheritance. A sentence has no equivalent failure mode.
3What the register writes in the cell
The vendor's construction rather than the inference. A cell reads that the free plan's feature list does not include watermark-free output, which is a claim about the page, rather than free output is marked, which is a claim about files that the page does not support.
That looks fussy until a vendor changes one without the other. A grid can gain a watermark-free line for a plan whose output never carried a mark, and a mark can appear on output whose plan line never mentioned one. Recording what was read keeps both changes visible.
Nothing on this page is a vendor statement; the values it helps read are on the support table, with the page and the date each one was read from. See also the paid tier column, reading a plan table. Nearby terms: crossing point, list price, annual basis.