Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
YAML-only comparison of LB-1588's proposed flat
methodsstructure with PR #30, as requested. This is a schema/authoring prototype, not a merge-ready consumer migration.Base:
refine-v3-yaml-authoring, pinned during preparation toec974430a87c04483a2808e580894b08ff23134e. Stacking on #30 makes this diff exactly one YAML file and isolates the alternative from #30's existing renderer and byte-formatting changes. #30 is unchanged.No parser, builder, renderer, generated SDK, or workflow changes. The unchanged consumers do not yet support this mixed flat-list schema, so a rendered preview is not evidence for this comparison. No build or deployment was requested or performed.
Comparable source size
Physical lines in each complete message definition, from its numeric message key to the next message key, including shared fields, prose, examples, and blank/comment lines. This measures the actual authored source, not generated output; wrapping and compact lists affect these figures.
Maximum indentation in MT39 drops from 16 to 12 spaces and MT58 from 20 to 14 spaces. MT34/35 still reach 18 because the existing captured exchanges remain attached. The flatter lists remove
exchange, per-methodversions, andcontextsnesting; lifecycle and error prose remains explicit, and common prose can repeat across flat version entries.The three additional worked proposal examples are a separate coverage increase, not evidence that the new syntax is bigger for equivalent content:
MT31's new conditional rules reach 18-space indentation versus 12 before. Fewer wrapper levels do not make conditional semantics disappear. The MT14 count includes two new scope-caveat comments; the global prototype banner is excluded from message-block counts.
Content and preservation
request,response, andpublicationstages; compact presence lists; fixed values separate from defaults, fallbacks, constraints, and conditional rules.methodsremains optional. All 44 unrelated message definitions and every protocol header are unchanged. Existing messages that lack operation metadata remain valid source material; no claim is made that all communication must be expressed as a method.readonly: true. Existing raw examples and the complete MT34/35 captured exchanges remain deeply equal after parsing, including bytes, encodings, targets, descriptions, and provenance. No captures or example bytes were invented.Explicit prototype choices and remaining decisions
keyis a prototype extension: stable operation identity is separate from editablename, following the latest discussion. Existing operation keys are retained for a later renderer to preserve links. Repeated keys have distinct versions. This YAML-only change itself does not implement link preservation.type: 5alone fully formalizes them. Shared ACK/error semantics and consumer integration remain open.Validation
Passed on the final YAML:
git diff --check.Not run: consumer test suite, build, or rendered browser comparison, deliberately excluded from this YAML-only request. The audits above are syntax/reference/preservation checks, not a complete formal schema validator or verification of proposed firmware semantics.