W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2012

Re: feedback on draft-reschke-basicauth-enc-04, "3. The 'encoding' auth-param"

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Mon, 30 Jan 2012 14:17:08 +0100
To: "Alexei Khlebnikov" <alexei.khlebnikov@opera.com>
Cc: ietf-http-wg@w3.org
Message-ID: <ff4di7h44pike7nb859avqr4lc5cbr38ml@hive.bjoern.hoehrmann.de>
* Alexei Khlebnikov wrote:
>My feedback on  
><http://greenbytes.de/tech/webdav/draft-reschke-basicauth-enc-04.html#encoding>:
>
>Was it considered to name the new parameter "charset" instead of  
>"encoding"?

Well, "we" are trying to http://www.w3.org/TR/charmod/#C020 move away
from using the "charset" term and there are not many alternative words
to choose from if you want to use an established term.

>I can see the following advantages of "charset":
>
>1) "Charset" is unambigous. "Encoding" is ambigous, it can refer to many  
>things: base64, quoted-printable, chunked-coding, gzip-compression, etc.

That is probably largely thanks to language hygiene efforts like above,
it used to be rather unclear what people meant when they said "charset"
or "character set". Maybe we can declare success and use it, at least
where it's consistent with existing usage, but expect complaints.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Monday, 30 January 2012 13:17:17 GMT

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