W3C

List of comments on “W3C mobileOK Scheme 1.0” (dated 12 July 2006)

Quick access to

There are 5 comments (sorted by their types, and the section they are about).

general comment comments

Comment LC-1464
Commenter: Susan Lesch <lesch@w3.org> (archived message)
Context: 1.4.3 Visual Representation
n the mobileOK 1.0 draft, label [1] appears to be the source of
authenticity. Have you considered a lightweight text-based logo styled
in CSS? From 1.4.3 Visual Representation [2]:

"Content which bears a mobileOK label may optionally advertise this
by displaying a mobileOK logo (to be produced)..."

The example below condensed is about 200 bytes. A CSS expert can improve
on that no doubt. :-). I don't know if the mobileOK mark is meant to be
a service mark, or a trademark or if the strings would need to be
protected by patent, copyright or trade or service mark registration.
Apologies in advance if I misunderstood, and the spec means that the
logo itself needs to be hard to forge.

<a id="mobileOK"
href="http://www.example.com/mobileOK/#id4485358">mobileOKâ„¢</a>

a#mobileOK {
margin-left: 0;
padding: 0.05% 0.3%;
background: #fff;
color: #093;
text-decoration: none;
font: bold smaller sans-serif;
}

[1] http://www.w3.org/TR/mobileOK/#id4477838
[2] http://www.w3.org/TR/mobileOK/#id4485358
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1466
Commenter: Dan Connolly <connolly@w3.org> (archived message)
Context: 2.2.2 CHARACTER_ENCODING_SUPPORT
assigned to Sean Owen
Resolution status:

I see:

"If the request response does specify a character encoding but it is not
"UTF-8", FAIL"
-- http://www.w3.org/TR/mobileOK/#id4485785

How about US-ASCII? especially since you can treat US-ASCII
as UTF-8 and preserve the meaning of the bytes.

It's perhaps not worthwhile to complicate things, if very
few documents are labelled US-ASCII.

p.s. I wonder if it's acceptable to limit encodings to UTF-8
and exclude UTF-16; it wasn't when XML was ratified.
But I'll leave it to those who have 1st-hand experience
with the need for UTF-16 to comment on that.

p.p.s. The fragid #id4485785 seems fragile. If you're
going to break it, break it only once, for the next draft.
At that point, change it to something like #char-encoding-support
and keep it that way for future revisions.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

editorial comments

Comment LC-1465
Commenter: Susan Lesch <lesch@w3.org> (archived message)
Context: 2 mobileOK Label Test Suites (comments on CSS usage)
assigned to Sean Owen
Resolution status:

(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1467
Commenter:
Context: 2.2.4 CONTENT_FORMAT_SUPPORT
assigned to Sean Owen
Resolution status:

(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1468
Commenter: Susan Lesch <lesch@w3.org> (archived message)
Context: 2.2.4 CONTENT_FORMAT_SUPPORT
assigned to Sean Owen
Resolution status:

Hello,

Congratulations on your First Public Working Draft [1] for mobileOK. A
comment for 2.2:

"If the document's MIME type, as specified in the HTTP response
Content-Type header, is not application/vnd.wap.xhtml+xml or
application/xhtml+wml , FAIL"

These are called Internet Media Types (rather than MIME I think) and are
not registered. Are you planning to register them?

I am not an expert but am checking to see if mobileOK requires XHTML
Basic and Basic requires application/xhtml+xml.

"If the document's DOCTYPE's PUBLIC identifier is not an XHTML
Basic identifier (at present, "-//W3C//DTD XHTML Basic 1.1//EN" or
"-//W3C//DTD XHTML Basic 1.0//EN"), FAIL"

In case the references help, the topic came up in March of 2004 on two
different W3C lists [2,3].

[1] http://www.w3.org/TR/2006/WD-mobileOK-20060712/
[2] http://lists.w3.org/Archives/Public/www-validator/2004Mar/0001
[3] http://lists.w3.org/Archives/Public/www-archive/2004Mar/0000

Hope this helps,
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Add a comment.


Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: Overview.php,v 1.46 2013-10-04 08:11:33 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org