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.
Adam On Sun, Sep 26, 2010 at 5:55 PM, KANZAKI Masahide <[email protected]> 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 <[email protected]>: >> 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 "[email protected]"]. >
