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

Bjoern Hoehrmann <derhoermi@gmx.net> Sat, 04 February 2012 04:01 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 1AC1711E80A0 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 3 Feb 2012 20:01:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.499
X-Spam-Level:
X-Spam-Status: No, score=-7.499 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_50=0.001, 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 0QL-uRNTfhHE for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 3 Feb 2012 20:01:29 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 2E19E11E80A1 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 3 Feb 2012 20:01:28 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1RtWmP-000469-Dl for ietf-http-wg-dist@listhub.w3.org; Sat, 04 Feb 2012 03:59:13 +0000
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <derhoermi@gmx.net>) id 1RtWlo-00044c-Lb for ietf-http-wg@listhub.w3.org; Sat, 04 Feb 2012 03:58:36 +0000
Received: from mailout-de.gmx.net ([213.165.64.23]) by maggie.w3.org with smtp (Exim 4.72) (envelope-from <derhoermi@gmx.net>) id 1RtWll-0004YU-Rp for ietf-http-wg@w3.org; Sat, 04 Feb 2012 03:58:35 +0000
Received: (qmail invoked by alias); 04 Feb 2012 03:58:07 -0000
Received: from dslb-094-222-141-016.pools.arcor-ip.net (EHLO HIVE) [94.222.141.16] by mail.gmx.net (mp017) with SMTP; 04 Feb 2012 04:58:07 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1+VhWgcOlqVURmvnfGdRA2O2MEWgZYSCyT3M8cevU nxww7ztZp1ekjb
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Anne van Kesteren <annevk@opera.com>
Cc: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Julian Reschke <julian.reschke@gmx.de>, HTTP Working Group <ietf-http-wg@w3.org>
Date: Sat, 04 Feb 2012 04:58:07 +0100
Message-ID: <hsapi7pkbff0ok1loepbbbgnetrtp17ogr@hive.bjoern.hoehrmann.de>
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>
In-Reply-To: <op.v82myadp64w2qv@annevk-macbookpro.local>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Received-SPF: pass client-ip=213.165.64.23; envelope-from=derhoermi@gmx.net; helo=mailout-de.gmx.net
X-W3C-Hub-Spam-Status: No, score=-1.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01
X-W3C-Scan-Sig: maggie.w3.org 1RtWll-0004YU-Rp c363ec1991418b7185a9b1cc548e5353
X-Original-To: ietf-http-wg@w3.org
Subject: Re: paramname in draft-reschke-basicauth-enc-04
Archived-At: <http://www.w3.org/mid/hsapi7pkbff0ok1loepbbbgnetrtp17ogr@hive.bjoern.hoehrmann.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/12307
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: <E1RtWmP-000469-Dl@frink.w3.org>
Resent-Date: Sat, 04 Feb 2012 03:59:13 +0000

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