Warning:
This wiki has been archived and is now read-only.

DeviceDescriptionLandscapePreamble

From Device Description Working Group Wiki
Jump to: navigation, search

This is the Preamble to the document. See the DeviceDescriptionLandscape overview.

Abstract

Developing Web content for mobile devices is more challenging than developing for the desktop Web. Compared to desktop Web clients, mobile Web devices come in a much wider range of shapes, sizes and capabilities. The mobile Web developer relies upon accurate device descriptions in order to dynamically adapt content to suit the client.

This Note describes what efforts the W3C and other organizations are doing in order to provide accurate device descriptions.

This Note should be read in conjunction with the DDWG Ecosystem [DDWG-Ecosystem] document. This Note, together with the Ecosystem document, provides input to the proposed DDWG Requirements document as described in the DDWG Charter [DDWG-Charter].

Status of this Document

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 a First Public Working Draft and has been produced as part of the W3C Mobile Web Initiative, Device Description Working Group [DDWG], following the procedures set out for the W3C Process. The authors of this document are members of the W3C Mobile Web Initiative, Device Description Working Group ( members only ). Feedback can be directed to the DDWG Public Mailing List, which is also archived.

The Device Description Working Group does not intend this document to become a W3C Recommendation. Therefore the document has no associated W3C Patent Policy licensing obligations.