27528 2014-12-05 22:32:41 +0000 terminology: distinguish between URL objects and URL strings 2014-12-06 14:22:58 +0000 1 1 1 Unclassified WHATWG URL unspecified PC Linux RESOLVED DUPLICATE 26405 P2 normal Unsorted 1 rubys annevk fielding mike rubys sideshowbarker+urlspec oldest_to_newest 115978 0 rubys 2014-12-05 22:32:41 +0000 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. 115982 1 annevk 2014-12-06 14:22:58 +0000 *** This bug has been marked as a duplicate of bug 26405 ***