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 fourth 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
2.3 Contributions to UWA ontology
3 Properties
3.1 Vendor
3.2 Model
3.3 Version
3.4 Display Width
3.5 Display Height
3.6 Display Color Depth
3.7 Input Devices
3.8 Markup Support
3.9 Stylesheet Support
3.10 Image Format Support
3.11 Input Mode Support
3.12 Cookie Support
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 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].
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.
Implementors 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.
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 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.
Properties that were deemed appropriate to the DDR Core Vocabulary required appropriate semantics to be defined in the UWA ontology. The DDWG held regular meetings with UWA and kept the UWA informed about the needs of the Vocabulary. The UWA in turn helped to refine the DDWG's understanding of the proposed properties and their representation. The conclusion is a set of properties in the DDR Core Vocabulary that reference corresponding semantics in the UWA ontology.
This is a list of the properties in the DDR Core Vocabulary. Data types are as defined in [XSD-Part2].
Namespace ids are tentative
The property identifiers are associated with the namespace http://www.w3.org/2008/01/ddr-core-vocabualry-property-ids and values from the enumerations are associated with http://www.w3.org/2008/01/ddr-core-vocabulary-property-values.
Bindings to the UWA Ontology will be finalized in a later version of the document, those suggested here are for discussion.
Note:
Unlike the UWA Ontology, properties of the Core Vocabulary are not bound to particular aspects of the Delivery Context. Use of the term "display" in several property names is intended to refer to any aspect that can display content, or the Delivery Context as a whole, and is not intended specifically to refer to the aspect of "display" or "screen".
The name of the maker (OEM) of a device, browser or some other component (e.g. Mozilla).
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 (the values can be extended by individual DDR):
| Value | Description | |
|---|---|---|
| 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 additional values determined by DDR implementations(:
| Value | Description | |
|---|---|---|
| xhtmlBasic10 | XHTML Basic 1.0 | [XHTMLBasic10] |
| xhtmlBasic11 | XHTML Basic 1.1 | [XHTMLBasic11] |
| xhtmlMP10 | XHTML-MP 1.0 | [XHTMLMP] |
It has been proposed to rename this property "external format support" and add values for scripting to the enumeration, alternative proposals involve adding a "scriptSupport" property.
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 | |
|---|---|---|
| useFormatAttribute | Use the format attribute of the input element - an extension to XHTML-MP. | [@@ref] |
| useWCSS | Use the WCSS -wap-input-format property. | [WCSS] |
| useInputmodeAttribute | Use the inputmode attribute. | [XHTMLBasic11] |
The editors acknowledge the contributions of members of the DDWG.
The editors acknowledge contributors to the Vocabulary Submission Process, namely:
Do we have a list of people who contributed? Other than the above and Andrea?