Re: [ietf-types] The application/www-form-urlencoded format

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Mon, 27 September 2010 07:15 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf-types@core3.amsl.com
Delivered-To: ietf-types@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 325363A6C8F for <ietf-types@core3.amsl.com>; Mon, 27 Sep 2010 00:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.848
X-Spam-Level:
X-Spam-Status: No, score=-99.848 tagged_above=-999 required=5 tests=[AWL=-0.058, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MaxRRWEgzQNq for <ietf-types@core3.amsl.com>; Mon, 27 Sep 2010 00:15:29 -0700 (PDT)
Received: from pechora2.lax.icann.org (pechora2.icann.org [IPv6:2620:0:2d0:1::37]) by core3.amsl.com (Postfix) with ESMTP id 319423A67CC for <ietf-types@ietf.org>; Mon, 27 Sep 2010 00:15:29 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by pechora2.lax.icann.org (8.13.8/8.13.8) with ESMTP id o8R7Fkns025931 for <ietf-types@iana.org>; Mon, 27 Sep 2010 00:16:06 -0700
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id o8R7Fjf5007453 for <ietf-types@iana.org>; Mon, 27 Sep 2010 16:15:45 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 0e2e_265b_0b8be260_ca07_11df_a37a_001d096c5782; Mon, 27 Sep 2010 16:15:45 +0900
Received: from [IPv6:::1] ([133.2.210.1]:51956) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S1454B3E> for <ietf-types@iana.org> from <duerst@it.aoyama.ac.jp>; Mon, 27 Sep 2010 16:15:43 +0900
Message-ID: <4CA04494.20908@it.aoyama.ac.jp>
Date: Mon, 27 Sep 2010 16:15:32 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
References: <k1os96p03o78p78490hei104biadpiepit@hive.bjoern.hoehrmann.de> <4C9ED94B.6080505@it.aoyama.ac.jp> <cobv96t2l31brfk85r30h6j8qto4rh8ero@hive.bjoern.hoehrmann.de>
In-Reply-To: <cobv96t2l31brfk85r30h6j8qto4rh8ero@hive.bjoern.hoehrmann.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Greylist: Delayed for 25:50:01 by milter-greylist-4.0 (pechora2.lax.icann.org [208.77.188.37]); Mon, 27 Sep 2010 00:16:06 -0700 (PDT)
Cc: ietf-types@iana.org
Subject: Re: [ietf-types] The application/www-form-urlencoded format
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Sep 2010 07:15:31 -0000

On 2010/09/27 6:02, Bjoern Hoehrmann wrote:
> * Martin J. Dürst wrote:
>> Can you give some rough information on where
>> application/www-form-urlencoded is implemented or implementation is planned?
>
> Well, that depends on what you would consider an implementation. You can
> use it in the `enctype` attribute of the form element in a HTML document
> right now (if you use "get" as the method and UTF-8 for the document)
> and it will work in most browsers, except they use "&" as separator. The
> label as such isn't used anywhere that I know of yet. I do not know of
> anyone other than me planning to support the label.

Ok. That implies that if you use another character encoding for the 
document, it will fail, which isn't helpful at all. It also means that 
you can get exactly the same, with the above preconditions, if you use 
the x- variant.

>> Also, in many cases, an identifier without x- denotes just the same as
>> the identifier with the x-. I think it would be good if the registration
>> template contained at least a small reminder and pointer to make clear
>> that it's not exactly the same as the x- variant.
>
> As I understand it, IANA does not copy the template to its web site, and
> I don't know of anyone else using the templates out of context, and the
> form does not really have a field where this could go, so I am reluctant
> to do that.

That's okay then. But the draft should be very explicit about it.

Regards,   Martin.

-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp