Expand description
Neutral, format-agnostic structural schema model — the hub every schema format (protobuf, ODCS, JSON Schema, Avro, …) converts to and from, so N formats cost N adapters rather than N². This carries shape (named objects, their fields, cardinality, leaf types, cross-object references); quality rules and precedence/merge remain the resolved-spec concern of the rest of this crate.
A SchemaModel is a flat set of SchemaObjects that reference one another
by fully-qualified name (an object-typed field carries the target’s name),
which is how a multi-package/multi-message source maps onto a multi-object
contract without inlining or losing structure.
Structs§
- Field
- One field of a
SchemaObject. - Schema
Model - A complete set of schema objects that may reference each other by name.
- Schema
Object - One named record/message type.
Enums§
- Cardinality
- How many values a field holds.
- Logical
Type - A leaf (scalar or reference) type, format-neutral but precise enough to reconstruct a source type (width/signedness preserved).