dotReg

Readable.configuration.built.on.dotted:keys.

Format version 0.1

A full key. A shared heading. The same setting.

Write each dotted key in full, or group related settings beneath a heading. Values begin as text; your application decides how to interpret them.

@dotReg 0.1

A.Code:001
A.Message: "Hello, dotReg"
A.Group.Enabled:true

@dotReg 0.1

A.
  .Code:001
  .Message: "Hello, dotReg"
  .Group.
    .Enabled:true

Both forms resolve to A.Code, A.Message and A.Group.Enabled. Each heading level adds exactly two ASCII spaces. The code 001 keeps its leading zeroes. Every complete file starts with @dotReg 0.1 and a blank separator.

Text stays text

Keep paths, codes and literal values intact. Use an initial double quote when you want quoted syntax and escapes.

Every occurrence counts

Repeat a key to record multiple values in source order. Repeated values are retained, including identical ones.

Room for longer values

Use triple quotes for decoded multiline strings, or pipe blocks for literal text.

From a first example to the precise rules

01Learn the notationSmall examples of keys, headings, strings and repeated values.02Read the specificationCore syntax, string decoding and processing responsibilities.03Try the sample parsersChoose Go, Python, JavaScript, TypeScript, Java, C#, Rust or C++.

Format scope. The specification defines the core rules. Type profiles and candidate types describes type-specific representations and candidate names; undecided matters lists the details left open. The sample parsers demonstrate syntax processing, and the Go sample also provides an example type profile and retrieval API.

The specification, examples and sample implementations are available under the MIT License.