All Classes and Interfaces
Class
Description
Explains why a single field was inferred as
any rather than a specific
scalar kind, part of InferResult.Implements every
omnist CLI command: format, validate,
convert, schema (with its normalize/prune/extract/
compatible-with/equivalent/is-empty/lint subcommands),
and infer.Process entry point.
Represents a date and time of day, joined, with optional UTC offset (omnist-spec §2.2.1).
Root interface representing an Omnist Document (omnist-spec §2.2).
An edge in the Document model, consisting of a label and a target (omnist-spec §2.2).
An immutable field declaration within a
Record definition (omnist-spec §5.4).Conformance test harness entry point for the omnist-spec conformance suite.
The result of
SchemaAlgebra.inferWithReport(List, String, boolean): the
inferred schema plus a report of every field that fell back to any.Codec for reading and writing the Omnist Document model as JSON (omnist-spec §7.3).
Safety limits bounding Document nesting depth, node count, and integer literal digits (omnist-spec §2.4).
One structural diagnostic returned by SchemaAlgebra.lint(S) (§6.11).
Schema-driven coercion of a parsed
Document into a fully-typed document (omnist-spec §8).A node in the Document model, consisting of an ordered list of labeled edges (omnist-spec §2.1/§2.2).
Normative OML Tokenizer (omnist-spec §4.2).
An individual token produced by
OmlLexer.Token types produced by the OML lexer (omnist-spec §4.2).
Structured exception thrown when an OML document fails to parse (omnist-spec §8).
OML (Omnist Markup Language) Core Reader (omnist-spec §4).
OML (Omnist Markup Language) Canonical Writer (omnist-spec §4 and §9.5).
Tokenizer for OSD (Omnist Schema Definition) grammar (omnist-spec §5.3).
An individual token produced by
OsdLexer.Token types produced by the OSD lexer (omnist-spec §5.3).
Thrown when OSD (Omnist Schema Definition) text fails to parse (omnist-spec §5).
OSD (Omnist Schema Definition) Reader (omnist-spec §5).
OSD (Omnist Schema Definition) Canonical Writer (omnist-spec §5.9).
An immutable record definition in the OSD schema model (omnist-spec §5.5).
Represents a scalar value in the Omnist Document model (omnist-spec §2.2.1).
A scalar holding a boolean value (omnist-spec §2.2.1, type
boolean).A scalar holding a calendar date without a time component (omnist-spec §2.2.1, type
date).A scalar holding a date-time with an optional UTC offset (omnist-spec §2.2.1, type
datetime).A scalar holding an arbitrary-precision integer value (omnist-spec §2.2.1, type
integer).A scalar holding an IEEE-754 64-bit floating-point number (omnist-spec §2.2.1, type
number).A scalar holding a Unicode text value (omnist-spec §2.2.1, type
string).A scalar holding a time-of-day with an optional UTC offset (omnist-spec §2.2.1, type
time).The seven scalar kinds defined by omnist-spec §2.2.1.
The seven scalar type keywords a field can name in OSD (omnist-spec §5,
§3.3).
A parsed OSD schema (omnist-spec §5, §3): a root record name plus the graph of
named records it (transitively) reaches.
Normative Schema Algebra operations (§6 of 06-schema-algebra.md).
A target is either a value or a node (omnist-spec §2.2).
Represents a time of day with optional UTC offset (omnist-spec §2.2.1).
Codec for reading and writing the Omnist Document model as TOML (omnist-spec §7.3),
built on the
tomlj parser.Track 1 of the conformance harness: runs the compiled
omnist CLI as a real
subprocess against the fixture-based test suite (omnist-spec §8.5) and compares its
stdout/stderr/exit-code against each fixture's expected result.Track 2 of the conformance harness: runs the omnist-spec's JSON-vector test suite
(omnist-spec §8.5) directly in-process against this port's public API (no CLI
subprocess), dispatching each vector's operation and comparing the result or
diagnostics against the vector's expected outcome.
The three field-type forms an OSD schema field can declare (omnist-spec §5.3, §3.3):
a scalar kind, a reference to another record, or the open
any type.The open
any type: accepts any value unchecked (omnist-spec §5.3.3).A field typed as a reference to another record in the same schema (omnist-spec §5.3.2).
A field typed as one of the seven scalar kinds, optionally nullable.
Diagnostic emitted when validation fails against an OSD Schema (§8.2, §8.3.4).
Structured outcome of validating a Document against a Schema (§3.6).
OSD Schema Validator (omnist-spec §3.6, §3.6.1, §8.3.4).
Represents a value in the Document model (omnist-spec §2.2).
Represents the null value in the Document model (omnist-spec §2.2.1).
A single format-specific adjustment a codec's writer made to represent a document
in a target format that cannot express it exactly, part of a
WriteReport
(omnist-spec §8.3.8's format.* diagnostic family — e.g. a dropped null,
or a temporal value stringified because the format has no native temporal type).Thrown by a codec's
write/check path when a document cannot be
written to the target format at all (e.g.Accumulates the
format.* adjustments (omnist-spec §8.3.8) a codec's writer
made while serializing a document that couldn't be represented exactly in the
target format.Codec for reading and writing the Omnist Document model as XML (omnist-spec §7.3),
built on
javax.xml.parsers/DOM.Codec for reading and writing the Omnist Document model as YAML (omnist-spec §7.3),
built on SnakeYAML.