Problem
The current format is a custom markdown-like text structure. Every consumer
that wants to parse blueprint.txt programmatically has to write their own
parser — and they will all get it slightly wrong in different ways, causing
the standard to fragment across implementations.
Proposed change
Migrate the canonical format to YAML in v3.0.0. YAML is:
- Still human-writable without tooling
- Formally parseable by any language with a standard library
- Strict enough to validate against a schema
The current text format would remain valid as a "human draft" format,
with a reference parser that converts it to canonical YAML.
Source
Raised by a blueprint consumer implementation that needs to ingest
blueprint.txt programmatically to drive automated tooling.
Problem
The current format is a custom markdown-like text structure. Every consumer
that wants to parse blueprint.txt programmatically has to write their own
parser — and they will all get it slightly wrong in different ways, causing
the standard to fragment across implementations.
Proposed change
Migrate the canonical format to YAML in v3.0.0. YAML is:
The current text format would remain valid as a "human draft" format,
with a reference parser that converts it to canonical YAML.
Source
Raised by a blueprint consumer implementation that needs to ingest
blueprint.txt programmatically to drive automated tooling.