Hi,
This is kind of a stupid feedback, but I think I should mention it since
I have
now faced the problem several times.....
I have gotten a lot of feedback from people who have misunderstood that
the MOK Basic
test doc is setting requirements for a mobile web browser, like for
example people are
wondering why in 2.3.2 http://www.w3.org/TR/mobileOK-basic10-
tests/#http_request
we define such a limited HTTP Request etc....
So I have had to explain people that this doc is about defining how a
web site can be tested
for it's ability to deliver content based on the limitations set forth
by DDC and selected BPs
we chose to test. Meaning that the doc is about how to exercise a web
site with an imaginary
DDC client which MOK tester pretends to be to see if indeed the web site
can deliver MOK
content. Also I needed to make it clear to them that the doc is NOT
about testing a mobile
browser for MOK or setting any requirements to a mobile browser.....
I wonder if we should somewhere in the doc, like on the Abstract or on
the Introduction make it
clear that MOK is not about testing a mobile browser or setting any
requirements for it, but it is
about testing a web site and setting requirements for it.
Or maybe people providing me feedback are ignorant enough not to read
the doc in enough details...
-------------
Jo Rabin says:
I agree that if this is a common misconception then that misconception
should be put to rest. However, I think that what is missing is mainly a
statement of what mobileOK _is_ rather than a statement about what it is
_not_.
Also under 1.3 Claiming mobileOK conformance, we say "mobileOK does not
imply endorsement or suitability ... or is appropriate for children".
That statement is actually out of place (in that it is not about
claiming mobileOK conformance), so we should move it and put it with a
"not user agent test" disclaimer, to a proper section.
I think the right place is in section 1 Introduction. I suggest:
Current Text:
This document describes W3C mobileOK Basic tests, which are based on
Mobile Web Best Practices [BestPractices].
mobileOK Basic is the lesser of two levels of claim, the greater level
being mobileOK (W3C mobileOK?), described separately. Claims to be W3C
mobileOK Basic are represented using content labels, also described
separately.
The intention of mobileOK is to help catalyze development of Web sites
that provide a functional user experience in a mobile context.
Proposed Text:
mobileOK is a scheme for assessing whether Web resources (Web pages) can
be delivered in a manner that is conformant with Mobile Web Best
Practices [BestPractices].
This document describes W3C mobileOK Basic tests. mobileOK Basic is the
lesser of two levels of claim, the greater level being mobileOK (W3C
mobileOK?), described separately. Claims to be W3C mobileOK Basic are
represented using content labels, also described separately.
The intention of mobileOK is to help catalyze development of Web sites
that provide a functional user experience in a mobile context.
mobileOK does not imply endorsement or suitability of content. For
example, it must not be assumed that mobileOK content is of higher
informational value, is more reliable, more trustworthy or is
appropriate for children.
mobileOK is not a test for user agents and is not intended to imply
anything about the way that user agents should behave.
---------------------
Yes, thanks, I think there is an important aspect of Sean's proposal
that I missed out which is that the DDC needs significant mention. I
don't think that the tests 'emulate a request' as such. Rather they
describe how to emulate the DDC when making a request and how to assess
content delivered as a result.
So forgive me but I have a further elaboration:
Proposed Text:
mobileOK Basic is a scheme for assessing whether Web resources (Web
content) can be delivered in a manner that is conformant with Mobile Web
Best Practices [BestPractices] to a simple and largely hypothetical
mobile user agent, the Default Delivery Context [DDC].
This document describes W3C mobileOK Basic tests for delivered content,
and describes how to emulate the DDC when requesting that content.
mobileOK Basic is the lesser of two levels of claim, the greater level
being mobileOK (W3C mobileOK?), described separately. Claims to be W3C
mobileOK Basic are represented using content labels, also described
separately.
The intention of mobileOK is to help catalyze development of Web content
that provides a functional user experience in a mobile context. It is
not a test for browsers, user agents or mobile devices, and is not
intended to imply anything about the way these should behave.
mobileOK does not imply endorsement or suitability of content. For
example, it must not be assumed that mobileOK content is of higher
informational value, is more reliable, more trustworthy or is
appropriate for children.