[specification] Clarify SEP numbering #1045
Merged
Conversation
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
localden
approved these changes
Jul 23, 2025
koic
reviewed
Jul 23, 2025
| @@ -44,9 +44,9 @@ Each SEP must have an **SEP author** -- someone who writes the SEP using the sty | |||
|
|
|||
| SEPs should be submitted as a GitHub Issue in the [specification repository](https://github.com/modelcontextprotocol/modelcontextprotocol). The standard SEP workflow is: | |||
|
|
|||
| 1. You, the SEP author, create a [well-formatted](#sep-format) GitHub Issue with the `SEP` and `proposal` tags. Do not assign an SEP number; one will be assigned by the SEP sponsor. | |||
| 1. You, the SEP author, create a [well-formatted](#sep-format) GitHub Issue with the `SEP` and `proposal` tags. The SEP number is the same as the Github Issue number, the two can be used interchangably. | |||
There was a problem hiding this comment.
Suggested change
| 1. You, the SEP author, create a [well-formatted](#sep-format) GitHub Issue with the `SEP` and `proposal` tags. The SEP number is the same as the Github Issue number, the two can be used interchangably. | |
| 1. You, the SEP author, create a [well-formatted](#sep-format) GitHub Issue with the `SEP` and `proposal` tags. The SEP number is the same as the GitHub Issue number, the two can be used interchangably. |
dsp-ant
approved these changes
Jul 23, 2025
dsp-ant
added a commit
that referenced
this pull request
Jul 25, 2025
Follow-up to #1045 (review). Co-authored-by: David Soria Parra <[email protected]>
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.
Refine SEP numbering strategy to be instead based on the Issue number.
Motivation and Context
Aids discovery, auto-numbering, and navigation.
How Has This Been Tested?
N /A
Breaking Changes
N/A
Types of changes