7c1a6dde73
So the canonical JSON's string form (RFC 8785: no escape for a non-ASCII character, the short escape for a tab) and TOML's unicode escapes are part of what the two implementations must agree on. Co-Authored-By: Claude Opus 5.5 <[email protected]>
32 lines
712 B
TOML
32 lines
712 B
TOML
# eq-spelling-a.toml spelled otherwise: inline tables, dotted keys, members in
|
|
# another order, literal strings, a hexadecimal and an underscored integer, comments.
|
|
lead = 'v' # the lead component
|
|
schema = "wai.pack.policy/1"
|
|
asset_id = "sp\u00e9l\u006cing\u0009id"
|
|
segmentation.lookahead_frames = 0x4
|
|
segmentation.target_ms = 3_000
|
|
|
|
[[component]]
|
|
timebase = { den = 1, num = 25 }
|
|
media = "video"
|
|
id = "v"
|
|
|
|
[[ladder]]
|
|
role = "base"
|
|
params.q_candidates = [ 12, 6, ]
|
|
params.block = 0o10
|
|
capability = "wai.video.int_motion"
|
|
component = "v"
|
|
id = "b0"
|
|
|
|
[[ladder]]
|
|
params = { q = 4 }
|
|
refines = "b0"
|
|
role = "refinement"
|
|
capability = 'wai.video.int_refine'
|
|
component = "v"
|
|
id = "r1"
|
|
|
|
[[class]]
|
|
max_layer = 1
|
|
id = "tv"
|