Overview

Overview of the parsing pipeline and the two error classes.

Turning Internet Object text into validated data happens in stages:

1. Tokenize — split the text into tokens (values, separators, structural characters).

2. Parse — assemble tokens into a document tree (header, sections, records, values).

3. Validate — check the data against the schema.

4. Load — produce the final in-memory values.

Errors fall into two classes, matching the stages that produce them:

Class	Stage	Example
Syntax error	tokenize / parse	unbalanced {, missing comma, unterminated string
Validation error	validate	wrong type, out of range, missing required field

The distinction matters because the two classes recover differently:

• Syntax errors are bounded by structure — the parser skips to the next boundary (~ or ---) and continues.

• Validation errors are bounded by the object — each record is validated on its own and may report zero, one, or many errors, without affecting other records.

In this section

• Error Model — the two classes, categories, and error conditions

• Parser Behavior & Recovery — how recovery works; processing options

• Error Accumulation — collecting many errors and partial output

See Also

• Syntax Errors

• Collection Rules