Define deterministic representation of non-string daw_i18n/v1 parameter values #9

Open
opened 2026-08-14 15:57:11 +02:00 by michael · 0 comments
Owner

Problem

#8 deliberately excludes deterministic representation of
non-string parameter values used in daw_i18n/v1 placeholder
materialization.

config_parser.lua shows this is a real case, not theoretical:
data.line is numeric (17), while path, section_type,
section, key are strings. Two independent resolvers
materializing the same daw_error/v1.data could produce different
visible text for the same numeric or boolean value if formatting
is left to implementation convention.

Scope

Define, for daw_i18n/v1 placeholder materialization, a
deterministic language-/binding-neutral representation for
non-string parameter values (at minimum: integers, floats,
booleans). Out of scope: locale-specific number formatting
(thousands separators, decimal comma vs point) -- that remains a
presentation/rendering concern, not an interchange concern.

Acceptance criteria

  • The contracts define a deterministic canonical string
    representation for non-string parameter values used in
    placeholder materialization.
  • The representation is binding-neutral (does not assume Lua
    semantics).
  • Locale-specific formatting is explicitly excluded from this
    representation and named as a presentation-layer concern.
  • At least one normative example covers a numeric parameter
    (e.g. line number).
## Problem #8 deliberately excludes deterministic representation of non-string parameter values used in daw_i18n/v1 placeholder materialization. config_parser.lua shows this is a real case, not theoretical: `data.line` is numeric (17), while `path`, `section_type`, `section`, `key` are strings. Two independent resolvers materializing the same daw_error/v1.data could produce different visible text for the same numeric or boolean value if formatting is left to implementation convention. ## Scope Define, for daw_i18n/v1 placeholder materialization, a deterministic language-/binding-neutral representation for non-string parameter values (at minimum: integers, floats, booleans). Out of scope: locale-specific number formatting (thousands separators, decimal comma vs point) -- that remains a presentation/rendering concern, not an interchange concern. ## Acceptance criteria - [ ] The contracts define a deterministic canonical string representation for non-string parameter values used in placeholder materialization. - [ ] The representation is binding-neutral (does not assume Lua semantics). - [ ] Locale-specific formatting is explicitly excluded from this representation and named as a presentation-layer concern. - [ ] At least one normative example covers a numeric parameter (e.g. line number). ## Related - DAW/daw-contracts#8
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
DAW/daw-contracts#9
No description provided.