8462 2009-12-08 16:19:54 +0000 "fetch the resulting absolute URL" 2010-10-04 13:58:23 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC Windows NT RESOLVED WONTFIX P3 normal --- 1 julian.reschke ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 30005 0 julian.reschke 2009-12-08 16:19:54 +0000 "4.8.5 The object element ... If that is successful, fetch the resulting absolute URL,..." This should say "...fetch the resource identified by the resulting..." (according to the definition of 'fetch'). 30625 1 ian 2010-01-06 10:44:33 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Partially Accepted Change Description: see diff given below Rationale: The terminology is used all over the place, so I just changed the "fetch" algorithm to allow it to be used with either a resource or a URL. 30626 2 contributor 2010-01-06 10:45:48 +0000 Checked in as WHATWG revision r4518. Check-in comment: make 'fetch' support being called with a URL, since that is what the spec does all over the place anyway. http://html5.org/tools/web-apps-tracker?from=4517&to=4518 30633 3 julian.reschke 2010-01-06 10:52:24 +0000 You just made things even more confusing. URLs are identifiers. The result of "fetching" an identifier isn't the same thing as fetching what it identifies (there's a difference in the levels of indirection). Please undo, and just make the spec consistent. 30638 4 ian 2010-01-06 11:05:24 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: Nonsense, people talk about fetching URLs all the time, it's not confusing at all. 30639 5 julian.reschke 2010-01-06 11:09:41 +0000 The purpose of a spec is not to mirror the language that "people use" (which is acceptable to be sloppy), but to be consistent internally, consistent with other specs, and precise. 30643 6 ian 2010-01-06 11:21:25 +0000 No, the purpose of a spec is to set out what should happen in such a way that interoperability is achieved. It could be sloppy and inconsistent and completely intelligible, if that happened to be the way to get interoperability (it rarely is). In this particular instance, however, it is self-consistent, unambiguous, and consistent with numerous specs (just not some that happen to themselves be ambiguous and confusing in their terminology use).