Edit comment LC-1464 for Mobile Web Best Practices Working Group

Quick access to LC-1464 LC-1465 LC-1466 LC-1467 LC-1468

Comment LC-1464

Comment Shortname:

Commenter: Susan Lesch <lesch@w3.org>

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeW3C mobileOK Scheme 1.0 /**/ code { font-fami... W3C mobileOK Scheme 1.0 W3C Working Draft 12 July 2006 Abstract Status of this Document Revision Description Table of Contents Appendices 1 Overview 1.1 What is mobileOK? 1.2 Why mobileOK? 1.3 Who is mobileOK for? 1.4 Form of the mobileOK label 1.4.1 Verification and Trustability 1.4.2 Asserting Compliance with Individual Tests 1.4.3 Visual Representation 1.5 Requirements 2 mobileOK Label Test Suites 2.1 Testing Parameters 2.1.1 HTTP Request 2.2 mobileOK Level 1 2.2.1 AUTO_REFRESH (partial) 2.2.2 CHARACTER_ENCODING_SUPPORT 2.2.3 CHARACTER_ENCODING_USE 2.2.4 CONTENT_FORMAT_SUPPORT 2.2.5 DEFAULT_INPUT_MODE 2.2.6 EXTERNAL_RESOURCES 2.2.7 GRAPHICS_FOR_SPACING 2.2.8 IMAGE_MAPS 2.2.9 IMAGES_RESIZING 2.2.10 IMAGES_SPECIFY_SIZE 2.2.11 LARGE_GRAPHICS 2.2.12 LIMITED 2.2.13 LINK_TARGET_FORMAT 2.2.14 MEASURES 2.2.15 NO_FRAMES 2.2.16 NON-TEXT_ALTERNATIVES (partial) 2.2.17 OBJECTS_OR_SCRIPT (partial) 2.2.18 PAGE_SIZE_LIMIT 2.2.19 PAGE_SIZE_USABLE 2.2.20 PAGE_TITLE (partial) 2.2.21 POP_UPS 2.2.22 PROVIDE_DEFAULTS 2.2.23 REDIRECTION 2.2.24 STYLE_SHEETS_SIZE 2.2.25 STYLE_SHEETS_USE 2.2.26 TABLES_ALTERNATIVES 2.2.27 TABLES_LAYOUT (partial) 2.2.28 TABLES_NESTED 2.2.29 TABLES_SUPPORT 2.2.30 VALID_MARKUP 2.3 mobileOK Level 2 2.3.1 ACCESS_KEYS (partial) 2.3.2 AVOID_FREE_TEXT 2.3.3 BACKGROUND_IMAGE_READABILITY 2.3.4 CACHING 2.3.5 COLOR_CONTRAST 2.3.6 CONTENT_FORMAT_PREFERRED 2.3.7 CONTROL_LABELLING 2.3.8 CONTROL_POSITION 2.3.9 COOKIES 2.3.10 ERROR_MESSAGES 2.3.11 FONTS 2.3.12 LINK_TARGET_ID 2.3.13 MINIMIZE 2.3.14 MINIMIZE_KEYSTROKES 2.3.15 NAVBAR 2.3.16 NAVIGATION 2.3.17 SCROLLING (partial) 2.3.18 STRUCTURE 2.3.19 STYLE_SHEETS_SUPPORT 2.3.20 TAB_ORDER 2.3.21 USE_OF_COLOR 2.4 Best Practices Outside mobileOK Scope 3 Label Technical Specification A Use Cases (Non-Normative) A.1 Certification Provider A.2 Content Adaptation A.3 Content Syndication / Aggregator A.4 Individual Content Author A.5 Search Engine A.6 Software Developer A.7 Operator A.8 Accepting or Rejecting a mobileOK claim B Acknowledgements (Non-Normative) C References (Non-Normative) BestPractices Techniques WCL RDF EARL
or

Refinement of the section concerned:

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Nobody

Type: substantive editorial typo question general comment undefined

Comment:

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

Related issues: (space separated ids)

WG Notes: (Following up for the tracker) I replied on 7/28 with the following. If anything, the open question is whether to supply both an image and CSS-styled logo in the final labels spec later. "If the final mobileOK logo is substantially just text, then I agree that an alternate CSS version could useful. I am not sure if the W3C has guidelines or policies on this but it sounds reasonable to me. I am not a lawyer, though I suspect the term "mobileOK" will have the usual appropriate set of legal protections. We will make sure that the appropriate marks appears on the logo. The logo itself does not necessarily need to be hard to forge, but rather the machine-readable label -- you read it right. Thanks as always, Sean"

Resolution:

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