Remove given and optional URI assignments with PUT, PATCH, POST #621
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.
This PR is a correction class 2 change in the Solid Protocol ED:
Change: Remove requirement #server-put-patch-uri-assignment
PUTandPATCH(RFC 9110, RFC5789)PUTandPATCH.Change: Remove requirement #server-slug-uri-assignment
PUT,PATCH, andPOSTsupport, the optional support for the Slug header does not enhance the product classes, and there are specific scenarios requiring careful implementation to avoid information leakage (e.g., 574, 631, 1720) - which can be expressed in Considerations. The Solid Protocol need not promote this requirement (as MAY). Implementers can always choose to support this.