Standardize Application-Specific Headers #71
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
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.
What does this PR do?
This PR standardizes the notion of application-specific headers. An application-specific header is a header that is not covered by this specification but used by an implementation. This PR standardizes the format for application-specific headers.
Example:
If an application
Foo Barwants to introduce a header for the speed of a song (whatever that may mean) it could use the application-specific header#FOO_BAR-SPEED.Closes Issue(s)
Closes #56
Motivation
See #56
Additional Notes
I have used the hyphen as a separator for application-specific headers because I found it to be visually more convincing. There is a small technical benefit in that double-clicking a word usually includes underscores but not hyphens. So using an underscore as a separator (and potentially a hyphen within the application or header name) would be a little more difficult to double-click-copy. I am open to change this if another pattern is preferred.