Application cache uses the term resource where it really talks about the bits fetched from the network for a resource, which are called representations in RFC 2616. The spec should be consistent with HTTP because of its dependency on HTTP.
RFC2616 is the one unnecessarily introducing new terminology here. A resource is a bag of bits, and HTML5 consistently uses that term throughout.
Mike, it appears this one needs to be escalated.
HTTP's definition of resource vs representation has stood since 1996 (http://tools.ietf.org/html/rfc1945#section-1.2). Even if HTML5 consistently uses resource in place of representation, it is incorrect to do so since those reading HTTP in conjunction with HTML5 would be confused.
escalated to tracker:
Now that this is a tracker issue, I'm moving the status for this bug here back to Resolved
This bug predates the HTML Working Group Decision Policy.
If you are satisfied with the resolution of this bug, 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:
This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.