W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2007

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

From: Geoffrey Sneddon <foolistbar@googlemail.com>
Date: Sun, 28 Oct 2007 22:10:02 +0000
Message-Id: <A600F7EC-E053-469C-A082-A37DC9BF7F5D@googlemail.com>
Cc: ietf-http-wg@w3.org
To: Julian Reschke <julian.reschke@gmx.de>


On 28 Oct 2007, at 22:05, Julian Reschke wrote:

> 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.

My point is that such behaviour, like when to keep them and not,  
should be defined.

All the best,

Geoffrey Sneddon.
Received on Sunday, 28 October 2007 22:10:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:23 GMT