- From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
- Date: Tue, 21 May 2019 12:27:14 +0300 (EEST)
- To: HTTP Working Group <ietf-http-wg@w3.org>
- CC: Poul-Henning Kamp <phk@phk.freebsd.dk>, Mark Nottingham <mnot@mnot.net>, Tommy Pauly <tpauly@apple.com>, Kari Hurtta <hurtta-ietf@elmme-mailer.org>
> A. Leave the document as-is, without specifying a URI type for SH; > note that URI types can be added in a future revision > > B. Specify a URI type for SH as a String Weak preference is B. I assume that this means sh-item += sh-reference sh-reference = "<" *(chr) ">" Analogical to sh-string = DQUOTE *(chr) DQUOTE However sh-reference can not be allowed exactly same characters. Specially < > can not allowed. And \ escaping is not needed to be allowed because there %xx encoding can be used. Some clarify needed what this means? ( <https://github.com/httpwg/http-extensions/issues/782> seems suggesting sh-item += sh-reference sh-reference = "<" URI-reference ">" which imply that generic structured header parser check URI syntax. ) That make sense if there is parameter values which want literal string or alternatively allow giving value as reference. Using < > as separator then makes they syntactically different. Requiring that generic structured header parser checks URI syntax is perhaps too much, but if URI type for SH is defined as String that is not required. This B is very weak preference, because most URI parameters seems want only URI ie there is no need for both literal string and URI. Because URI's occurs on http very often it however makes sense to mark them with specific syntax. / Kari Hurtta
Received on Tuesday, 21 May 2019 09:27:50 UTC