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 13:12:56 -0700
Message-ID: <AANLkTinsAXF5tLYiQZAjn94TYOvSD4MamT5zi1WhH1-k@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: www-archive@w3.org, Ian Hickson <ian@hixie.ch>
I think the URL stuff is going to end up getting split into at least
two documents.  One that describes the
parsing/resolving/canonicalizing of URLs and another that defines a
web API for interacting with URLs.  We could start off with them in
the same document, but we'll probably be forced to split them up later
anyway.

w.r.t. application/x-www-form-urlencoded, I haven't studied the format
in detail, but my sense is that it could be included in one of those
documents.  Currently, the URL API document has algorithms for parsing
and serializing query parameters, so that might be a good place to
start off putting application/x-www-form-urlencoded.

Adam


On Sun, Sep 26, 2010 at 1:08 PM, Anne van Kesteren <annevk@opera.com> wrote:
> Hey Adam,
>
> 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.
>
> Cheers,
>
>
> --
> Anne van Kesteren
> http://annevankesteren.nl/
>
Received on Sunday, 26 September 2010 22:10:12 GMT

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