Device Description Repository Core Vocabulary 1e 1f

W3C Working Group Note 29 January 11 February 2008

This version:
http://www.w3.org/2005/MWI/DDWG/Drafts/corevocabulary/080129 http://www.w3.org/2005/MWI/DDWG/Drafts/corevocabulary/080211
Latest version:
http://www.w3.org/2005/MWI/DDWG/Drafts/corevocabulary/latest
Previous version:
http://www.w3.org/2005/MWI/DDWG/Drafts/corevocabulary/080124 http://www.w3.org/2005/MWI/DDWG/Drafts/corevocabulary/080129
Editors:
Andrea Trasatti, mTLD Top Level Domain (dotMobi) [Lead Editor]
Jo Rabin, mTLD Top Level Domain (dotMobi)
Rotan Hanrahan, MobileAware

Abstract

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.

Status of this Document

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 fifth sixth 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 .

Table of Contents

1 Introduction
2 Process
    2.1 Questionnaire
    2.2 Assessment
    2.3 Contributions to UWA ontology
    2.4 Property Relationship to Aspects of the Delivery Context
3 Properties
    3.1 Vendor
        3.1.1 ID
        3.1.2 Associated Aspects
        3.1.3 Description
        3.1.4 Type
        3.1.5 Related Properties
        3.1.6 Note
    3.2 Model
        3.2.1 ID
        3.2.2 Associated Aspects
        3.2.3 Description
        3.2.4 Type
        3.2.5 Related Properties
        3.2.6 Note
    3.3 Version
        3.3.1 ID
        3.3.2 Associated Aspects
        3.3.3 Description
        3.3.4 Type
        3.3.5 Related Properties
        3.3.6 Note
    3.4 Display Width
        3.4.1 ID
        3.4.2 Associated Aspects
        3.4.3 Description
        3.4.4 Measurement
        3.4.5 Type
        3.4.6 Related Properties
        3.4.7 Note
    3.5 Display Height
        3.5.1 ID
        3.5.2 Associated Aspects
        3.5.3 Description
        3.5.4 Measurement
        3.5.5 Type
        3.5.6 Related Properties
        3.5.7 Note
    3.6 Display Color Depth
        3.6.1 ID
        3.6.2 Associated Aspects
        3.6.3 Description
        3.6.4 Measurement
        3.6.5 Type
        3.6.6 Note
    3.7 Input Devices
        3.7.1 ID
        3.7.2 Associated Aspects
        3.7.3 Description
        3.7.4 Measurement
        3.7.5 Type
        3.7.6 Note
    3.8 Markup Support
        3.8.1 ID
        3.8.2 Associated Aspects
        3.8.3 Description
        3.8.4 Measurement
        3.8.5 Type
        3.8.6 Note
    3.9 Stylesheet Support
        3.9.1 ID
        3.9.2 Associated Aspects
        3.9.3 Description
        3.9.4 Measurement
        3.9.5 Type
        3.9.6 Note
    3.10 Image Format Support
        3.10.1 ID
        3.10.2 Associated Aspects
        3.10.3 Description
        3.10.4 Measurement
        3.10.5 Type
        3.10.6 Note
    3.11 Input Mode Support
        3.11.1 ID
        3.11.2 Associated Aspects
        3.11.3 Description
        3.11.4 Measurement
        3.11.5 Type
        3.11.6 Note
    3.12 Cookie Support
        3.12.1 ID
        3.12.2 Associated Aspects
        3.12.3 Description
        3.12.4 Measurement
        3.12.5 Type
        3.12.6 Note
    3.13 Script Support
        3.13.1 ID
        3.13.2 Associated Aspects
        3.13.3 Description
        3.13.4 Measurement
        3.13.5 Type

Appendices

A References
B Acknowledgments


1 Introduction

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.

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.

This document is maintained by the MWI DDWG and arrangements will be made to assign a maintainer after the closure of the DDWG.

2 Process

The DDWG established a lightweight process for accepting and evaluating contributions to the DDR Core Vocabulary, comprising the following:

2.1 Questionnaire

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.

2.2 Assessment

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.

2.3 Contributions to UWA ontology

The following is not true

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 relate to semantics in the UWA ontology.

It is anticipated that a cross reference from the UWA Ontology to this vocabulary will be produced. However, the UWA Ontology is at an earlier stage of publication than this note at the time of publication of this note.

2.4 Property Relationship to Aspects of the Delivery Context

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, 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. Work on aspects of the delivery context continues, however, for the purposes of this vocabulary two specific aspects are identified. Use of the aspects UserAgent and Device serves to disambiguate the usage of properties such as Vendor . Implementations and other vocabularies may define other values for aspects.

This document identifies the relationship between its properties and the two aspects of the Delivery Context defined here. This does not constrain the generality of applying those properties to other aspects.

3 Properties

This is a list of the properties in the DDR Core Vocabulary. Data types are as defined in [XSD-Part2] . Refer to [DDR-API] for allowable identifier syntax, for allowable value datatypes data types and how to represent enumerations in vocabularies that are to be used with the DDR-API.

Namespace ids are tentative

The property identifiers are associated with the namespace http://www.w3.org/2008/01/ddr-core-vocabulary-property-ids . 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.

Drop this along with other references to UWA Ontology except as a note in section 2. Bindings to the UWA Ontology are tentative. 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".

3.1 Vendor

3.1.1 ID

vendor

3.1.2 Associated Aspects

UserAgent, Device

3.1.3 Description

The name of the maker (OEM) of a device, browser or some other component (e.g. Mozilla).

3.1.3 3.1.4 Type

string .

3.1.4 3.1.5 Related Properties

model , version

3.1.5 Ontology Links The following are for discussion deviceVendor webBrowserName 3.1.6 Note

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.

3.2 Model

3.2.1 ID

model

3.2.2 Associated Aspects

UserAgent, Device

3.2.3 Description

The model name of a device, browser or some other component (e.g. Firefox).

3.2.3 3.2.4 Type

string .

3.2.4 3.2.5 Related Properties

vendor , version

3.2.5 Ontology Links The following are for discussion deviceModel webBrowserName 3.2.6 Note

See deviceVendor above.

3.3 Version

3.3.1 ID

version

3.3.2 Associated Aspects

UserAgent, Device

3.3.3 Description

The version number of a component (e.g. 2.0.0.10)

3.3.3 3.3.4 Type

string .

3.3.4 3.3.5 Related Properties

vendor , model

3.3.5 Ontology Links The following are for discussion deviceModel webBrowserVersion 3.3.6 Note

See deviceVendor above.

3.4 Display Width

3.4.1 ID

displayWidth

3.4.2 Associated Aspects

UserAgent, Device

3.4.3 Description

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.

3.4.3 3.4.4 Measurement

The pixels are counted from the top left corner to the top right corner, and the result expressed as an integer.

3.4.4 3.4.5 Type

nonNegativeInteger .

3.4.5 3.4.6 Related Properties

displayHeight

3.4.6 Ontology Links The following is for discussion pixelCount 3.4.7 Note

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.

3.5 Display Height

3.5.1 ID

displayHeight

3.5.2 Associated Aspects

UserAgent, Device

3.5.3 Description

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.

3.5.3 3.5.4 Measurement

The pixels are counted from the top left corner to the bottom left corner, and the result expressed as an integer.

3.5.4 3.5.5 Type

nonNegativeInteger .

3.5.5 3.5.6 Related Properties

displayWidth

3.5.6 Ontology Links The following is for discussion pixelCount 3.5.7 Note

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.

3.6 Display Color Depth

3.6.1 ID

displayColorDepth

3.6.2 Associated Aspects

Device

3.6.3 Description

The color depth of a display.

3.6.3 3.6.4 Measurement

Count the number of bits usable for color definition.

3.6.4 3.6.5 Type

nonNegativeInteger .

3.6.5 Related Properties 3.6.6 Ontology Links The following is for discussion Display-BitsPerPixel 3.6.7 Note

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.

3.7 Input Devices

3.7.1 ID

inputDevices

3.7.2 Associated Aspects

Device

3.7.3 Description

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.

3.7.3 3.7.4 Measurement

Observation of features or study of specifications.

3.7.4 3.7.5 Type

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

3.7.5 Related Properties 3.7.6 Ontology Links The following are for discussion TactileInputType-keyboardTypeName PointingInputType-pointingTypeName 3.7.7 Note

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.

3.8 Markup Support

3.8.1 ID

markupSupport

3.8.2 Associated Aspects

UserAgent

3.8.3 Description

Set of mark-up languages a client supports.

3.8.3 3.8.4 Measurement

Claim of conformance by the vendor.

3.8.4 3.8.5 Type

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]

3.8.5 Related Properties 3.8.6 Ontology Links The following is for discussion PageMarkupSupport 3.8.7 Note

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.

3.9 Stylesheet Support

3.9.1 ID

stylesheetSupport

3.9.2 Associated Aspects

UserAgent

3.9.3 Description

Set of Style Sheet languages a client supports.

3.9.3 3.9.4 Measurement

Claim of conformance by the vendor.

3.9.4 3.9.5 Type

Enumeration with values chosen from the following (or other values supported by individual DDRs):

Value Description Reference
css10 CSS Level 1 [CSS10]
css21 CSS Level 2 Revision 1 [CSS21]
wcss10 WCSS [WCSS]

3.9.5 Related Properties 3.9.6 Ontology Links The following is for discussion StyleLanguage 3.9.7 Note

Style sheets are needed to define how the page should be laid out, positions and colors.

3.10 Image Format Support

3.10.1 ID

imageFormatSupport

3.10.2 Associated Aspects

UserAgent

3.10.3 Description

Set of image formats a client supports as part of a Web page.

3.10.3 3.10.4 Measurement

Claim of conformance by the vendor.

3.10.4 3.10.5 Type

Enumeration with values chosen from the following (or other values supported by individual DDRs):

Value Description Reference
gif87 GIF 87 [GIF87]
gif89a GIf GIF 89a [GIF89a]
jpeg JPEG [JPEG]
png PNG [PNG]

3.10.5 Related Properties 3.10.6 Ontology Links The following is for discussion ImageSupport 3.10.7 Note

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.

3.11 Input Mode Support

3.11.1 ID

inputModeSupport

3.11.2 Associated Aspects

UserAgent

3.11.3 Description

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.

3.11.3 3.11.4 Measurement

Test using <input type="text"> controls specifying the format with the mechanisms cited.

3.11.4 3.11.5 Type

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. [@@ref] [OpenWave-Format-Attribute]
useWCSS Use the WCSS -wap-input-format property. [WCSS]
useInputmodeAttribute Use the inputmode attribute. [XHTMLBasic11]

3.11.5 Related Properties 3.11.6 Ontology Links The following is for discussion none 3.11.7 Note

Assists user with input by setting the device input mode appropriately.

3.12 Cookie Support

3.12.1 ID

cookieSupport

3.12.2 Associated Aspects

UserAgent

3.12.3 Description

The ability of a client to store cookies and send them when appropriate.

3.12.3 3.12.4 Measurement

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.

3.12.4 3.12.5 Type

boolean .

3.12.5 Related Properties 3.12.6 Ontology Links WebBrowser-browserSupportsCookies 3.12.7 Note

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.

3.13 Script Support

3.13.1 ID

scriptSupport

3.13.2 Associated Aspects

UserAgent

3.13.3 Description

Which scripting languages are supported.

3.13.3 3.13.4 Measurement

Manufacturer claim of support of a scripting language or dialect.

3.13.4 3.13.5 Type

Enumeration with values chosen from the following list (or other values supported by individual DDRs):

Value Description Reference
ecmascript-MP Supports Ecmascript MP. ECMAScript Mobile Profile [@@ref] [ECMAScript-MP]
3.13.5 Related Properties 3.13.6 Ontology Links @@LINK-TO-UWA-ONTOLOGY@@ is there one? 3.13.7 Note

A References

DDR-API
Device Description Repository Simple API (to be published) (See )
UWA-Ontology
Delivery Context Ontology, Rhys Lewis (ed), W3C Editor's Draft 30 November 2007 (See http://www.w3.org/2007/uwa/editors-drafts/DeliveryContextOntology/2007-11-30/DCOntology.html )
DIGLOSS
W3C Glossary of Terms for Device Independence, Rhys Lewis (ed), W3C Working Draft 18 January 2005 (See http://www.w3.org/TR/di-gloss/ )
XSD-Part2
XML Schema Part 2: Datatypes Second Edition, Paul V. Biron, Ashok Malhotra (eds.), W3C Recommendation 28 October 2004 (See http://www.w3.org/TR/xmlschema-2/ )
CSS10
Cascading Style Sheets, level 1, Håkon Wium Lie, Bert Bos, W3C Recommendation 17 Dec 1996, revised 11 Jan 1999 (See http://www.w3.org/TR/REC-CSS1 )
CSS21
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 http://www.w3.org/TR/CSS21 )
WCSS
Wireless CSS Specification, Open Mobile Alliance, Candidate Version 1.1 – 09 Jun 2004 (See http://www.openmobilealliance.org/release_program/docs/Browsing/V2_3-20050118-C/OMA-WAP-WCSS-V1_1-20040609-C.pdf )
GIF87
G I F (tm) Graphics Interchange Format (tm), CompuServe Incorporated, 15 June 1987 (See http://www.w3.org/Graphics/GIF/spec-gif87.txt )
GIF89a
GRAPHICS INTERCHANGE FORMAT (sm), Version 89a, CompuServe Incorporated, 1990 (See http://www.w3.org/Graphics/GIF/spec-gif89a.txt )
JPEG
Recommendation T.81, 18 September 1992 (See http://www.w3.org/Graphics/JPEG/itu-t81.pdf )
PNG
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 http://www.w3.org/TR/PNG/ )
XHTMLBasic10
XHTML Basic, Mark Baker, Masayasu Ishikawa, Shinichi Matsui, Peter Stark, Ted Wugofski, Toshihiko Yamakami, W3C Recommendation 19 December 2000 (See http://www.w3.org/TR/2006/WD-xhtml-basic-20060705/ )
XHTMLBasic11
XHTML Basic 1.1, Shane McCarron, Masayasu Ishikawa et al., 13 July 2007 (See http://www.w3.org/TR/2007/CR-xhtml-basic-20070713 )
XHTMLMP
XHTML Mobile Profile, Open Mobile Alliance, 29 October 2001 (See http://www.openmobilealliance.org/tech/affiliates/wap/wap-277-xhtmlmp-20011029-a.pdf )
ECMAScript-MP
ECMAScript Mobile Profile, A Wireless Markup Scripting Language, Version 1.0, 20 Oct 2006, MOA-WAP-ESMP-V1_0-20061020-A (Zipped MS Word) (See http://www.openmobilealliance.org/ftp/Public_documents/BT/MAE/Permanent_documents/OMA-WAP-ESMP-V1_0-20061020-A.zip )
OpenWave-Format-Attribute
XHTML-MP Style Guide Chapter 5 - Forms: Collecting User Data (See http://developer.openwave.com/dvl/support/documentation/guides_and_references/xhtml-mp_style_guide/chapter5.htm )

B Acknowledgments

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?