The root element of a moki document.

A timestamp of when the retrieval activity started.

The value should be the number of milliseconds elapsed since January 1, 1970 UTC.

Information about the process carrying out the assembly of the resources into moki format.

The name of a processing component.

The version of a processing component.

The IP Address of the component generating the moki document.

Since servers may vary the representation of resources based on IP address, this field is significant, though it is understood that address translation (NAT) may be in operation, so the IP address assigned to the component compiling the moki document may not be that received by the remote servers. Where possible, therefore, the address inserted here should be that after address translation.

This element contains information about the primary resource, i.e. the resource that is the subject of the moki document. The element contains details of the document's HTTP retrieval followed by details of the document itself.

Details of the primary document, which is assumed to be an XHTML document.

This element describes validity aspects of the primary document. The "valid" attribute summarises the validity status - it is true if all aspects of validity are true.

The mobileOK Checker incorrectly produces a validity element as a child element of the imageInfo element. It should rather produce an imageValidity element (whose definition it actually respects).

The number of characters in the document and the number of white space characters that are extraneous (as defined in mobileOK Basic Tests MINIMIZE.

Not sure whether the "total" here is different to the "size" of the final HTTP retrieval's body entity.

Details of the XML declaration of the primary document. "declaration" indicates the presence or otherwise of an XML declaration, encoding indicates the declared character encoding, absent if none.

Missing: version? Absent indicates no version declared, present, the version declared.

Details of any DOCTYPE declaration that may be present.

The HTML content of the document, tidied if necessary to make it correct. The original untidied version is found as the entity body of the final HTTP request. The content is tidied if "Validity" of the parent element is false.

We should consider adding a "tidied" attribute to indicate this. Also it would be nice if we allowed for details of which tidy operations were carried out, they may not correspond exactly to the validity errors.

A collection of style sheet information associated with the document.

An aspect of the style sheet information associated with the document - which might be an external style, a style element ("embedded") or "in line" style. The URI element refers to where the reference to the style sheet was found, rather than the URI of the style sheet itself.

POssibly missing here is a more precise reference to where the style was found - especially for "inline".

A collection of the images that were found in the primary document and in the style sheets associated with the primary document (as background or as list item images. The list contains only one reference for each image, caching considerations being equal.

Ideally each image would contain a list of references that caused its retireval.

Information about the retrieved image, its URI, details of its HTTP retrieval and basic image information.

Information about an image. The "type" attribute denotes the Internet Content Type (mime type) of the image. Validity contains information about whether the document is a valid instance of that image type, transparency denotes whether the whole image is transparent, and actualDimensions determines the actual pixel dimensions of images that have an intrinsic size in pixels. Dimensions may be absent for image types that do not support that features.

The mobileOK Checker incorrectly produces a validity child element instead of the imageValidity element it should produce.

The "transparent" attribute is true if all the pixels of an image are transparent.

This would probably be better as an attribute.

The actual dimensions in pixels of images that have an intrinsic size.

A collection of objects found in the document - i.e. the referrent of "object" elements. A resource is only contained once in the list, even if it is referred to multiple times, caching considerations being equal. An image that is referred to as an Object is placed under the images element of a moki document.

It would be worth giving some thought as to whether the images list and the objects list should be combined.

It would be worth giving some thought as to how to represent the dependent relationships between objects.

The referrent of an object element in the primary document.

Ideally, each object would reference where it was found in the referring document.

Contains information about the object:

• the "loadtype" attribute specifies how the object would be handled by browsers:
  • "RENDERED" means the object would be rendered
  • "TASTED" means the object would not be rendered but would need to be retrieved to render the document
  • "SKIPPED" means the object would not be retrieved
• the "type" attribute specifies the Internet Content Type found on retrieval of the object.

All the targets of anchor (<a>) elements found in the primary document.

Should be one element per target and references to where they were found?

Information about the retrieval of a document referenced by hyperlink.