Repository navigation
docs(spec): settle the last three provisional readings - #22
Merged
Merged
Conversation
The owner ruled on 2026-10-20 that the three readings still marked provisional are final as drafted: comments and blank lines may stand inside a block (§4.2, §6); duplicate-edge compares labels as bytes after removing leading and trailing WSP (§4.6); and after subgraph the whole run of WSP is skipped before the subgraph-without-id test (§4.7). Drop their markers from the text, move their bullets into the "Settled by the owner" list at their original positions, and reword the status paragraph and the opening of §12 so they hold with no reading provisional. The provisional tag stays defined in §10 for any future reading. The seven cases that pinned these readings drop their tag and the matching line in WHY.md, as the other settled cases did; no outcome changes. Signed-off-by: Cameron Brooks <95648474+CameronBrooks11@users.noreply.github.com>
Removing the provisional marker left one line of the comment rule at 97 characters. Re-wrap the rest of the paragraph to the file's width; the text is unchanged. Signed-off-by: Cameron Brooks <95648474+CameronBrooks11@users.noreply.github.com>
Note in the provenance section that the last seven provisional tags and their seven "Pins the provisional reading" lines in WHY.md were removed when the owner settled the last three readings, as the tags of the other 23 were before. Signed-off-by: Cameron Brooks <95648474+CameronBrooks11@users.noreply.github.com>
The README said boundary twins are named ...-accepted and ...-refused,
as if each pair had one of each. Since §4.2 rule 3 refuses any line
holding ::: or @{, both twins of some pairs are refused, so say each
case is named for its own outcome.
Signed-off-by: Cameron Brooks <95648474+CameronBrooks11@users.noreply.github.com>
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.
The owner ruled on 2026-10-20 that the three readings still marked provisional in SPEC.md are final as drafted:
duplicate-edgecompares labels as bytes after removing leading and trailingWSP(§4.6);subgraph, the whole run ofWSPis skipped before thesubgraph-without-idtest (§4.7).SPEC.md
:::and@{stays last, so "except the last" still holds.provisionaltag defined and adds that no case carries one now.Conformance cases
The seven cases that pinned these readings drop the
provisionaltag fromexpect.json, the way #19 handled the other settled readings. Each also drops its**Pins the provisional reading (§12):**line inWHY.md, since no other settled case carries that line any more. The README's Provisional readings pinned table is replaced by a note that none remain. No outcome changes. WHY.md quotes of SPEC.md at 055509e are left as they are.Gates