You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
335 lines
19 KiB
335 lines
19 KiB
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
|
<head>
|
|
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
|
|
<title>W3C mobileOK Scheme 1.0</title>
|
|
<style type="text/css">
|
|
/*<![CDATA[*/
|
|
code { font-family: monospace; }
|
|
|
|
div.constraint,
|
|
div.issue,
|
|
div.note,
|
|
div.notice { margin-left: 2em; }
|
|
|
|
ol.enumar { list-style-type: decimal; }
|
|
ol.enumla { list-style-type: lower-alpha; }
|
|
ol.enumlr { list-style-type: lower-roman; }
|
|
ol.enumua { list-style-type: upper-alpha; }
|
|
ol.enumur { list-style-type: upper-roman; }
|
|
|
|
p.pseudocode1 {text-indent: 0.1in}
|
|
p.pseudocode2 {text-indent: 0.2in}
|
|
p.pseudocode3 {text-indent: 0.3in}
|
|
p.pseudocode4 {text-indent: 0.4in}
|
|
|
|
|
|
div.exampleInner pre { margin-left: 1em;
|
|
margin-top: 0em; margin-bottom: 0em}
|
|
div.exampleOuter {border: 4px double gray;
|
|
margin: 0em; padding: 0em}
|
|
div.exampleInner { background-color: #d5dee3;
|
|
border-top-width: 4px;
|
|
border-top-style: double;
|
|
border-top-color: #d3d3d3;
|
|
border-bottom-width: 4px;
|
|
border-bottom-style: double;
|
|
border-bottom-color: #d3d3d3;
|
|
padding: 4px; margin: 0em }
|
|
div.exampleWrapper { margin: 4px }
|
|
div.exampleHeader { font-weight: bold;
|
|
margin: 4px}
|
|
|
|
.ednote {background: #90EE90; border: 1px solid black;}
|
|
#img_mobileOK_Logo {margin: 1em; float: right;}
|
|
/*]]>*/</style>
|
|
<link rel="stylesheet" type="text/css"
|
|
href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE.css" />
|
|
</head>
|
|
|
|
<body>
|
|
|
|
<div class="head">
|
|
<p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home"
|
|
alt="W3C" height="48" width="72" /></a></p>
|
|
|
|
<h1><a name="title" id="title"></a>W3C mobileOK Scheme 1.0</h1>
|
|
|
|
<h2 id="Editor"><a name="w3c-doctype" id="w3c-doctype"></a>W3C Working Group Note 25 August 2009</h2>
|
|
<dl>
|
|
<dt>This version:</dt>
|
|
<dd><a href="http://www.w3.org/TR/2009/NOTE-mobileOK-20090825/">http://www.w3.org/TR/2009/NOTE-mobileOK-20090825/</a></dd>
|
|
<dt>Latest version:</dt>
|
|
<dd><a href="http://www.w3.org/TR/mobileOK/">http://www.w3.org/TR/mobileOK/</a></dd>
|
|
<dt>Previous version:</dt>
|
|
<dd><a href="http://www.w3.org/TR/2009/NOTE-mobileOK-20090625/">http://www.w3.org/TR/2009/NOTE-mobileOK-20090625/</a></dd>
|
|
<dt>Editors:</dt>
|
|
<dd>Jo Rabin, dotMobi (mTLD Mobile Top Level Domain Limited)</dd>
|
|
<dd>Phil Archer, Institute of Informatics & Telecommunications (IIT), NCSR "Demokritos" (and previously with FOSI)</dd>
|
|
</dl>
|
|
|
|
<p class="copyright"><a
|
|
href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2009
|
|
|
|
<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup>
|
|
(<a href="http://www.csail.mit.edu/"><acronym
|
|
title="Massachusetts Institute of Technology">MIT</acronym></a>, <a
|
|
href="http://www.ercim.org/"><acronym
|
|
title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
|
|
<a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a
|
|
href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
|
|
<a
|
|
href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>
|
|
and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document
|
|
use</a> rules apply.</p>
|
|
|
|
</div>
|
|
<hr />
|
|
|
|
<h2 id="sec-Abstract">Abstract</h2>
|
|
|
|
<p>The mobileOK scheme allows content providers to promote their content as being suitable
|
|
for use on <em>very basic</em> mobile devices. This document provides an overview of the scheme and
|
|
references the documentation that composes it.</p>
|
|
|
|
<div>
|
|
<h2 id="sec-Status">Status of this Document</h2>
|
|
|
|
<p><em>This section describes the status of this document at the time of its
|
|
publication. Other documents may supersede this document. A list of current
|
|
W3C publications and the latest revision of this technical report can be
|
|
found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a>
|
|
at http://www.w3.org/TR/.</em></p>
|
|
|
|
<p>This is a public Working Group Note of the W3C mobileOK Scheme. It follows a period of
|
|
evolution during which the Working Group considered defining two levels of mobileOK
|
|
conformance, each with its own set of tests. mobileOK is presented here as a
|
|
simplified and unified scheme in which the relationship with the <a href="#bp">Best Practices</a>
|
|
document, the <a href="#basic">Basic Tests</a> and the <a href="#check">Checker</a> is made explicit. The only change since last
|
|
publication in <a href="http://www.w3.org/TR/2009/NOTE-mobileOK-20090625/" title="25 June 2009 version of W3C mobileOK Scheme 1.0 document">June 2009</a>
|
|
is the correction of the Media Type for POWDER in sections <a href="#linkingClaims">2.2.2</a> and <a href="#linkingClaimsHTTP">2.2.3</a>. A <a href="diff.html">complete list of earlier changes</a> is available.
|
|
The Working Group does not expect further versions of this document.</p>
|
|
|
|
<p>Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p>
|
|
|
|
<p>This document has been produced by the <a
|
|
href="http://www.w3.org/2005/MWI/BPWG/">Mobile Web Best Practices Working
|
|
Group</a> as part of the <a href="http://www.w3.org/2005/MWI/Activity">Mobile
|
|
Web Initiative</a>. Please send comments on this document to the working
|
|
group's public email list <a
|
|
href="mailto:public-bpwg-comments@w3.org">public-bpwg-comments@w3.org</a> , a
|
|
<a href="http://lists.w3.org/Archives/Public/public-bpwg-comments/">publicly
|
|
archived mailing list</a>.</p>
|
|
|
|
<p>This document was produced by a group operating under the <a
|
|
href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004
|
|
W3C Patent Policy</a>. W3C maintains a <a rel="disclosure"
|
|
href="http://www.w3.org/2004/01/pp-impl/37584/status">public list of any
|
|
patent disclosures</a> made in connection with the deliverables of the group;
|
|
that page also includes instructions for disclosing a patent. An individual
|
|
who has actual knowledge of a patent which the individual believes contains
|
|
|
|
<a
|
|
href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
|
|
Claim(s)</a> must disclose the information in accordance with <a
|
|
href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
|
|
6 of the W3C Patent Policy</a>.</p>
|
|
</div>
|
|
|
|
<h2 id="sec-Contents"><a name="contents" id="contents"></a>Table of Contents</h2>
|
|
|
|
<div class="toc">
|
|
<ul>
|
|
<li><a href="#sec-mobileOK_Scheme">1 The mobileOK Scheme</a>
|
|
<ul>
|
|
|
|
<li><a href="#sec_mobileOK_Basic_Tests">1.1 mobileOK Basic Tests 1.0</a></li>
|
|
<li><a href="#sec_Mobile_Web_Best_Practices">1.2 Mobile Web Best Practices 1.0</a></li>
|
|
<li><a href="#sec_Default_Delivery_Context">1.3 The Default Delivery Context</a></li>
|
|
<li><a href="#sec_mobileOK_Checker">1.4 mobileOK Checker</a></li>
|
|
</ul></li>
|
|
<li><a href="#sec_Claiming_Conformance">2 Claiming Conformance</a>
|
|
|
|
<ul><li><a href="#sec_mobileOK_Icon">2.1 The mobileOK Icon</a></li>
|
|
<li><a href="#sec_mobileOK_Labels">2.2 Machine Readable Identification</a></li>
|
|
</ul>
|
|
</li>
|
|
<li><a href="#sec-Acknowledgements">3 Acknowledgements</a></li>
|
|
<li><a href="#sec-References">4 References</a></li>
|
|
</ul>
|
|
|
|
</div>
|
|
<hr />
|
|
|
|
<h2 id="sec-mobileOK_Scheme">1. The mobileOK Scheme</h2>
|
|
|
|
<p>mobileOK is designed to improve the Web experience for users of mobile devices
|
|
by rewarding content providers that adhere to good practice when
|
|
delivering content to them.</p>
|
|
<p>mobileOK says nothing about what may be delivered to non-mobile devices; furthermore, 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, is or is not
|
|
appropriate for children etc.</p>
|
|
<h3 id="sec_mobileOK_Basic_Tests">1.1 mobileOK Basic Tests 1.0</h3>
|
|
<p>mobileOK Basic Tests 1.0 [<a href="#basic">mobileOK</a>] specifies a number of tests that HTTP responses must pass when
|
|
a URI is requested with a specific set of HTTP headers in the request. The tests are designed to be machine processable and to provide confidence that content will display well on <em>very basic</em> mobile devices. </p>
|
|
|
|
<h3 id="sec_Mobile_Web_Best_Practices">1.2 Mobile Web Best Practices 1.0</h3>
|
|
<p>mobileOK Basic Tests 1.0 is itself based on Mobile Web Best Practices 1.0 [<a href="#bp">BP</a>], which provides a set of sixty guidelines for making content work well across a wide variety of mobile devices.</p>
|
|
<h3 id="sec_Default_Delivery_Context">1.3 The Default Delivery Context</h3>
|
|
<p>The HTTP Request headers used in mobileOK Basic Tests 1.0 identify a hypothetical user agent called the "Default Delivery Context" (DDC).
|
|
The values of the key properties of the DDC (screen width, formats supported and other basic characteristics) are set at the minimum possible, while still supporting a Web experience.</p>
|
|
<p>The DDC is thus not a target to aspire to, it merely sets a base line below which content providers do not need to provide their content.
|
|
It is Best Practice (see Best Practice <a href="http://www.w3.org/TR/mobile-bp/#CAPABILITIES">[CAPABILITIES]</a>) for content providers, as well as
|
|
targetting DDC level devices, also to provide experiences for more
|
|
advanced mobile devices that have capabilities not supported by the DDC.</p>
|
|
|
|
<h3 id="sec_mobileOK_Checker">1.4 mobileOK Checker</h3>
|
|
|
|
<p>A software package called the mobileOK Checker [<a href="#check">CHECK</a>], has been developed by the Best Practices Working Group to provide automated checking of conformance. The package is in Java, and is open source. It is available under a <a href="http://dev.w3.org/cvsweb/~checkout~/2007/mobileok-ref/LICENSE.html?rev=1.1&content-type=text/html;%20charset=iso-8859-1">W3C License</a>.</p>
|
|
<p>W3C has created a <a href="http://validator.w3.org/mobile">Web interface</a> as part of the <a href="http://validator.w3.org">W3C Validator</a>, which uses this package. Other Web based checkers, by dotMobi (see <a href="http://ready.mobi">ready.mobi</a>) and CTIC (see <a href="http://validadores.tawdis.net/mobileok/en/">TAWDIS</a>) have also been created that adhere to the mobileOK Basic Tests 1.0 [<a href="#basic">mobileOK</a>].</p>
|
|
|
|
<h2 id="sec_Claiming_Conformance">2 Claiming Conformance</h2>
|
|
|
|
<p>Content Providers may wish to identify that their content is mobileOK conformant. This means that it can be requested so that
|
|
the response conforms to mobileOK Basic Tests 1.0 [<a href="#basic">mobileOK</a>] and hence will provide at least a
|
|
<a href="http://www.w3.org/TR/2003/WD-di-gloss-20030825/#def-functional-user-experience">functional user experience</a> on mobile devices.
|
|
A claim may only be made of a URI that when dereferenced in the manner described in [<a href="#basic">mobileOK</a>] yields a response that passes all the tests contained in mobileOK Basic Tests 1.0. Such a claim says nothing about other experiences that may be provided at the same URI, when dereferenced in a different way (e.g. with different User-Agent and Accept HTTP headers).</p>
|
|
<h3 id="sec_mobileOK_Icon">2.1 The mobileOK Icon</h3>
|
|
<p><img id="img_mobileOK_Logo" src="http://www.w3.org/2005/11/MWI-Icons/mobileOK.png" alt="mobileOK Logo" />
|
|
W3C provides a mobileOK icon that represents a claim that
|
|
the content on which the icon is found is mobileOK conformant as described above.</p>
|
|
|
|
<p>The icon is most appropriately used on desktop representations
|
|
of a resource for which a mobileOK representation is also available. In such a situation it
|
|
acts as a signal to a desktop user that the content or service they are using is also
|
|
available on a mobile device. Display of the mobileOK icon is usually inappropriate on
|
|
a mobile device since whether the content is usable on their device or not will be
|
|
fully apparent without it.</p>
|
|
<p>When displaying a mobileOK icon, the image should be served from the same server as the resource, not from the W3C site.
|
|
Note that the image is provided in PNG format which is a further reason why it is not suitable for use on mobileOK representations of pages, though it may be used on other representations.</p>
|
|
|
|
<p>The icon is issued under W3C copyright and may only be used in accordance with the W3C mobileOK license [<a href="#license">LICENSE</a>], the key
|
|
feature being that it may only be used in representations of resources that, when dereferenced in accordance with the mobileOK Basic Tests 1.0, pass those tests.</p>
|
|
<h3 id="sec_mobileOK_Labels">2.2 Machine Readable Identification</h3>
|
|
<p>To enhance discoverability of mobileOK content, providers may wish to identify their material as being mobileOK using POWDER (see <a href="#powderClaim">Claiming mobileOK Conformance Using POWDER</a>). Content should then be linked to a claim as described in <a href="#linkingClaims">2.2.3 Linking Resources to Claims</a>.</p>
|
|
|
|
|
|
<h4 id="powderClaim">2.2.1 Claiming mobileOK Conformance Using POWDER</h4>
|
|
<p>The Protocol for Web Description Resources [<a href="#powder">POWDER</a>] provides a means through
|
|
which a claim of mobileOK conformance may be made about many resources at once, such as all
|
|
those available from a Web site. Importantly, POWDER also provides a means of identifying the
|
|
person, organization or entity that made the claim. These two features make POWDER's Description
|
|
Resources an ideal transport mechanism for mobileOK conformance claims (mobileOK was a key use
|
|
case for POWDER).</p>
|
|
|
|
<p>In the following (fictitious) example, on 25th June 2008 (line 5), the organization described at
|
|
http://www.example.com/company.rdf#me (line 4) claimed that all the resources available from example.com (lines 9-11)
|
|
were mobileOK (line 13). This makes use of a one-class RDF vocabulary with namespace
|
|
http://www.w3.org/2008/06/mobileOK# and class name <code>Conformant</code>.</p>
|
|
<div>
|
|
<pre>
|
|
1 <?xml version="1.0"?>
|
|
|
|
2 <powder xmlns="http://www.w3.org/2007/05/powder#">
|
|
|
|
3 <attribution>
|
|
4 <issuedby src="http://www.example.com/company.rdf#me" />
|
|
5 <issued>2008-06-25T00:00:00</issued>
|
|
|
|
6 <supportedby src="http://example.net/checker/" />
|
|
7 </attribution>
|
|
|
|
8 <dr>
|
|
9 <iriset>
|
|
10 <includehosts>example.com</includehosts>
|
|
|
|
11 </iriset>
|
|
|
|
12 <descriptorset>
|
|
13 <typeof src="http://www.w3.org/2008/06/mobileOK#Conformant" />
|
|
14 <displaytext>The example.com webiste conforms to mobileOK</displaytext>
|
|
|
|
15 <displayicon src="http://www.example.com/images/mobileOK.png" />
|
|
16 </descriptorset>
|
|
17 </dr>
|
|
|
|
18 </powder></pre>
|
|
</div>
|
|
|
|
<p>http://www.example.com/company.rdf#me (line 4) should lead to an RDF resource that describes the
|
|
entity (either the <a href="http://xmlns.com/foaf/spec/#term_Agent"><code>foaf:Agent</code></a> or
|
|
<a href="http://purl.org/dc/terms/Agent"><code>dcterms:Agent</code></a>) that provided the Description
|
|
Resource. It is open to that organization to provide authentication methods to support its claim of
|
|
mobileOK conformance. Note also in line 6 that POWDER's <code>supportedby</code> element has been used
|
|
to refer to http://example.net/checker/, the implication being that the content of the described Web site has
|
|
been tested using that checker. Lines 14 and 15 provide textual and graphical data that user agents may
|
|
display to end users.</p>
|
|
<h4 id="linkingClaims">2.2.2 Linking Resources to Claims using the HTML <code>link</code> Element</h4>
|
|
<p>All mobileOK resources are HTML. In the following example a powder document is linked using the <code>link</code> element (line 3). The value of the <code>rel</code> attribute, "describedby" is namespaced by the <code>profile</code> attribute of the <code>head</code> element (line 2) in versions of HTML that support it.</p>
|
|
|
|
<div><pre>
|
|
1 <html xmlns="http://www.w3.org/1999/xhtml">
|
|
2 <head profile="http://www.w3.org/2007/11/powder-profile">
|
|
3 <link rel="describedby" href="powder.xml" type="application/powder+xml"/>
|
|
4 <title>Welcome to example.com </title>
|
|
5 </head>
|
|
6 <body>
|
|
7 <p>Today's content is ....</p>
|
|
8 </body>
|
|
9 </html>
|
|
</pre>
|
|
</div>
|
|
|
|
|
|
<h4 id="linkingClaimsHTTP">2.2.3 Linking Resources to Claims using the HTTP <code>link</code> Header</h4>
|
|
|
|
<p>In many application environments it can also be appropriate to use HTTP Link [<a href="#httpLink">HTTP Link</a>] headers. The following header is semantically equivalent to the HTML link header above.</p>
|
|
|
|
<pre>Link: <powder.xml>; rel="describedby" type="application/powder+xml";</pre>
|
|
|
|
|
|
<h4 id="otherClaims">2.2.4 Other Forms of Claim</h4>
|
|
|
|
<p>Other machine readable means of making a claim of mobileOK conformance are available. For example the following RDF triple asserts that the URI <var>http://example.com</var> is mobileOK conformant:</p>
|
|
<p><code><<var>http://example.com</var>> rdf:type < http://www.w3.org/2008/06/mobileOK#conformant></code></p>
|
|
<p>Other forms of expressing a claim may become available in the future.</p>
|
|
<h2 id="sec-Acknowledgements">3. Acknowledgements</h2>
|
|
|
|
<p>The editors would like to thank members of the BPWG for contributions of
|
|
various kinds.</p>
|
|
<dl>
|
|
<dt>Previous Editors:</dt>
|
|
<dd>Sean Owen, Google</dd>
|
|
<dd>Charles McCathieNevile, <a href="http://www.opera.com">Opera Software</a></dd>
|
|
</dl>
|
|
|
|
<h2 id="sec-References">4. References </h2>
|
|
|
|
<dl>
|
|
<dt class="label" id="bp">BP</dt>
|
|
<dd><cite><a href="http://www.w3.org/TR/mobile-bp/">Mobile Web Best Practices 1.0</a></cite>, Jo Rabin, Charles McCathieNevile, W3C Recommendation 29 July 2008</dd>
|
|
|
|
<dt class="label" id="basic">BASIC</dt>
|
|
<dd><cite><a href="http://www.w3.org/TR/mobileOK-basic10-tests/">W3C mobileOK Basic Tests 1.0</a></cite>, Sean Owen, Jo Rabin. W3C Recommendation 8 December 2008</dd>
|
|
|
|
<dt class="label" id="check">CHECK</dt>
|
|
<dd><cite><a href="http://dev.w3.org/cvsweb/2007/mobileok-ref/">W3C mobileOK Checker</a></cite>, BPWG Checker Task Force</dd>
|
|
|
|
|
|
<dt class="label" id="license">LICENSE</dt>
|
|
<dd><cite><a href="http://www.w3.org/Consortium/Legal/2008/04-mobileok-policy.html">W3C mobileOK License</a></cite></dd>
|
|
<dt class="label" id="powder">POWDER</dt>
|
|
|
|
<dd><cite><a href="http://www.w3.org/TR/powder-dr/">Protocol for Web Description Resources (POWDER): Description Resources</a></cite>, Phil Archer, Kevin Smith, Andrea Perego, W3C Proposed Recommendation, 4 June 2009</dd>
|
|
<dt class="label" id="httpLink">HTTP Link</dt>
|
|
<dd><cite><a href="http://tools.ietf.org/html/draft-nottingham-http-link-header-05">
|
|
Web Linking</a></cite>, Mark Nottingham, Internet Draft, 17 April 2009 (expires 19 October 2009, expected to advance to RFC status)</dd>
|
|
|
|
</dl>
|
|
|
|
|
|
|
|
</body>
|
|
</html>
|