W3C home > Mailing lists > Public > public-bpwg@w3.org > May 2008

Re: ISSUE-251 (mobileOK Algorithms): Differences between the algorithms in OBJECTS_OR_SCRIPT and PAGE_SIZE_LIMIT [mobileOK Basic tests]

From: Jo Rabin <jrabin@mtld.mobi>
Date: Thu, 22 May 2008 18:09:53 +0100
Message-ID: <4835A8E1.3090806@mtld.mobi>
To: Mobile Web Best Practices Working Group WG <public-bpwg@w3.org>

And in response to my ACTION-761, redraft section on Included Resources.

I've proposed text below that clarifies that objects that are tasted and 
discarded are not included resources. I have also straightened out the 
definitions for EXTERNAL RESOURCES and PAGE SIZE LIMIT to be consistent 
with each other and to include objects tasted, but only those that a) 
don't have a type attribute and that b) are image/gif or image/jpeg

I think this now solves the issues that Francois notes ref 
"CONTENT_FORMAT_SUPPORT and VALID_MARKUP" and 
"CHARACTER_ENCODING_SUPPORT and CHARACTER_ENCODING_USE"


=============

Under 2.4.6 Included Resources

* CURRENT TEXT *

Note:

For nested object elements, count only the number of objects that need 
to be assessed as discussed in 3.15 OBJECTS_OR_SCRIPT .

* PROPOSED TEXT *

Note:

For object elements, objects that are accessed in order to test their 
content but that do not form part of the ultimate representation of the 
resource under test (see OBJECTS_OR_SCRIPT) are not considered included 
resources. Their treatment as regards 3.16 PAGE_SIZE_LIMIT and 3.6 
EXTERNAL_RESOURCES is discussed in those sections.

==============

Under 3.6 EXTERNAL_RESOURCES

* CURRENT TEXT *

Make an inventory of unique included resources, as defined in 2.4.6 
Included Resources.

For each such resource:

	Request the resource and carry out the procedures discussed under 2.4.3 
HTTP Response maintaining a running total of requests made. FAILures 
that occur in the course of making this assessment contribute to the 
result of this test.

* PROPOSED TEXT *

Retrieve the resource under test, and add the number of retrievals 
required to obtain the resource (see 2.4.3 HTTP Response) to a running 
total.

For each unique included resource, as defined in 2.4.6 Included Resources:

	Request the referenced resource

	Add the number of HTTP requests that are required to retrieve the 
resource (see 2.4.3 HTTP Response) to the running total.

	Note:

	For object elements count the number of objects retrieved under the 
"Object Element Processing Rule" whose type attribute is not specified, 
and those whose content type is either "image/jpeg" or "image/gif" 
irrespective of whether the type attribute is specified.

==============

Under 3.16 PAGE_SIZE_LIMIT

* CURRENT TEXT *

If the size of the document exceeds 10 kilobytes, FAIL

Add the size to a running total

For each included resource, as defined in 2.4.6 Included Resources:

	Request the referenced resource

	Add the size of the response body to the running total (for object 
elements count the size of objects retrieved under the "Object Element 
Processing Rule" whose type attribute is not specified, and those whose 
content type is either "image/jpeg" or "image/gif" irrespective of 
whether the type attribute is specified)

* PROPOSED TEXT *

If the size of the document under test exceeds 10 kilobytes, FAIL

Add the size to a running total

For each unique included resource, as defined in 2.4.6 Included Resources:

	Request the referenced resource

	Add the size of the response body to the running total

	Note:
	
	For object elements count the size of objects retrieved under the 
"Object Element Processing Rule" whose type attribute is not specified, 
and those whose content type is either "image/jpeg" or "image/gif" 
irrespective of whether the type attribute is specified.


=========

I am minded to alter the wording of 2.4.3 HTTP response where it 
discusses the page size and external resource count:

e.g. "Include the size of the response in the total described under 3.16 
PAGE_SIZE_LIMIT"

to

"Include the size of the response in the total as described under 3.16 
PAGE_SIZE_LIMIT"

i.e. add the word "as", since this is a minor change indeed.




On 22/05/2008 14:49, Mobile Web Best Practices Working Group Issue 
Tracker wrote:
> ISSUE-251 (mobileOK Algorithms): Differences between the algorithms in OBJECTS_OR_SCRIPT and PAGE_SIZE_LIMIT [mobileOK Basic tests]
> 
> http://www.w3.org/2005/MWI/BPWG/Group/track/issues/
> 
> Raised by: Jo Rabin
> On product: mobileOK Basic tests
> 
> This in response to my ACTION-758 Raise an Issue on the differences between the algorithms in OBJECTS_OR_SCRIPT and PAGE_SIZE_LIMIT
> 
> Please see also the excellent post by Francois [1] whi9ch relates to this:
> [1] http://lists.w3.org/Archives/Public/public-bpwg/2008May/0018.html
> 
> The issue is this - in OBJECTS_OR_SCRIPT we say that the checker should check every object, irrespective of whether the Object element has a type attribute. This is because some browsers ignore the type attribute.
> 
> On the other hand, in PAGE_SIZE_LIMIT, we say that if the type attribute is specified and the content is irrelevant then, because some browsers take account of the type attribute, it's not fair to count that resource.
> 
> The logic is to be both safe and generous. I think, modulo FD's comments, that the logic is OK, but a little bit more word-smithing may be needed to make the document completely consistent.
> 
> Additionally, the latest OBJECTS_OR_SCRIPT algorithm needs careful checking, it's not the one we agreed as the new one, as that was broken, as was the one we originally published. This is obviously something that is hard to get right, and ideally we need a resolution that the new one is correct. 
> 
> OBJECTS_OR_SCRIPT
> 
> 3.15.1 Object Element Processing Rule
>    
> For each object element that has no object element ancestor in this context (excepting the context node itself):
> 
>   Retrieve the object (ignoring the type attribute)
> 
>   If the content type of the retrieved object is not "image/jpeg" or "image/gif"
> 
>     If the object element is empty, warn
> 
>     If the content of the object element consists only of white space, FAIL
> 
>     For each img element that has no object element ancestor in this context:
> 
>       If the content type of the img element is not "image/jpeg" or "image/gif", FAIL
> 
>     Reapply this rule using the current object element as the context
> 
> 
> PAGE_SIZE_LIMIT
> 
> For each included resource, as defined in 2.4.6 Included Resources:
> 
>   Request the referenced resource
> 
>   Add the size of the response body to the running total (for object elements count the size of objects retrieved under the "Object Element Processing Rule" whose type attribute is not specified, and those whose content type is either "image/jpeg" or "image/gif" irrespective of whether the type attribute is specified)
> 
> If the total exceeds 20 kilobytes, FAIL 
> 
> 
> 
> 
Received on Thursday, 22 May 2008 17:11:11 UTC

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