W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: URL spec parameter-related methods use "parameter" in a way inconsistent with the URI RFC

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 24 May 2012 12:03:03 +0200
Message-ID: <4FBE0757.6080700@gmx.de>
To: Maciej Stachowiak <mjs@apple.com>
CC: "public-webapps@w3.org WG" <public-webapps@w3.org>
On 2012-05-24 11:29, Maciej Stachowiak wrote:
> The current draft URL spec has a number of Parameter-related methods (getParameterNames, getParameterValues, hasParameter, getParameter, setParameter, addParameter, removeParameter, clearParameters)[1]. Apparently these methods refer to key-value pairs in the query part of the URL as "parameters". However, the term "parameter" is used by the URI RFC[2] to refer to something else, a semicolon-delimited part of a path (which I think is nearly obsolete in modern use; I am not sure what it is for). I understand that for legacy reasons, much of the URL interface cannot be consistent with RFC-official terminology. But it seems like a bad idea to use the same term for a different piece of the URL, worse than using the same term for a different part. At least call it something like "query parameters" to disambiguate.

The URI RFC actually is RFC 3986. Otherwise, agreed.

> ...

Best regards, Julian
Received on Thursday, 24 May 2012 10:03:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:34 UTC