Changelog — Fieldset Spec 1.0
Editorial — 2026-10-22 (no version change)
- The README states the meta-schema's SHA-256 and advises validators to bundle
meta-schema.jsonrather than fetch its$idat runtime; the docs site serves the file at the$idURL. No semantic change:specVersionstays1.0.0and the meta-schema is unchanged.
Rename — 2026-10-21 (no version change)
- Renamed from "Form Schema Spec 1.0" to "Fieldset Spec 1.0". The meta-schema
$idis nowhttps://beyerenrico.github.io/fieldset/spec/form-definition/1.0/meta-schema.json(washttps://localhost/spec/form-definition/1.0/meta-schema.json); the bundled template registry isurn:fieldset:bundled-templates. No semantic change:specVersionstays1.0.0,$schemaandsource.registryremain pattern-only, so definitions naming the former URIs stay valid.
1.0.0 — 2026-10-16
- Initial release: definition structure, 30 element types, JsonLogic dialect with decimal and date operators, evaluation algorithm, validation error codes, lint rules, versioning and checksum rules.
- Reserved for later features:
role(withroles.json),source,i18n, therecordtype. - Documented extension:
x-import. - Clarified (same day, before any release): round stability, incremental visibility, normalization errors, repeater
minItemson empty lists, rating/attachment/signature/location/hidden checks, JSNumber()and==array rules, variadicmin/max, operator error handling, lint path and reference rules, data-contracttimepattern. - Hardened (M1 review, before release): restricted ECMAScript pattern subset with fixed semantics and no nested quantifiers (§3.4), 4,096-code-point pattern subject limit, 60-digit decimal limit, 512-level nesting limit and
logic_too_deep, calculation order (topological, document order for ties), 254-code-point email limit, finite location numbers, explicit check order, meta-schema URI pattern instead offormat: uri, strict asset UUIDs.