Move the deprecated elements at the end of the specs #487
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
This was referenced Apr 18, 2021
This was referenced May 9, 2021
|
Add some text explaning that "players don't have to support these deprecated elements". |
mbunkus
approved these changes
May 30, 2021
hubblec4
approved these changes
May 30, 2021
retokromer
approved these changes
May 30, 2021
|
@robUx4 This branch has conflicts now, too. Please rebase & then merge. Thanks. |
it's already in the title section and the path
|
I had to rework the patch a bit as notes were no longer the last markdown file processed. |
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.
And move the IANA Considerations at the end.
Maybe we need to define what fields should be in the registry ? At least the ID, the name, and likely the path.
It might use the same registry fields as the regular/used Matroska IDs.
Fixes #305