docs: correct the standards home and the profile-status text in three places - #133
Merged
Conversation
… places Three documents named three different standards homes. Section 6.1 proposed splitting TRACE between CoSAI and the Linux Foundation entity hosting MCP, the README said "Targeting AAIF", and the roadmap said something else again. TRACE is being formed at the Linux Foundation as its own series, "TRACE Specification, a Series of LF Projects, LLC", which #127 is preparing GOVERNANCE.md for. Section 4.1 described the MCP and A2A profiles as "targeted for v0.2" inside the v0.2 document. Neither shipped in v0.2. Both now say v0.3, and the A2A entry names what did land: the delegation link block, as the foundation the binding rules attach to. The two open questions those changes answer, Q1 host organization and Q6 A2A timing, are marked resolved in place rather than deleted, so a reader tracking them can see how they landed. The section heading moves from "before v0.2" to "before v1.0". Section 6.3 licensing is deliberately untouched. It still says CC BY 4.0 for specifications, and the LF relicensing question is live on #127. No normative text, schema, or record field changed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.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
1 participant
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.
Stale-text sweep, follow-up to #132.
Standards home
Three documents named three different homes.
spec/trace-v0.2.md§6.1 proposed splitting TRACE between CoSAI (technical workstream) and the LF entity hosting MCP (spec, IP, trademark);README.mdsaid "Targeting AAIF"; the roadmap said something else again. None is where this is going.TRACE is being formed at the Linux Foundation as its own series, "TRACE Specification, a Series of LF Projects, LLC", which #127 is preparing
GOVERNANCE.mdfor. §6.1 is rewritten and says what it supersedes and why. The README line is corrected. CoSAI stays named as a technical-liaison partner, which is accurate.Profile status
§4.1 described the MCP and A2A profiles as "targeted for v0.2" inside the v0.2 document. Neither shipped in v0.2. Both now say v0.3, and the A2A entry names what did land: the
delegationlink block, as the foundation the binding rules attach to.Open questions
§7 was headed "These need input before v0.2" in v0.2. Now v1.0. Q1 (host organization) and Q6 (A2A profile timing) are marked resolved in place with strikethrough rather than deleted, so anyone tracking those questions can see how they landed. The remaining five are untouched.
Deliberately not changed
§6.3 still says CC BY 4.0 for specifications. The LF General Project Policies block makes Apache-2.0 the project license for code and specifications, but that relicense is a live question on #127 with a contributor-consent dependency. Not something to change quietly in a sweep.
No normative text, schema, or record field changed.
🤖 Generated with Claude Code