v3.2: Add support for application/linkset[+json] #4740
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
These media types solve our long-standing problems with modeling HTTP Link headers. We do not need to define anything beyond noting how to use them media types in a Media Type Ojbect.
handrews
added
media and encoding
This was referenced Jun 19, 2025
|
I am always glad to see standards being useful and being adopted. And of course even more so when I played a role in creating these standards. But, @handrews, is there anything I need to actually review here other than being happy to see this happening? |
dret
reviewed
Jun 20, 2025
3 tasks
lornajane
reviewed
Jul 8, 2025
Co-authored-by: Lorna Jane Mitchell <[email protected]>
|
I like the concept here and support adding this feature. |
@darrelmiller Do you like it enough to approve this PR? 😎 |
lornajane
approved these changes
Jul 16, 2025
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.
Fixes:
These media types solve our long-standing problems with modeling HTTP Link headers. We do not need to define anything beyond noting how to use them in a Media Type Ojbect. RFC9264 already defines the mapping between the JSON data model, the standalone HTTP-like format, and the actual HTTP
Linkheader syntax. This fits well with our 3.2 theme of data modeling improvements.When someone hands us a standardized solution for our problem, we should improve the standards ecosystem by adopting it :-) Note that this is much more powerful and flexible than the hack I used as an example elsewhere, which required a mind-boggling combination of
anyOf,contains, andpatternand can't do much beyond checking for the link relations that way. Its also fragile due to the need to manage quoting and whitespace concerns, and the possibility of something elsewhere in a header matching a link relation type string. RFC9264 has none of these problems.