index.html
36.4 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US"><head><title>Device Description Repository Core Vocabulary</title><style type="text/css">
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; }
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}
</style><link rel="stylesheet" type="text/css" href="additional.css"/><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE.css"/></head><body><div class="head">
<a href="http://www.w3.org/"><img height="48" width="72" alt="W3C" src="http://www.w3.org/Icons/w3c_home"/></a>
<h1><a name="title" id="title"/>Device Description Repository Core Vocabulary</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"/>W3C Working Group Note 14 April 2008</h2><dl><dt>This version:</dt><dd>
<a href="http://www.w3.org/TR/2008/NOTE-ddr-core-vocabulary-20080414/">http://www.w3.org/TR/2008/NOTE-ddr-core-vocabulary-20080414/</a>
</dd><dt>Latest version:</dt><dd>
<a href="http://www.w3.org/TR/ddr-core-vocabulary/">http://www.w3.org/TR/ddr-core-vocabulary/</a>
</dd><dt>Previous version:</dt><dd>
<a href="http://www.w3.org/TR/2007/WD-ddr-core-vocabulary-20071218/">http://www.w3.org/TR/2007/WD-ddr-core-vocabulary-20071218/</a>
</dd><dt>Editors:</dt><dd>Jo Rabin, mTLD Top Level Domain (dotMobi)</dd><dd>Andrea Trasatti, mTLD Top Level Domain (dotMobi)</dd><dd>Rotan Hanrahan, MobileAware</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2008 <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/><div>
<h2><a name="abstract" id="abstract"/>Abstract</h2><p>This document describes the Device Description Repository Core Vocabulary for Content
Adaptation in the Mobile Web, described in the charter of the Device Descriptions
Working Group, as well as the process by which the Vocabulary was defined.</p></div><div>
<h2><a name="status" id="status"/>Status of this Document</h2><p>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 W3C technical
reports index at <a href="http://www.w3.org/TR/">http://www.w3.org/TR/</a>.</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 is a Working Group Note. It has been developed by the <a href="http://www.w3.org/2005/MWI/DDWG/">Mobile Web Initiative Device Description Working Group</a>, as
part of the <a href="http://www.w3.org/">W3C</a>
<a href="http://www.w3.org/Mobile/">Mobile
Web Initiative</a>. Please send comments on this document to the Working
Group's public email list <a href="mailto:public-ddwg-comments@w3.org">public-ddwg-comments@w3.org</a>, a <a href="http://lists.w3.org/Archives/Public/public-ddwg-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/37583/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>
<div class="toc">
<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#sec-introduction">Introduction</a><br/>
2 <a href="#sec-process">Process</a><br/>
2.1 <a href="#sec-process-questionnaure">Questionnaire</a><br/>
2.2 <a href="#sec-process-evaluation">Assessment</a><br/>
3 <a href="#sec-vocabulary-property-aspect">Vocabulary, Property and Aspect </a><br/>
3.1 <a href="#sec-aspects">Aspects of the Core Vocabulary</a><br/>
3.2 <a href="#sec-property-names-value-types">Property Names and Property Value Types</a><br/>
4 <a href="#sec-properties">Properties</a><br/>
4.1 <a href="#sec-property-vendor">Vendor</a><br/>
4.2 <a href="#sec-property-model">Model</a><br/>
4.3 <a href="#sec-property-version">Version</a><br/>
4.4 <a href="#sec-property-displayWidth">Display Width</a><br/>
4.5 <a href="#sec-property-displayHeight">Display Height</a><br/>
4.6 <a href="#sec-displayColorDepth">Display Color Depth</a><br/>
4.7 <a href="#sec-inputDevices">Input Devices</a><br/>
4.8 <a href="#sec-markupSupport">Markup Support</a><br/>
4.9 <a href="#sec-stylesheetSupport">Stylesheet Support</a><br/>
4.10 <a href="#sec-imageFormatSupport">Image Format Support</a><br/>
4.11 <a href="#sec-inputModeSupport">Input Mode Support</a><br/>
4.12 <a href="#sec-cookieSupport">Cookie Support</a><br/>
4.13 <a href="#sec-scriptSupport">Script Support</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#sec-references">References</a><br/>
B <a href="#sec-acknowledgements">Acknowledgments</a><br/>
</p></div><hr/><div class="body"><div class="div1">
<h2><a name="sec-introduction" id="sec-introduction"/>1 Introduction</h2><p>This document identifies properties that are considered essential for adaptation of
content in the Mobile Web. Its intended use is to define a baseline Vocabulary for
Device Description Repository (DDR) implementations.</p><p>The Vocabulary defined in this document is not intended to represent an exhaustive
set of properties for content adaptation. DDR Implementations that require
additional properties are free to make use of additional vocabularies. The process
of creating a new Vocabulary can be modeled on the process described in this
document. Implementors are encouraged to make use of the UWA ontology <a href="#UWA-Ontology">[UWA-Ontology]</a> to suggest
extensions to it.</p><p>Implementers of DDR solutions that are intended to support content adaptation for
Mobile Web-enabled devices should, at a minimum, support the DDR Core Vocabulary as
defined in this document.</p><p>This document is maintained by the MWI DDWG and arrangements will be made to assign a
maintainer after the closure of the DDWG.</p></div><div class="div1">
<h2><a name="sec-process" id="sec-process"/>2 Process</h2><p>The DDWG established a lightweight process for accepting and evaluating contributions
to the DDR Core Vocabulary, comprising the following:</p><div class="div2">
<h3><a name="sec-process-questionnaure" id="sec-process-questionnaure"/>2.1 Questionnaire</h3><p>A <a href="http://www.w3.org/2005/MWI/DDWG/wiki/CoreVocabulary#head-e0d6d328997c4d86695895ee212265a276a50577">public questionnaire</a> was
launched to request proposals for inclusion in the Core Vocabulary, with the
following data being obtained for each proposal:</p><ul><li><p><em>Description</em>: A brief description of the proposed
Property.</p></li><li><p><em>Type</em>: The data type associated with the Property.</p></li><li><p><em>Justification</em>: An argument put forward to justify the
Property being part of the Core Vocabulary. This should explain why the
proposed Property is essential for basic adaptation of typical Web
content, in the context of Mobile Web-enabled devices.</p></li><li><p><em>Measurement</em>: A explanation of how this Property is
evaluated, suggesting where appropriate the units of measurement.</p></li></ul></div><div class="div2">
<h3><a name="sec-process-evaluation" id="sec-process-evaluation"/>2.2 Assessment</h3><p>Proposals submitted via the questionnaire were assessed to determine if they were
appropriate for the Core Vocabulary. The following guidance was used to
determine the main candidates:</p><ul><li><p>The Property must be considered essential to achieve adaptation of Web
content for mobile devices.</p></li><li><p>The Property must be objective, unambiguous and any measurements must be
reliably repeatable.</p></li><li><p>The Property should not be derivable from other essential Properties.</p></li><li><p>There should be a reasonable expectation of acquiring values for the
Property (e.g. from manufacturers).</p></li></ul><p>The group voted on each proposed Property. Those Properties that were rejected
were further assessed for the possibility of being useful in other domains, and
where identified, external groups were informed of these Properties so that they
may consider developing their own vocabularies.</p></div></div><div class="div1">
<h2><a name="sec-vocabulary-property-aspect" id="sec-vocabulary-property-aspect"/>3 Vocabulary, Property and Aspect </h2><p>The DDWG's work on modelling the Delivery Context has highlighted the
desirability of identifying components of actual Delivery Contexts and
classifying their types.</p><p>Components of the Delivery Context are, typically, a
device, a user agent, a network connection, and possibly one or more proxies. The
notion of "Aspect" captures the type of such components, and allows Properties
of vocabularies to refer to specific Aspects of the Delivery Context, or to the
Delivery Context as a whole.</p><p>The terms "Vocabulary", "Property" and "Aspect" are defined in <a href="#DDR-Simple-API">[DDR-Simple-API]</a>, under <a href="http://www.w3.org/TR/DDR-Simple-API/#sec-vocabularies">Section 3. Vocabularies</a>.</p><div class="div2">
<h3><a name="sec-aspects" id="sec-aspects"/>3.1 Aspects of the Core Vocabulary</h3><p>This Vocabulary defines two Aspects, <code>webBrowser</code> and <code>device</code>,
which serve to disambiguate the usage of Properties such as <code>Vendor</code>.
Other Vocabularies may define other values for Aspects.</p><div class="div3">
<h4><a name="sec-aspect-device" id="sec-aspect-device"/>3.1.1 device</h4><p>An apparatus through which a user can perceive and interact with the Web (see <a href="http://www.w3.org/TR/di-gloss/#def-device">Device</a> in <a href="#DIGLOSS">[DIGLOSS]</a>)</p></div><div class="div3">
<h4><a name="sec-aspect-webBrowser" id="sec-aspect-webBrowser"/>3.1.2 webBrowser</h4><p>A User Agent for Web pages (see <a href="http://www.w3.org/TR/di-gloss/#def-user-agent">User Agent</a> in <a href="#DIGLOSS">[DIGLOSS]</a>)</p></div></div><div class="div2">
<h3><a name="sec-property-names-value-types" id="sec-property-names-value-types"/>3.2 Property Names and Property Value Types</h3><p>Refer to <a href="#DDR-Simple-API">[DDR-Simple-API]</a> <a href="http://www.w3.org/TR/DDR-Simple-API/#sec-vocabularies">Section 3. Vocabularies</a> for allowable identifier syntax, for allowable value data types and how to represent enumerations in vocabularies that are to be used with the DDR Simple API.</p><p>The Property identifiers in this Vocabulary are associated with the namespace
<code>http://www.w3.org/2008/01/ddr-core-vocabulary</code>. This
namespace will change if the Core Vocabulary is updated.</p><p>The enumerations described in this document contain initial values that should be
supported by all implementations of the Core Vocabulary and which may be
supplemented by further DDR specific values.</p></div></div><div class="div1">
<h2><a name="sec-properties" id="sec-properties"/>4 Properties</h2><p>This is a list of the Properties in the DDR Core Vocabulary. </p><p>The <em>Default Aspect</em> for the Properties of the Core Vocabulary is <code>device</code> where a Property applies to more than one Aspect.</p><div class="div2">
<h3><a name="sec-property-vendor" id="sec-property-vendor"/>4.1 Vendor</h3><div class="div3">
<h4><a name="d0e252" id="d0e252"/>4.1.1 ID</h4><p><code>vendor</code></p></div><div class="div3">
<h4><a name="d0e258" id="d0e258"/>4.1.2 Associated Aspects</h4><p>webBrowser, device</p></div><div class="div3">
<h4><a name="d0e263" id="d0e263"/>4.1.3 Description</h4><p> The name of the maker (OEM) of a device, browser or some other component
(e.g. Mozilla).</p></div><div class="div3">
<h4><a name="d0e268" id="d0e268"/>4.1.4 Type</h4><p>String</p></div><div class="div3">
<h4><a name="d0e273" id="d0e273"/>4.1.5 Related Properties</h4><p>
<a href="#sec-property-model">model</a>, <a href="#sec-property-version">version</a></p></div><div class="div3">
<h4><a name="d0e283" id="d0e283"/>4.1.6 Note</h4><p> While knowing the Vendor, Model and Version of a device is not essential
when carrying out content adaptation, it is very important when designing an
application, building reports and analytics, and analyzing logs and usage
data.</p></div></div><div class="div2">
<h3><a name="sec-property-model" id="sec-property-model"/>4.2 Model</h3><div class="div3">
<h4><a name="d0e291" id="d0e291"/>4.2.1 ID</h4><p><code>model</code></p></div><div class="div3">
<h4><a name="d0e297" id="d0e297"/>4.2.2 Associated Aspects</h4><p>webBrowser, device</p></div><div class="div3">
<h4><a name="d0e302" id="d0e302"/>4.2.3 Description</h4><p>The model name of a device, browser or some other component (e.g.
Firefox).</p></div><div class="div3">
<h4><a name="d0e307" id="d0e307"/>4.2.4 Type</h4><p>String</p></div><div class="div3">
<h4><a name="d0e312" id="d0e312"/>4.2.5 Related Properties</h4><p>
<a href="#sec-property-vendor">vendor</a>, <a href="#sec-property-version">version</a></p></div><div class="div3">
<h4><a name="d0e322" id="d0e322"/>4.2.6 Note</h4><p> See Vendor above.</p></div></div><div class="div2">
<h3><a name="sec-property-version" id="sec-property-version"/>4.3 Version</h3><div class="div3">
<h4><a name="d0e330" id="d0e330"/>4.3.1 ID</h4><p><code>version</code></p></div><div class="div3">
<h4><a name="d0e336" id="d0e336"/>4.3.2 Associated Aspects</h4><p>webBrowser, device</p></div><div class="div3">
<h4><a name="d0e341" id="d0e341"/>4.3.3 Description</h4><p> The version number of a component (e.g. 2.0.0.10)</p></div><div class="div3">
<h4><a name="d0e346" id="d0e346"/>4.3.4 Type</h4><p>String</p></div><div class="div3">
<h4><a name="d0e351" id="d0e351"/>4.3.5 Related Properties</h4><p>
<a href="#sec-property-vendor">vendor</a>, <a href="#sec-property-model">model</a></p></div><div class="div3">
<h4><a name="d0e361" id="d0e361"/>4.3.6 Note</h4><p> See Vendor above.</p></div></div><div class="div2">
<h3><a name="sec-property-displayWidth" id="sec-property-displayWidth"/>4.4 Display Width</h3><div class="div3">
<h4><a name="d0e369" id="d0e369"/>4.4.1 ID</h4><p><code>displayWidth</code></p></div><div class="div3">
<h4><a name="d0e375" id="d0e375"/>4.4.2 Associated Aspects</h4><p>webBrowser, device</p></div><div class="div3">
<h4><a name="d0e380" id="d0e380"/>4.4.3 Description</h4><p>The total number of addressable pixels in the horizontal direction of a
rectangular display when held in its default orientation. The Property does
not apply to displays that are not rectangular or square.</p></div><div class="div3">
<h4><a name="d0e385" id="d0e385"/>4.4.4 Measurement</h4><p> The pixels are counted from the top left corner to the top right corner, and
the result expressed as an integer.</p></div><div class="div3">
<h4><a name="d0e390" id="d0e390"/>4.4.5 Type</h4><p>int</p></div><div class="div3">
<h4><a name="d0e395" id="d0e395"/>4.4.6 Related Properties</h4><p>
<a href="#sec-property-displayHeight">displayHeight</a>
</p></div><div class="div3">
<h4><a name="d0e403" id="d0e403"/>4.4.7 Note</h4><p> Needed to fit/crop images, text or other width-adaptable content to the
screen. Especially useful for LTR and RTL content, where vertical scrolling
would be the norm but horizontal scrolling is not desirable. Identified as
an important Property by the DDWG in its Top N finding <a href="#TopN">[TopN]</a>. Present in UAProf <a href="#UAPROF">[UAPROF]</a>.
Present (and used) in existing adaptation solutions.</p></div></div><div class="div2">
<h3><a name="sec-property-displayHeight" id="sec-property-displayHeight"/>4.5 Display Height</h3><div class="div3">
<h4><a name="d0e415" id="d0e415"/>4.5.1 ID</h4><p><code>displayHeight</code></p></div><div class="div3">
<h4><a name="d0e421" id="d0e421"/>4.5.2 Associated Aspects</h4><p>webBrowser, device</p></div><div class="div3">
<h4><a name="d0e426" id="d0e426"/>4.5.3 Description</h4><p> The total number of addressable pixels in the vertical direction of a
rectangular display when held in its default orientation. The Property does
not apply to displays that are not rectangular or square.</p></div><div class="div3">
<h4><a name="d0e431" id="d0e431"/>4.5.4 Measurement</h4><p> The pixels are counted from the top left corner to the bottom left corner,
and the result expressed as an integer.</p></div><div class="div3">
<h4><a name="d0e436" id="d0e436"/>4.5.5 Type</h4><p>int</p></div><div class="div3">
<h4><a name="d0e441" id="d0e441"/>4.5.6 Related Properties</h4><p>
<a href="#sec-property-displayWidth">displayWidth</a>
</p></div><div class="div3">
<h4><a name="d0e449" id="d0e449"/>4.5.7 Note</h4><p> Needed to fit/crop images, text or other width-adaptable content to the
screen. Especially useful for LTR and RTL content, where vertical scrolling
would be the norm but horizontal scrolling is not desirable. Identified as
an important Property by the DDWG in its Top N finding. Present in UAProf.
Present (and used) in existing adaptation solutions.</p></div></div><div class="div2">
<h3><a name="sec-displayColorDepth" id="sec-displayColorDepth"/>4.6 Display Color Depth</h3><div class="div3">
<h4><a name="d0e457" id="d0e457"/>4.6.1 ID</h4><p><code>displayColorDepth</code></p></div><div class="div3">
<h4><a name="d0e463" id="d0e463"/>4.6.2 Associated Aspects</h4><p>device</p></div><div class="div3">
<h4><a name="d0e468" id="d0e468"/>4.6.3 Description</h4><p>The color depth of a display.</p></div><div class="div3">
<h4><a name="d0e473" id="d0e473"/>4.6.4 Measurement</h4><p>Count the number of bits used for color definition.</p></div><div class="div3">
<h4><a name="d0e478" id="d0e478"/>4.6.5 Type</h4><p>int</p></div><div class="div3">
<h4><a name="d0e483" id="d0e483"/>4.6.6 Note</h4><p> If you are making any image or video transcoding it is important to know the
maximum colors addressable by the screen. Measuring in bits should make it
easier for programmatic conversions.</p></div></div><div class="div2">
<h3><a name="sec-inputDevices" id="sec-inputDevices"/>4.7 Input Devices</h3><div class="div3">
<h4><a name="d0e491" id="d0e491"/>4.7.1 ID</h4><p><code>inputDevices</code></p></div><div class="div3">
<h4><a name="d0e497" id="d0e497"/>4.7.2 Associated Aspects</h4><p>device</p></div><div class="div3">
<h4><a name="d0e502" id="d0e502"/>4.7.3 Description</h4><p> This Property described which input devices are available to the user.
Normally most mobile devices such as mobile phones will have a keypad, it is
common, though, to have a rocker, a stylus and a touch screen in PDAs,
tablets and so on.</p></div><div class="div3">
<h4><a name="d0e507" id="d0e507"/>4.7.4 Measurement</h4><p> Observation of features or study of specifications.</p></div><div class="div3">
<h4><a name="d0e512" id="d0e512"/>4.7.5 Type</h4><p> Enumeration of values as follows (or other values supported by individual
DDRs:</p><table class="parameterList"><tbody><tr><th>Value</th><th>Description</th><th>Reference</th></tr><tr><td>keypad</td><td>classic 12 button mobile phone keypad</td><td/></tr><tr><td>touchScreen</td><td>touch screen that allows pointing to an area on the screen</td><td/></tr><tr><td>stylus</td><td>a stylus normally works in combination with a touch screen, the
stylus provides higher precision</td><td/></tr><tr><td>trackball</td><td> a little sphere that acts like a trackball mouse</td><td/></tr><tr><td>clickWheel</td><td>a wheel that is normally placed either below the screen or on
the side of the device that lets the user quickly move up and
down and click on link or items on the screen</td><td/></tr></tbody></table></div><div class="div3">
<h4><a name="d0e556" id="d0e556"/>4.7.6 Note</h4><p>From an application perspective knowing that a device features a stylus or a
touch screen can open many possibilities to greatly enhance the user
interaction.</p></div></div><div class="div2">
<h3><a name="sec-markupSupport" id="sec-markupSupport"/>4.8 Markup Support</h3><div class="div3">
<h4><a name="d0e564" id="d0e564"/>4.8.1 ID</h4><p><code>markupSupport</code></p></div><div class="div3">
<h4><a name="d0e570" id="d0e570"/>4.8.2 Associated Aspects</h4><p>webBrowser</p></div><div class="div3">
<h4><a name="d0e575" id="d0e575"/>4.8.3 Description</h4><p> Set of mark-up languages a client supports. </p></div><div class="div3">
<h4><a name="d0e580" id="d0e580"/>4.8.4 Measurement</h4><p> Claim of conformance by the vendor.</p></div><div class="div3">
<h4><a name="d0e585" id="d0e585"/>4.8.5 Type</h4><p> Enumeration with values chosen from the following (or other values supported
by individual DDRs):</p><table class="parameterList"><tbody><tr><th>Value</th><th>Description</th><th>Reference</th></tr><tr><td>xhtmlBasic10</td><td>XHTML Basic 1.0</td><td>
<a href="#XHTMLBasic10">[XHTMLBasic10]</a>
</td></tr><tr><td>xhtmlBasic11</td><td>XHTML Basic 1.1</td><td>
<a href="#XHTMLBasic11">[XHTMLBasic11]</a>
</td></tr><tr><td>xhtmlMP10</td><td>XHTML-MP 1.0</td><td>
<a href="#XHTMLMP">[XHTMLMP]</a>
</td></tr></tbody></table></div><div class="div3">
<h4><a name="d0e626" id="d0e626"/>4.8.6 Note</h4><p> In order to provide the appropriate mark-up when serving a web page, it is
required that the server knows the supported mark-ups. Accept headers are
often not accurate enough and can be modified by proxies in-between.</p></div></div><div class="div2">
<h3><a name="sec-stylesheetSupport" id="sec-stylesheetSupport"/>4.9 Stylesheet Support</h3><div class="div3">
<h4><a name="d0e634" id="d0e634"/>4.9.1 ID</h4><p><code>stylesheetSupport</code></p></div><div class="div3">
<h4><a name="d0e640" id="d0e640"/>4.9.2 Associated Aspects</h4><p>webBrowser</p></div><div class="div3">
<h4><a name="d0e645" id="d0e645"/>4.9.3 Description</h4><p>Set of Style Sheet languages a client supports.</p></div><div class="div3">
<h4><a name="d0e650" id="d0e650"/>4.9.4 Measurement</h4><p> Claim of conformance by the vendor.</p></div><div class="div3">
<h4><a name="d0e655" id="d0e655"/>4.9.5 Type</h4><p> Enumeration with values chosen from the following (or other values supported
by individual DDRs):</p><table class="parameterList"><tbody><tr><th>Value</th><th>Description</th><th>Reference</th></tr><tr><td>css10</td><td>CSS Level 1</td><td>
<a href="#CSS10">[CSS10]</a>
</td></tr><tr><td>css21</td><td>CSS Level 2 Revision 1</td><td>
<a href="#CSS21">[CSS21]</a>
</td></tr><tr><td>wcss10</td><td>WCSS</td><td>
<a href="#WCSS">[WCSS]</a>
</td></tr></tbody></table></div><div class="div3">
<h4><a name="d0e696" id="d0e696"/>4.9.6 Note</h4><p> Style sheets are needed to define how the page should be laid out, positions
and colors.</p></div></div><div class="div2">
<h3><a name="sec-imageFormatSupport" id="sec-imageFormatSupport"/>4.10 Image Format Support</h3><div class="div3">
<h4><a name="d0e704" id="d0e704"/>4.10.1 ID</h4><p><code>imageFormatSupport</code></p></div><div class="div3">
<h4><a name="d0e710" id="d0e710"/>4.10.2 Associated Aspects</h4><p>webBrowser</p></div><div class="div3">
<h4><a name="d0e715" id="d0e715"/>4.10.3 Description</h4><p>Set of image formats a client supports as part of a Web page (as distinct from formats that may be downloaded).</p></div><div class="div3">
<h4><a name="d0e720" id="d0e720"/>4.10.4 Measurement</h4><p> Claim of conformance by the vendor.</p></div><div class="div3">
<h4><a name="d0e725" id="d0e725"/>4.10.5 Type</h4><p> Enumeration with values chosen from the following (or other values supported
by individual DDRs):</p><table class="parameterList"><tbody><tr><th>Value</th><th>Description</th><th>Reference</th></tr><tr><td>gif87</td><td>GIF 87</td><td>
<a href="#GIF87">[GIF87]</a>
</td></tr><tr><td>gif89a</td><td>GIF 89a</td><td>
<a href="#GIF89a">[GIF89a]</a>
</td></tr><tr><td>jpeg</td><td>JPEG</td><td>
<a href="#JPEG">[JPEG]</a>
</td></tr><tr><td>png</td><td>PNG</td><td>
<a href="#PNG">[PNG]</a>
</td></tr></tbody></table></div><div class="div3">
<h4><a name="d0e775" id="d0e775"/>4.10.6 Note</h4><p> Images are the first step to make content more compelling. Accept headers
are often not accurate enough to determine which formats are supported and
can be modified by proxies in-between.</p></div></div><div class="div2">
<h3><a name="sec-inputModeSupport" id="sec-inputModeSupport"/>4.11 Input Mode Support</h3><div class="div3">
<h4><a name="d0e783" id="d0e783"/>4.11.1 ID</h4><p><code>inputModeSupport</code></p></div><div class="div3">
<h4><a name="d0e789" id="d0e789"/>4.11.2 Associated Aspects</h4><p>webBrowser</p></div><div class="div3">
<h4><a name="d0e794" id="d0e794"/>4.11.3 Description</h4><p> The preferred ways of supporting specific formats for input type="text"
fields. This can be done with the 'format' attribute, as a WCSS property or
using the 'inputmode' attribute.</p></div><div class="div3">
<h4><a name="d0e799" id="d0e799"/>4.11.4 Measurement</h4><p> Test using controls specifying the format
with the mechanisms cited.</p></div><div class="div3">
<h4><a name="d0e804" id="d0e804"/>4.11.5 Type</h4><p> Enumeration with values chosen from the following (or other values supported
by individual DDRs):</p><table class="parameterList"><tbody><tr><th>Value</th><th>Description</th><th>Reference</th></tr><tr><td>useFormatAttribute</td><td>Use the <code>format</code> attribute of the <code>input</code>
element - an extension to XHTML-MP.</td><td>
<a href="#OpenWave-Format-Attribute">[OpenWave-Format-Attribute]</a>
</td></tr><tr><td>useWCSS</td><td>Use the WCSS <code>-wap-input-format</code> property.</td><td>
<a href="#WCSS">[WCSS]</a>
</td></tr><tr><td>useInputmodeAttribute</td><td>Use the <code>inputmode</code> attribute.</td><td>
<a href="#XHTMLBasic11">[XHTMLBasic11]</a>
</td></tr></tbody></table></div><div class="div3">
<h4><a name="d0e857" id="d0e857"/>4.11.6 Note</h4><p>Assists user with input by setting the device input mode appropriately.</p></div></div><div class="div2">
<h3><a name="sec-cookieSupport" id="sec-cookieSupport"/>4.12 Cookie Support</h3><div class="div3">
<h4><a name="d0e865" id="d0e865"/>4.12.1 ID</h4><p><code>cookieSupport</code></p></div><div class="div3">
<h4><a name="d0e871" id="d0e871"/>4.12.2 Associated Aspects</h4><p>webBrowser</p></div><div class="div3">
<h4><a name="d0e876" id="d0e876"/>4.12.3 Description</h4><p> The ability of a client to store cookies and send them when appropriate.</p></div><div class="div3">
<h4><a name="d0e881" id="d0e881"/>4.12.4 Measurement</h4><p> A web server sets a cookie in an HTTP Response. The Mobile Web browser makes
a subsequent HTTP request. If the browser supports cookies the HTTP request
should contain the cookie previously set by the web server.</p></div><div class="div3">
<h4><a name="d0e886" id="d0e886"/>4.12.5 Type</h4><p>boolean</p></div><div class="div3">
<h4><a name="d0e891" id="d0e891"/>4.12.6 Note</h4><p> It is very important to know if a browser support cookies, among other
things, to support the concept of user session. An adaptation solution that
knows that a device does not support cookies can fall back to a URI
rewriting mechanism.</p></div></div><div class="div2">
<h3><a name="sec-scriptSupport" id="sec-scriptSupport"/>4.13 Script Support</h3><div class="div3">
<h4><a name="d0e899" id="d0e899"/>4.13.1 ID</h4><p><code>scriptSupport</code></p></div><div class="div3">
<h4><a name="d0e905" id="d0e905"/>4.13.2 Associated Aspects</h4><p>webBrowser</p></div><div class="div3">
<h4><a name="d0e910" id="d0e910"/>4.13.3 Description</h4><p>Set of scripting languages supported.</p></div><div class="div3">
<h4><a name="d0e915" id="d0e915"/>4.13.4 Measurement</h4><p>Manufacturer claim of support of a scripting language or dialect.</p></div><div class="div3">
<h4><a name="d0e920" id="d0e920"/>4.13.5 Type</h4><p>Enumeration with values chosen from the following list (or other values
supported by individual DDRs):</p><table class="parameterList"><tbody><tr><th>Value</th><th>Description</th><th>Reference</th></tr><tr><td>ecmascript-MP</td><td>Supports ECMAScript Mobile Profile</td><td>
<a href="#ECMAScript-MP">[ECMAScript-MP]</a>
</td></tr></tbody></table></div></div></div></div><div class="back"><div class="div1">
<h2><a name="sec-references" id="sec-references"/>A References</h2><dl><dt class="label"><a name="CSS10" id="CSS10"/>CSS10</dt><dd>Cascading Style Sheets, level 1, Håkon Wium Lie, Bert
Bos, W3C Recommendation 17 Dec 1996, revised 11 Jan 1999 (See <a href="http://www.w3.org/TR/REC-CSS1">http://www.w3.org/TR/REC-CSS1</a>)</dd><dt class="label"><a name="CSS21" id="CSS21"/>CSS21</dt><dd>Cascading Style Sheets Level 2 Revision 1 (CSS 2.1)
Specification, Bert Bos, Tantek Çelik, Ian Hickson, Håkon Wium Lie, W3C
Candidate Recommendation 19 July 2007 (See <a href="http://www.w3.org/TR/CSS21 ">http://www.w3.org/TR/CSS21 </a>)</dd><dt class="label"><a name="DDR-Simple-API" id="DDR-Simple-API"/>DDR-Simple-API</dt><dd> Device
Description Repository Simple API, Jo Rabin, José Manuel Cantera Fonseca, Rotan Hanrahan, Ignacio Marín (eds.), W3C Working Draft, 4 April 2008 (See <a href="http://www.w3.org/TR/DDR-Simple-API">http://www.w3.org/TR/DDR-Simple-API</a>)</dd><dt class="label"><a name="DIGLOSS" id="DIGLOSS"/>DIGLOSS</dt><dd> W3C Glossary of Terms for Device
Independence, Rhys Lewis (ed), W3C Working Draft 18 January 2005 (See <a href="http://www.w3.org/TR/di-gloss/">http://www.w3.org/TR/di-gloss/</a>)</dd><dt class="label"><a name="ECMAScript-MP" id="ECMAScript-MP"/>ECMAScript-MP</dt><dd>ECMAScript Mobile
Profile, A Wireless Markup Scripting Language, Version 1.0, 20 Oct 2006,
MOA-WAP-ESMP-V1_0-20061020-A (PDF) (See <a href="http://www.openmobilealliance.org/technical/release_program/docs/Browsing/V2_2-20061020-A/OMA-WAP-ESMP-V1_0-20061020-A.pdf">http://www.openmobilealliance.org/technical/release_program/docs/Browsing/V2_2-20061020-A/OMA-WAP-ESMP-V1_0-20061020-A.pdf</a>)</dd><dt class="label"><a name="GIF87" id="GIF87"/>GIF87</dt><dd>G I F (tm) Graphics Interchange Format
(tm), CompuServe Incorporated, 15 June 1987 (See <a href="http://www.w3.org/Graphics/GIF/spec-gif87.txt">http://www.w3.org/Graphics/GIF/spec-gif87.txt</a>)</dd><dt class="label"><a name="GIF89a" id="GIF89a"/>GIF89a</dt><dd>GRAPHICS INTERCHANGE FORMAT (sm),
Version 89a, CompuServe Incorporated, 1990 (See <a href="http://www.w3.org/Graphics/GIF/spec-gif89a.txt">http://www.w3.org/Graphics/GIF/spec-gif89a.txt</a>)</dd><dt class="label"><a name="JPEG" id="JPEG"/>JPEG</dt><dd>Recommendation T.81, 18 September 1992 (See <a href="http://www.w3.org/Graphics/JPEG/itu-t81.pdf">http://www.w3.org/Graphics/JPEG/itu-t81.pdf</a>)</dd><dt class="label"><a name="OpenWave-Format-Attribute" id="OpenWave-Format-Attribute"/>OpenWave-Format-Attribute</dt><dd>XHTML-MP
Style Guide Chapter 5 - Forms: Collecting User Data (See <a href="http://developer.openwave.com/dvl/support/documentation/guides_and_references/xhtml-mp_style_guide/chapter5.htm">http://developer.openwave.com/dvl/support/documentation/guides_and_references/xhtml-mp_style_guide/chapter5.htm</a>)</dd><dt class="label"><a name="PNG" id="PNG"/>PNG</dt><dd>Portable Network Graphics (PNG) Specification (Second Edition)
Information technology — Computer graphics and image processing — Portable
Network Graphics (PNG): Functional specification. ISO/IEC 15948:2003 (E), David
Duce (ed.), W3C Recommendation 10 November 2003 (See <a href="http://www.w3.org/TR/PNG/">http://www.w3.org/TR/PNG/</a>)</dd><dt class="label"><a name="TopN" id="TopN"/>TopN</dt><dd>The "Top N" properties. A finding of the DDWG, recorded in the DDWG wiki, 28 February 2007. (See <a href="http://www.w3.org/2005/MWI/DDWG/wiki/TopFiveMindMap">http://www.w3.org/2005/MWI/DDWG/wiki/TopFiveMindMap</a>)</dd><dt class="label"><a name="UAPROF" id="UAPROF"/>UAPROF</dt><dd>User Agent Profile (zip/MS Word) (See <a href="http://member.openmobilealliance.org/ftp/public_documents/mce/DCAP/Permanent_documents/OMA-TS-UAProf-V2_0-20060206-A.zip">http://member.openmobilealliance.org/ftp/public_documents/mce/DCAP/Permanent_documents/OMA-TS-UAProf-V2_0-20060206-A.zip</a>)</dd><dt class="label"><a name="UWA-Ontology" id="UWA-Ontology"/>UWA-Ontology</dt><dd> Delivery Context Ontology, Rhys Lewis (ed), W3C Working Draft 21 December 2007 (See <a href="http://www.w3.org/TR/dcontology/">http://www.w3.org/TR/dcontology/</a>)</dd><dt class="label"><a name="WCSS" id="WCSS"/>WCSS</dt><dd>Wireless CSS Specification,
Open Mobile Alliance, Approved Version 1.1 – 20 October 2006 (See <a href="http://www.openmobilealliance.org/technical/release_program/docs/Browsing/V2_3-20080331-A/OMA-WAP-WCSS-V1_1-20061020-A.pdf">http://www.openmobilealliance.org/technical/release_program/docs/Browsing/V2_3-20080331-A/OMA-WAP-WCSS-V1_1-20061020-A.pdf</a>)</dd><dt class="label"><a name="XHTMLBasic10" id="XHTMLBasic10"/>XHTMLBasic10</dt><dd>XHTML Basic, Mark Baker, Masayasu
Ishikawa, Shinichi Matsui, Peter Stark, Ted Wugofski, Toshihiko Yamakami, W3C
Recommendation 19 December 2000 (See <a href="http://www.w3.org/TR/2006/WD-xhtml-basic-20060705/">http://www.w3.org/TR/2006/WD-xhtml-basic-20060705/</a>)</dd><dt class="label"><a name="XHTMLBasic11" id="XHTMLBasic11"/>XHTMLBasic11</dt><dd>XHTML Basic 1.1, Shane McCarron,
Masayasu Ishikawa et al., 13 July 2007 (See <a href="http://www.w3.org/TR/2007/CR-xhtml-basic-20070713">http://www.w3.org/TR/2007/CR-xhtml-basic-20070713</a>)</dd><dt class="label"><a name="XHTMLMP" id="XHTMLMP"/>XHTMLMP</dt><dd>XHTML Mobile Profile, Open
Mobile Alliance, 29 October 2001 (See <a href="http://www.openmobilealliance.org/tech/affiliates/wap/wap-277-xhtmlmp-20011029-a.pdf">http://www.openmobilealliance.org/tech/affiliates/wap/wap-277-xhtmlmp-20011029-a.pdf</a>)</dd></dl></div><div class="div1">
<h2><a name="sec-acknowledgements" id="sec-acknowledgements"/>B Acknowledgments</h2><p>The editors acknowledge contributors to the Core Vocabulary, namely:</p><ul><li>José Manuel Cantera Fonseca, Telefónica Investigación y Desarrollo</li><li>Martin Jones, Volantis</li><li>Jongpil Yi, Samsung</li></ul></div></div></body></html>