Re: Semantic meaning of double quotation marks delimiting quoted-string

Geoffrey Sneddon wrote:
> ...
> I was referring to my original example, i.e.,
>> If you don't [parse the quotation marks out], you can end up with 
>> character sets such as "UTF-8" (i.e., including the quotation marks) 
>> in headers like Content-Type: text/plain;charset="UTF-8".
> Which really is the question: what are we meant to do with the 
> delimiting quotation marks in quoted-string?

Well, in general keep them.

> If we take UTF-8 as a string, we can escape this as a quoted-string in 
> several ways, including:
> - "UTF-8"
> - "\U\T\F\-\8"
> Now, are we meant to unescape every quoted-string we come across 
> (therefore including entity-tag), or only some? I think we can all agree 
> that "\U\T\F\-\8" is not, in itself, a valid character set. If only 
> some, which? As it stands now, it is not clear if you should ever 
> unescape them.

I agree this is fuzzy, but I *disagree* that this fuzziness applies to ETag.

As far as I can tell, the quotes are an integral part of the ETag. It's 
invalid to leave them out.

Best regards, Julian

Received on Sunday, 28 October 2007 22:05:58 UTC