- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Feb 2021 20:45:02 +0000
- To: public-hydra-logs@w3.org
I think I have one reservation about the current proposal, regarding `possibleHeaderValue`. Naming aside, I think it's not universally sufficient as I see two distinct cases one might want to express: - open set, especially for response headers, indicating that other values are possible - closed set, especially for request headers, for example where a `content-type` would only be allowed to be one of the values provided In the latter case, I think we'd need some way to assert that fact. And for the name I propose more terse `possibleValue` -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/186#issuecomment-780106689 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 16 February 2021 20:45:04 UTC