- From: Johannes Koch <johannes.koch@fit.fraunhofer.de>
- Date: Tue, 20 Mar 2007 09:28:05 +0100
- To: public-wai-ert@w3.org
Shadi Abou-Zahra schrieb: > Johannes Koch wrote: [timestamping requests and responses] >> Hmm, in HTTP 1.1, section 13.2.3 >> <http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.2.3> >> there are several time values. > > This is "meta information", like the TCP stuff in the connection class. > It's not information that has been exchanged by the client and server. So? [Capitalization and white space in header values] > So here is a proposal for the convention: > - "The literal value of the properties will be the string string sent > by the client or the server. In other words, capitalization and white > space will be retained as-is." Capitalization: yes. White space: If you use just a literal for fieldValue, yes. If you split the value, leading and trailing white space should disappear. >>>>> 5.a. literal representation of the unprocessed headers >>>>> -> need to decide whether to implement this or not. It seems pretty >>>>> easy >>>>> to add an "http:transcript" property to store the original header >>>>> text. >>>> >>>> I don't think we need a literal representation of the unprocessed >>>> headers, if the processed representation of the headers is >>>> equivalent to the unprocessed stuff. >>> >>> Equivalent is in the eye of the beholder. I *may* be interested that >>> my server send "aCCept-language" instead of "Accept-language". It >>> would be optional anyway... >> >> Although both header names _are_ equivalent in HTTP terms, there may >> be a usecase :-) > > 1 down, 2 more to go... ;) Sorry, I don't get you. -- Johannes Koch BIKA Web Compliance Center - Fraunhofer FIT Schloss Birlinghoven, D-53757 Sankt Augustin, Germany Phone: +49-2241-142628 Fax: +49-2241-142065
Received on Tuesday, 20 March 2007 08:28:52 UTC