A YAML alternative without implicit typing

A YAML 1.1 reader turns no into false and 0777 into 511, deciding types from how a word looks. NOVA keeps YAML’s block layout and comments. A bare word is a string unless it is true, false, null or a strict number.

config.yaml what a YAML 1.1 reader sees
country: no
mode: 0777
beta: on
services:
   - id: api
false
511
true
3 spaces, still valid
config.nova what NOVA reads
country: no
mode: 0777
beta: true
services:
  - id: api
"no"
"0777"
true
exactly 2 spaces

In NOVA, three spaces of indentation are an error, not a different structure. Token classification, spec §4.4

What changes

TopicYAMLNOVASpec
Bare wordsTyped by patternStrings, except true, false, null and numbers§4.4
IndentationAny consistent amountExactly two spaces per level§4.3
Duplicate keysOften the last one winsRejected by every parser§2.10
ReuseAnchors, aliases and merge keys in the dataTemplates, rendered before anyone reads the data§9
TypesTags, resolved per parserTimestamps, decimals, rationals, sets, tuples, variants§2
ValidationExternal schema toolsBuilt-in schemas with SemVer-checked evolution§6

Migrating

Convert a file, review the loss report, then rename keys at your own pace. The converter marks the result @compat yaml so lints leave the names alone.

nvf convert config.yaml --to nova
nvf lint config.nova --fix

Merge keys (<<) and custom tags are rejected on import; move that reuse into a template. Aliases are expanded under an output budget. YAML mapping, spec §11.2

When to stay with YAML

  • Your tool only reads YAML, such as Kubernetes or a CI system. Keep YAML at that boundary and generate it with nvf convert --to yaml.
  • You need a format that is stable today. NOVA is a 0.1 draft, and minor versions must match exactly while the major version is 0.

Questions

Is NOVA a superset of YAML?

No. It looks similar, but the rules differ on purpose. Existing files convert with nvf convert, which reports anything it cannot carry over.

Does NOVA keep my comments?

Yes. Formatting and patching keep comments, blank lines and field order.

How do I write a date?

Write @timestamp("2026-11-17T16:00:00Z"), or leave it plain and let a schema field typed timestamp resolve it.