Copyright © 2008 W3C ® ( MIT , ERCIM , Keio ), All Rights Reserved. W3C liability , trademark and document use rules apply.
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.
This document is an editors' copy that has no official standing.
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 http://www.w3.org/TR/ .
Publication as a Working Draft 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.
This
document
is
the
seventh
eighth
internal
draft
of
a
First
Public
Working
Draft
of
a
future
Working
Group
Note.
It
has
been
developed
by
the
Device
Description
Working
Group
,
as
part
of
the
W3C
Mobile
Web
Initiative
.
Please
send
comments
on
this
document
to
the
Working
Group's
public
email
list
public-ddwg@w3.org
,
a
publicly
archived
mailing
list
.
This document was produced under the 5 February 2004 W3C Patent Policy . W3C maintains a public list of patent disclosures made in connection with this document; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) with respect to this specification must disclose the information in accordance with section 6 of the W3C Patent Policy .
1
Introduction
2
Process
2.1
Questionnaire
2.2
Assessment
3
Vocabulary,
Property
and
Aspect
3.1
Aspects
of
the
Core
Vocabulary
3.1.1
device
3.1.2
webBrowser
3.2
Property
Names
and
Property
Value
Types
4
Properties
4.1
Vendor
4.1.1
ID
4.1.2
Associated
Aspects
4.1.3
Description
4.1.4
Type
4.1.5
Related
Properties
4.1.6
Note
4.2
Model
4.2.1
ID
4.2.2
Associated
Aspects
4.2.3
Description
4.2.4
Type
4.2.5
Related
Properties
4.2.6
Note
4.3
Version
4.3.1
ID
4.3.2
Associated
Aspects
4.3.3
Description
4.3.4
Type
4.3.5
Related
Properties
4.3.6
Note
4.4
Display
Width
4.4.1
ID
4.4.2
Associated
Aspects
4.4.3
Description
4.4.4
Measurement
4.4.5
Type
4.4.6
Related
Properties
4.4.7
Note
4.5
Display
Height
4.5.1
ID
4.5.2
Associated
Aspects
4.5.3
Description
4.5.4
Measurement
4.5.5
Type
4.5.6
Related
Properties
4.5.7
Note
4.6
Display
Color
Depth
4.6.1
ID
4.6.2
Associated
Aspects
4.6.3
Description
4.6.4
Measurement
4.6.5
Type
4.6.6
Note
4.7
Input
Devices
4.7.1
ID
4.7.2
Associated
Aspects
4.7.3
Description
4.7.4
Measurement
4.7.5
Type
4.7.6
Note
4.8
Markup
Support
4.8.1
ID
4.8.2
Associated
Aspects
4.8.3
Description
4.8.4
Measurement
4.8.5
Type
4.8.6
Note
4.9
Stylesheet
Support
4.9.1
ID
4.9.2
Associated
Aspects
4.9.3
Description
4.9.4
Measurement
4.9.5
Type
4.9.6
Note
4.10
Image
Format
Support
4.10.1
ID
4.10.2
Associated
Aspects
4.10.3
Description
4.10.4
Measurement
4.10.5
Type
4.10.6
Note
4.11
Input
Mode
Support
4.11.1
ID
4.11.2
Associated
Aspects
4.11.3
Description
4.11.4
Measurement
4.11.5
Type
4.11.6
Note
4.12
Cookie
Support
4.12.1
ID
4.12.2
Associated
Aspects
4.12.3
Description
4.12.4
Measurement
4.12.5
Type
4.12.6
Note
4.13
Script
Support
4.13.1
ID
4.13.2
Associated
Aspects
4.13.3
Description
4.13.4
Measurement
4.13.5
Type
This
document
identifies
properties
that
are
considered
essential
for
adaptation
of
content
in
the
mobile
Mobile
Web.
Its
intended
use
is
to
define
a
baseline
Vocabulary
for
implementations
of
the
Device
Description
Repository
(DDR).
The
Vocabulary
makes
reference
to
the
ontology
for
the
Web
Delivery
Context
which
is
being
developed
by
the
W3C
UWA
Working
Group
[UWA-Ontology]
.
(DDR)
implementations.
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 to suggest extensions to it.
Implementers
of
DDR
solutions
that
are
intended
to
support
content
adaptation
for
mobile
Mobile
Web-enabled
devices
should,
at
a
minimum,
support
the
DDR
Core
Vocabulary
as
defined
in
this
document.
This document is maintained by the MWI DDWG and arrangements will be made to assign a maintainer after the closure of the DDWG.
The DDWG established a lightweight process for accepting and evaluating contributions to the DDR Core Vocabulary, comprising the following:
A public questionnaire was launched to request proposals for inclusion in the Core Vocabulary, with the following data being obtained for each proposal:
Description : A brief description of the proposed Property.
Type : The data type associated with the Property.
Justification
:
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
Mobile
Web-enabled
devices.
Measurement : A explanation of how this Property is evaluated, suggesting where appropriate the units of measurement.
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:
The Property must be considered essential to achieve adaptation of Web content for mobile devices.
The Property must be objective, unambiguous and any measurements must be reliably repeatable.
The Property should not be derivable from other essential Properties.
There should be a reasonable expectation of acquiring values for the Property (e.g. from manufacturers).
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.
The DDWG's work on modelling the Delivery Context has highlighted the desirability of identifying components of actual Delivery Contexts and classifying their types.
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.
The terms "Vocabulary", "Property" and "Aspect" are defined in [DDR-Simple-API] , under Section 3. Vocabularies .
Work
on
Aspects
of
the
Delivery
Context
continues,
however,
for
the
purposes
of
this
This
Vocabulary
defines
two
specific
Aspects
are
identified.
Aspects.
Use
of
the
Aspects
webBrowser
and
device
serves
to
disambiguate
the
usage
of
Properties
such
as
Vendor
.
Other
Vocabularies
may
define
other
values
for
Aspects.
An apparatus through which a user can perceive and interact with the Web (see Device in [DIGLOSS] )
A User Agent for Web pages (see User Agent in [DIGLOSS] )
Refer to [DDR-Simple-API] Section 3. Vocabularies 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.
The
Property
identifiers
in
this
Vocabulary
are
associated
with
the
namespace
http://www.w3.org/2008/01/ddr-core-vocabulary
.
This
namespace
will
change
if
the
Core
Vocabulary
is
updated.
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.
This is a list of the Properties in the DDR Core Vocabulary.
The
Default
Aspect
for
the
Properties
of
the
Core
Vocabulary
is
device
where
a
Property
applies
to
more
than
one
Aspect.
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.
The pixels are counted from the top left corner to the top right corner, and the result expressed as an integer.
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.
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.
The pixels are counted from the top left corner to the bottom left corner, and the result expressed as an integer.
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.
Needed
if
the
screen
orientation
is
rotated
90
degrees,
in
which
case
this
Property
would
represent
the
width
of
the
rotated
screen.
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.
Enumeration of values as follows (or other values supported by individual DDRs:
| Value | Description | Reference |
|---|---|---|
| keypad | classic 12 button mobile phone keypad | |
| touchScreen | touch screen that allows pointing to an area on the screen | |
| stylus | a stylus normally works in combination with a touch screen, the stylus provides higher precision | |
| trackball | a little sphere that acts like a trackball mouse | |
| clickWheel | 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 |
Enumeration with values chosen from the following (or other values supported by individual DDRs):
| Value | Description | Reference |
|---|---|---|
| xhtmlBasic10 | XHTML Basic 1.0 | [XHTMLBasic10] |
| xhtmlBasic11 | XHTML Basic 1.1 | [XHTMLBasic11] |
| xhtmlMP10 | XHTML-MP 1.0 | [XHTMLMP] |
Set
of
image
formats
a
client
supports
as
part
of
a
Web
page.
page
(as
distinct
from
formats
that
may
be
downloaded).
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.
Test using <input type="text"> controls specifying the format with the mechanisms cited.
Enumeration with values chosen from the following (or other values supported by individual DDRs):
| Value | Description | Reference |
|---|---|---|
| useFormatAttribute |
Use
the
format
attribute
of
the
input
element
-
an
extension
to
XHTML-MP.
|
[OpenWave-Format-Attribute] |
| useWCSS |
Use
the
WCSS
-wap-input-format
property.
|
[WCSS] |
| useInputmodeAttribute |
Use
the
inputmode
attribute.
|
[XHTMLBasic11] |
Enumeration with values chosen from the following list (or other values supported by individual DDRs):
| Value | Description | Reference |
|---|---|---|
| ecmascript-MP | Supports ECMAScript Mobile Profile | [ECMAScript-MP] |