fix: small editorial fixes across spec, README, ReSpec config, and docs#74
Merged
Merged
Conversation
- Fix README well-known path typo (./well-known -> /.well-known) - Update stale ReSpec abstract (server.json -> MCP Server Cards) - Use full-length sha256 digests in examples per the Digest Format definition (spec and docs) - Align MCP mapping example URN publisher segment with the entry's actual publisher domain (example.com -> acme-corp.com) - Clarify Well-Known URI prose: Trust Manifests are inline on entries, not retrieved from artifact URLs - Correct getting-started Level 2 claim (host object is required; well-known serving is optional) - Remove misleading identityType hints and open-string relation wording in the adding-trust guide
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
2 participants
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.
Fixes #67
Small mechanical fixes across the spec, README, ReSpec config, and docs site. No normative behavior changes.
./well-known/ai-catalog.json->/.well-known/ai-catalog.jsonspecification/respec-config.json): the appendix maps to MCP Server Cards, not "the MCP Registry server.json format"; the abstract now matches the appendix contentsha256:a1b2c3d4e5f6example values with full 64-char hex digests, matching the Digest Format definition (3 places in the spec, 1 indocs/examples/multi-protocol-agent.md)urn:air:example.com:mcp:finance-server->urn:air:acme-corp.com:mcp:finance-server(identifier, Trust Manifest identity, and the conceptual-mapping table row), so the URN publisher segment matches the entry's actual publisher and URLsdocs/getting-started.md: Level 2 requires thehostobject per the spec; serving at the well-known URI is optional. Reworded the sentence that claimed well-known serving alone reaches Level 2docs/guides/adding-trust.md: removed"identityType": "did"from two examples whose identity is aurn:air:URN (not a DID), and reworded "Threerelationtypes are defined" to reflect thatrelationis an open string with common valuesVerification
tools/build_spec.pyspecification/respec-config.jsonparses as valid JSON