Explicitly link to geo URI spec #3492
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
|
Seeing as that RFC looks to be what the spec was originally referring to (and matches the example event body), then this is just a clarification - and as such does not need an MSC. |
turt2live
requested changes
Nov 15, 2021
Co-authored-by: Travis Ralston <travisr@matrix.org>
shenanigans77-jpg
approved these changes
Nov 24, 2021
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.
We mention geo uri in the spec, but unhelpfully do not link to any documentation on what those are. This PR explicitly names the RFC and links to it. I am unsure if this needs a MSC, since I believe it doesn't change the spec in a meaningful way and just clarifies which RFC we're talking about.
If this needs a proposal, happy to open one first.
Preview: https://pr3492--matrix-org-previews.netlify.app