W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > July 2008

Moki objectInfo attributes joined

From: Miguel Garcia <miguel.garcia@fundacionctic.org>
Date: Thu, 3 Jul 2008 08:58:52 +0200
Message-ID: <09700B613C4DD84FA9F2FEA52188281903CEC0F8@ayalga.fundacionctic.org>
To: "public-mobileok-checker" <public-mobileok-checker@w3.org>


As agreed on last call instead of using a list of boolean attributes
(tasted,rendererd,isEmpty,isBlank,hasInvalidImage) in objectInfo element
we should join them (in two different attributes) and use a enumeration
of posibles values.

Tasted and rendered attributes are joined in "loadtype":
 - loadtype="TASTED": the object resource has been tasted it will count
against PageSizeLimit and ExternalResources but it won't be displayed so
its nested elements will be processed.
 - loadtype="RENDERED": the object resource will be displayed (is
supported by the device), of course it will count against both test but
nested elements won't be processed.
 - loadtype="SKIPPED": the object resource isn't tasted nor rendered (an
object that isn't supported and its mime type is clearly stated on
markup by the type attribute), in this case children elements will be

The other attributes (isEmpty,isBlank,hasInvalidImage) are joined in
 - content="EMPTY": the object body is empty (has no content).
 - content="BLANK": the object body consists only of white spaces.
 - content="IMAGE_INVALID": the object body has at least one invalid
 - content="HAS_CONTENT": the object body has a valid content which
could be some text or/and valid images.

"HAS_CONTENT" value could be splitted into different pass values (TEXT,
IMAGE_VALID, MIXED,...) but I think there is no gain having different
values to specify if the test pass because it has text or it has a valid

Received on Thursday, 3 July 2008 06:59:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:21:20 UTC