Copyright © 2007 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.
This ...
This document was produced under the 5 February 2004 W3C Patent Policy. The Working Group maintains a public list of patent disclosures relevant to this document; that page also includes instructions for disclosing [and excluding] a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) with respect to this specification should disclose the information in accordance with section 6 of the W3C Patent Policy.
This document is an editors' copy that has no official standing.
1 Introduction
1.1 The Delivery Chain
2 Guidance for Delivery Chain Component Developers
2.1 Communication Between Components
2.2 Guidance for Browser Developers
2.3 Guidance for Content Transformation Server Developers
2.4 Guidance for Server Developers
3 Guidance for Authors
3.1 Detecting the Presence of Delivery Chain Components
3.2 Authoring in the Presence of Content Transformation Servers
3.3 Authoring for Full Web Experience Browsers
3.4 Authoring for Content Adaptation
A References
A.1 Normative References
A.2 Informative References
B Changes in this Version (Non-Normative)
C Acknowledgements (Non-Normative)
Description of the various actors involved in the delivery of material from origin server to client, and their roles. Includes the technical components, such as adapting origin servers, content transformation servers, browsers etc. and also authors and users.
Discuss the need for a mechanism for communication between components
Describe the particular mechanism chosen - HTTP headers for example
Need for ability to 'pretend' to be a desktop
Need for ability to accept optimised mobile versions
Need for ability to allow user to choose between available versions of an experience
Details of how browsers communicate with the rest of the delivery chain
Need for content transformation servers to transform materials for use on mobile devices
Need for content transformation servers to 'pretend' to be a desktop
Need for content transformation servers to recognise optimised mobile versions of content and to pass it through unchanged
Need for content transformation servers to pass device information unchanged to other components of the delivery chain
Details of how content transformation servers communicate with the rest of the delivery chain
Need for access to accurate device information
Need for ability to identify content as optimised for device
Details of how content transformation servers communicate with the rest of the delivery chain
Identifying the various components that are present
Based on the communications mechanism discussion from the previous section
| Editorial note: Rhys | 9/8/2007 |
| This is a dummy entry as a placeholder | |
| Editorial note: Rhys | 9/8/2007 |
| This is a dummy entry as a placeholder | |
This section summarises the changes made since the version of the document issued as a second last call.
This is the first version of this document.
This document was produced with the participation of the Mobile Web Initiative Best Practices Working Group participants:
| Editorial note: Rhys | 9/8/2007 |
| This is an incomplete list as a placeholder | |