This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This bug is opened on behalf of Roy Fielding, based on http://lists.w3.org/Archives/Public/public-ietf-w3c/2014Dec/0007.html Original comment: I don't see any problem with continuing to use URL as the API name for an object that contains a parsed reference and produces a URL string. That should be distinguishable by context (e.g., code). What I have a problem with is the notion that both the input and the output of those processes is a URL. That is madness. There is a reason why the input is called href or src, not URL.
*** This bug has been marked as a duplicate of bug 26405 ***