W3C home > Mailing lists > Public > www-archive@w3.org > September 2010

Re: URLs and application/x-www-form-urlencoded

From: Adam Barth <w3c@adambarth.com>
Date: Sun, 26 Sep 2010 18:05:22 -0700
Message-ID: <AANLkTi=UTzSEavVoP_wfNeCqX8a=rNg=inGnFRdnJbJe@mail.gmail.com>
To: KANZAKI Masahide <mkanzaki@gmail.com>
Cc: Anne van Kesteren <annevk@opera.com>, www-archive@w3.org, Ian Hickson <ian@hixie.ch>
Thanks for the pointer.  I haven't read that draft.  I haven't studied
the topic in enough detail to know what the issues are.  Generally,
the fact that the draft is using a new MIME type is inauspicious.


On Sun, Sep 26, 2010 at 5:55 PM, KANZAKI Masahide <mkanzaki@gmail.com> wrote:
> Hello Anne,
> FYI, are you aware of a new Internet Draft "The
> application/www-form-urlencoded format" [1] that tries to address some
> shortcomings of x-www-form-urlencoded ?
> cheers,
> [1] http://tools.ietf.org/html/draft-hoehrmann-urlencoded-01
> 2010/9/27 Anne van Kesteren <annevk@opera.com>:
>> I discussed the application/x-www-form-urlencoded format with Ian earlier
>> today. I'm not sure what the most appropriate place would be for this
>> between the URL semantics/syntax specification and the URL API
>> specification. Since you plan on specifying an API for query parameters it
>> would make sense if the application/x-www-form-urlencoded format was defined
>> together with the URL stuff. Yay more work? :-)
>> Might even make sense to have all the URL stuff in one specification, but I
>> do not know how that plays with IETF/W3C.
> --
> @prefix : <http://www.kanzaki.com/ns/sig#> . <> :from [:name
> "KANZAKI Masahide"; :nick "masaka"; :email "mkanzaki@gmail.com"].
Received on Monday, 27 September 2010 01:13:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 November 2012 14:18:33 GMT