Guidance on HTTP headers an "targetHints"/"headerSchema" #422
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
The whole feature is pretty vague, so provide more guidance on what headers are good to use in schemas and support in implementations.
This is another very vague and open-ended feature. Provide more guidance on what headers are and are not useful to describe.
dlax
approved these changes
Sep 24, 2017
gregsdennis
added
clarification
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Both of these features are extremely vague, and it seems like a good idea to provide some guidance on which headers are and are not useful for schema authors to use, and implementations to support, for each of them.
As for what it means for an implementation to support these, I'll address that more thoroughly in the rewrite, assuming this guidance is accepted.