docs(roadmap): record Track D status after the vocabulary, repository and API-form work - #532
Merged
Merged
Conversation
… and API-form work Co-Authored-By: jason.han <hanhuijun@gmail.com>
Co-Authored-By: jason.han <hanhuijun@gmail.com>
Co-Authored-By: jason.han <hanhuijun@gmail.com>
Contributor
Author
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
HuiJun
marked this pull request as ready for review
September 22, 2026 16:50
Contributor
Author
There was a problem hiding this comment.
🔍 Devin Review: 1 flag
Not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
Co-Authored-By: jason.han <hanhuijun@gmail.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.
What and why
docs/project/roadmap.mdstill described Track D as it stood before #507, #509, #519 and #523 landed: D1, D2 and D9 carried no status marker, the "what remains open" and cross-cutting order still listed "D2 and D1" as the next Flexo step and gated B4's Flexo provider and D10 on D9.2, and the track-local summary quoted the RDF ratchet at 353/353 with D8 "only conformant behind D1 and D2".This brings the roadmap in line with
develop:developfigures stated beside thev0.8.0gate table: validation census 163/217 (157 faithful, 6 approximate, 0 not implemented, 1 deliberate, 53 unknown), RDF corpus round trip 356/356, API element-form round trip 354/356.No other file changes;
spec-compliance.md,README.md, the guide and reference pages were checked and already match the tree.How it was verified
Full gate on
developat9d67a0235before editing:go build,go vet,gofmt -l(empty),go test ./..., the four corpus/identity gates with their require variables set,make docs-check,make man-check,make docs-counts(already current),python3 scripts/changelog.py check— all pass, and the figures above are the ones those gates printed.On this branch:
make docs-check,make docs-counts(already current),python3 scripts/changelog.py check.Checklist
make testandmake lintpass locallymake docs-countsrun if a gate count moved (no count moved;docs-countsis current)F4,K5) in the body, docs, or changelog