Given PUT, PATCH, and POST support, 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.
Conformance
Does not affect conformance.
Testing
Can be part of test cases that checks for optional features in HTTP.
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.