This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Description ----- The retrieval sections in a moki representation contain information about exchanges needed to retrieve content. The final entity that represents the retrieved resource may appear in an entity element. The problem is that the content of this element is not the raw data that has been received, but the decoded version of the raw data that has been received, e.g. it does not contain the raw bytes of the received HTML page, but the decoded text of the received HTML page. The size attribute contains the size of the raw data that has been received. As such, the content of the element may not be of the same size as the size attribute seems to suggest. This looks a bit weird. The only real place where the entity content is being used is for external CSS stylesheets, AFAICT. Solution ----- I guess the correct solution would be to output the raw data in the entity element, or perhaps not to output anything because we don't really need the raw data anymore (we still need the size though!), and to output the decoded content elsewhere, as part of the decoded representation of the resource. There is no need to output raw data for images and other binary content. This could go to a decodedContent or decodedEntity element at the same level as retrieval and XHTMLDocInfo or imageInfo.
One thing that I haven't emphasized in the previous description is that having the decoded content appear in the HTTPResponse section creates an unnecessary binding to the HTTP scheme. The CSS tests that use the entity element expect to find it under an HTTPResponse element, and such an element only makes sense for the HTTP scheme. As such, the CSS tests that have nothing to do with HTTP cannot apply to other schemes.