Add certification scenario#511
Open
alexolivier wants to merge 2 commits into
Open
Conversation
Signed-off-by: Alex Olivier <alex@alexolivier.me>
alexolivier
force-pushed
the
add-certification-scenario
branch
from
779bc91 to
f2ef253
Compare
Convert the certification scenario to a kramdown-rfc document (frontmatter modelled on the MCP profile), with auto-numbered sections and anchor-based cross-references in place of manual test IDs. Wire it into the publish workflow so it renders to authorization-api-1_0-certification-scenario.html and deploys to GitHub Pages alongside the spec and profiles. Signed-off-by: Alex Olivier <alex@alexolivier.me>
alexolivier
requested review from
baboulebou,
davidjbrossard,
julioauto and
tulshi
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.
Actual asset rather than issue
closes #433
Published artifact
The certification scenario is now an
kramdown-rfcdocument (frontmatter modelled on the MCP profile) and is wired into thepublishworkflow. On merge tomainit is rendered and deployed to GitHub Pages alongside the spec and profiles:/authorization-api-1_0-certification-scenario.htmlBuild steps mirror the existing docs (
kramdown-rfc2629→xml2rfc→upload-pages-artifact). Sections are auto-numbered, with anchor-based cross-references replacing the manual test IDs.