Fix schema links to static ones #1870
Merged
Conversation
This file contains 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
egekorkan
added
Editorial
sebastiankb
approved these changes
Aug 9, 2023
So I would try to keep the PRs focused for now. This one changes the index.html and once we agree on the link, we can change the resource behind it easily (where the |
|
Merging as communicated at https://lists.w3.org/Archives/Member/member-wot-wg/2023Aug/0003.html |
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 should fix these notes. My proposal is to merge this and #1861 together and decide on where to serve the content from. It doesn't matter if the schemas come from a new repo, a GitHub release or the publication folder but these links should appear in the REC.
Preview | Diff