Re: paramname in draft-reschke-basicauth-enc-04

"Anne van Kesteren" <annevk@opera.com> Sat, 04 February 2012 07:15 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B99A21F84E4 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 3 Feb 2012 23:15:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g8sFA6jesiLk for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 3 Feb 2012 23:15:46 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 8568121F84E1 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 3 Feb 2012 23:15:46 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1RtZpI-0001kc-6c for ietf-http-wg-dist@listhub.w3.org; Sat, 04 Feb 2012 07:14:24 +0000
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <annevk@opera.com>) id 1RtZoz-0001j8-Fu for ietf-http-wg@listhub.w3.org; Sat, 04 Feb 2012 07:14:05 +0000
Received: from smtp.opera.com ([213.236.208.81]) by maggie.w3.org with esmtp (Exim 4.72) (envelope-from <annevk@opera.com>) id 1RtZow-00026e-Mj for ietf-http-wg@w3.org; Sat, 04 Feb 2012 07:14:04 +0000
Received: from annevk-macbookpro.local (a83-160-99-114.adsl.xs4all.nl [83.160.99.114]) (authenticated bits=0) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q147DSIi024522 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 4 Feb 2012 07:13:29 GMT
Content-Type: text/plain; charset="utf-8"; format="flowed"; delsp="yes"
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Cc: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Julian Reschke <julian.reschke@gmx.de>, HTTP Working Group <ietf-http-wg@w3.org>
References: <20120129152840.10536.93223.idtracker@ietfa.amsl.com> <4F2567DA.3060608@gmx.de> <visci75v85ndepsfib5qfpdqvsb84m8piu@hive.bjoern.hoehrmann.de> <4F26D337.1020507@gmx.de> <4F279977.1080705@it.aoyama.ac.jp> <4F285AB3.4090506@gmx.de> <op.v82myadp64w2qv@annevk-macbookpro.local> <hsapi7pkbff0ok1loepbbbgnetrtp17ogr@hive.bjoern.hoehrmann.de>
Date: Sat, 04 Feb 2012 08:13:31 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Anne van Kesteren <annevk@opera.com>
Organization: Opera Software
Message-ID: <op.v847ottn64w2qv@annevk-macbookpro.local>
In-Reply-To: <hsapi7pkbff0ok1loepbbbgnetrtp17ogr@hive.bjoern.hoehrmann.de>
User-Agent: Opera Mail/11.60 (MacIntel)
Received-SPF: pass client-ip=213.236.208.81; envelope-from=annevk@opera.com; helo=smtp.opera.com
X-W3C-Hub-Spam-Status: No, score=-4.2
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01
X-W3C-Scan-Sig: maggie.w3.org 1RtZow-00026e-Mj 5313edc2000dbec5fe9bd1183e73521c
X-Original-To: ietf-http-wg@w3.org
Subject: Re: paramname in draft-reschke-basicauth-enc-04
Archived-At: <http://www.w3.org/mid/op.v847ottn64w2qv@annevk-macbookpro.local>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/12308
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Resent-Message-Id: <E1RtZpI-0001kc-6c@frink.w3.org>
Resent-Date: Sat, 04 Feb 2012 07:14:24 +0000

On Sat, 04 Feb 2012 04:58:07 +0100, Bjoern Hoehrmann <derhoermi@gmx.net>  
wrote:
> * Anne van Kesteren wrote:
>> Other than XML, is there a precedent for using "encoding"? Most places  
>> use "charset" I think (HTTP, CSS, HTML).
>
> DOM Level 3 Core uses xmlEncoding and inputEncoding, XSLT uses output-
> encoding, .NET uses System.Text.Encoding.*, Google search uses "ie" and
> "oe" parameters indicating "encoding", ... It seems unlikely you could
> make a sensible argument about usage (outside the context of HTTP
> headers, which includes "HTML") to choose one over the other here.

Well, CSS has @charset, and HTML has a charset attribute. And xmlEncoding  
and inputEncoding are on their way out. I think it would make more sense  
to keep using charset as a keyword.


-- 
Anne van Kesteren
http://annevankesteren.nl/