Copyright © 2005 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
This document specifies WICD Mobile 1.0, a Compound Document profile based on XHTML, CSS and SVG, which is targeted at mobile agents.
Compound Document is the W3C term for a document that combines multiple formats.
WICD stands for Web Integration Compound 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/.
This is the 19 December 2005 Last Call Working Draft of the WICD Mobile Profile. The Compound Document Formats Working Group explicitly requests comments on this specification. Please send them to public-cdf@w3.org. This list is archived and acceptance of this archiving policy is requested automatically upon first post. To subscribe to this list send an email to public-cdf-request@w3.org with the word subscribe in the subject line.
The deadline for Last Call comments is 27 January 2006.
This document has been produced by the Compound Document Formats Working Group as part of the Rich Web Client Activity within the W3C Interaction Domain.
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.
Per section 4 of the W3C Patent Policy, Working Group participants have 150 days from the title page date of this document to exclude essential claims from the W3C RF licensing requirements with respect to this document series. Exclusions are with respect to the exclusion reference document, defined by the W3C Patent Policy to be the latest version of a document in this series that is published no later than 90 days after the title page date of this document.
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.
1 Introduction
1.1 Scope
2 Document Formats
2.1 Updated version of XHTML Basic
2.1.1 XHTML MIME Type
2.2 ECMAScript 3rd Edition Compact Profile
2.2.1 ECMAScript MIME Type
2.3 Updated version CSS Mobile Profile
2.4 SVG Tiny 1.2
2.5 Bitmap formats
2.6 Audio formats
2.7 Video formats
3 User Agent
3.1 Identification
3.2 DOM Level 3
3.2.1 Keyboard Event Naming
3.3 Intended Layout
3.3.1 Stylesheet being provided for handheld agents
3.3.2 No stylesheet being provided for handheld agents
3.3.3 Switching off mousepointer emulation for handheld content
A Definitions
B Conformance
C References
D Authoring Guidelines (Non-Normative)
E Acknowledgements (Non-Normative)
(This section is informative)
The WICD Mobile profile is primarily designed to enable rich multimedia content on mobile handset devices. These are devices with:
This document contains information, which is specific to the WICD Mobile 1.0 profile. User agents, conformant to the WICD Mobile 1.0 profile, must also implement:
Any information that applies to all WICD profiles, is compiled into the WICD Core 1.0 document. Any information that applies to "Compound Documents" in general, can be found in the documents describing the "Compound Document Framework" (CDR/CDI).
The following image shows the relation between WICD and CDF documents.
The following is a sample WICD Mobile 1.0 markup:
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>Example WICD Mobile content</title>
</head>
<body>
<h1>Example WICD Mobile content<h1>
<object type="image/svg+xml" src="child.svg" width="50%" />
</body>
</html>
[XHTMLBasic XHTML Basic. W3C Recommendation 19th December 2000
For reference: [XHTMLMP12] “XHTML Mobile Profile 1.2” (PDF)
Conformant user agent must support XHTML Basic as the root document.
| Editorial note | |
| We try to harmonize XHTML MP 1.2 specific features into XHTML Basic. We concluded that the best we can do, currently, is a forward reference to an updated XHTML Basic. | |
Documents authored for WICD Mobile 1.0 should be associated with the application/xhtml+xml mime type.
Conformant WICD Mobile user agents must support ECMAScript 3rd Edition as a scripting language.
CSS Mobile Profile 1.0 (W3C Candidate Recommendation 25 July 2002)
For reference: [Wireless Profile CSS 1.1] (PDF) OMA Candidate Version 1.1 – 09 Jun 2004
| Editorial note | |
| We try to harmonize Wireless CSS specific features into CSS MP. We concluded that the best we can do, currently, is a forward reference to an updated CSS MP. WICD Mobile needs to reference selected features of CSS 2.1 (Rightsizing). WICD Mobile needs these properties: 'min-width', 'max-width', 'min-height' and 'max-height'. WICD Mobile needs support for the 'position' property (absolute, relative). WICD Mobile needs support for the 'outline' property (in particular: outline-style hidden). | |
Conformant WICD Mobile 1.0 user agent must support Scalable Vector Graphics (SVG) Tiny 1.2 Specification while referenced from XHTML.
The viewer must support JPEG/JFIF [JPEG][JFIF] and PNG [PNG] raster image formats. Other image formats may be supported in addition. For JPEG, the subset defined in [SVG12] shall be supported. For PNG, all color types and bit depths shall be supported, gamma correction shall be supported, and any alpha or transparency information shall be used to composite the image onto the background.
Audio may be incorporated into WICD 1.0 content in several ways. It may be pointed to from an XHTML object element, or an SVG audio element, or indirectly from an SVG video element where the video includes audio.
In XHTML, there are no timing elements. Thus, audio will play from the time the document is loaded until the time the document is unloaded (eg, replaced by another document as a result of following a link). In conforming WICD 1.0 content, audio referenced from an XHTML object element must have width and height of zero.
In SVG, audio may be triggered by user interaction or by animations to start, stop, or change volume.
For accessibility, conforming WICD 1.0 user agents should profile the option of switching off audio. [UAAG].
No audio format is mandated in this profile. Any audio format supported by the device must also be supported to be used with the <audio> element in SVG and <object> element in XHTML.
Video may be incorporated into WICD 1.0 content in several ways. It may be pointed to from an XHTML object element, or an SVG video element.
In XHTML, there are no timing elements. Thus, video will play from the time the document is loaded until the time the document is unloaded (eg, replaced by another document as a result of following a link).
In SVG, video may be triggered by user interaction or by animations to start, pause, rewind, or stop.
For accessibility, conforming WICD 1.0 user agents must provide the option of pausing, rewinding, or stopping video.
No video format is mandated in this profile. Any video format supported by the device must also be supported to be used with the <video> element in SVG and <object> element in XHTML.
When declaring support for WICD Mobile 1.0, a conforming user agent should use an "Accept" header with the value:
application/xhtml+xml; profile="http://www.w3.org/2005/12/wicd-mobile"
Conformant WICD Mobile 1.0 user agents must support Document Object Model (DOM) Level 3 Core Specification and Document Object Model (DOM) Level 3 Events Specification.
(This section is informative)
DOM Level 3 Events is expected to specify a default keyboard mapping for handset devices. We would like to link to this specification and make it mandatory.
The following key assignements may be meaningful:
- Joystick up,down,left,right and activate to be assigned to "Up","Down","Left","Right" and "Ok".
- Softkey 1 and 2 to be assigned to "F1" and "F2".
A handheld user agent, that discovers a CSS stylesheet, provided for it's device class (either by media attribute set to "handheld" or by a Media Query expression), should assume the content was created with handheld properties 'in mind'. The agent is expected to deactivate any special adaptation techniques for rendering wide screen content on a narrow screen and display the intended layout. (See also the "Media Queries" and "Media Features" sections in the "WICD Core" document.)
(This section is informative)
A handheld user agent should also not activate special content adaptation techniques for the narrow screen, if documents, which do not contain a stylesheet referece for the "handheld" media type, do not requires such treatment. Such documents should be rendered as is.
(This section is informative)
When switching off special adaptation techniques for rendering wide screen content on a narrow screen, vendors of handset devices should also switch off any type of mouse pointer emulation. They are encouraged to implement a two dimensional, flat graphical focus navigation as described in WICD Core.
The terms used in this document are specified in Compound Document by Reference Framework 1.0.
This specification defines conformance for several classes of products:
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "may", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 (see http://www.ietf.org/rfc/rfc2119.txt). However, for readability, these words do not appear in all uppercase letters in this specification.
At times, this specification recommends good practice for authors and user agents. These recommendations are not normative and conformance with this specification does not depend on their realization. These recommendations contain the expression "We recommend ...", "This specification recommends ...", or some similar wording.
WICD Mobile 1.0 Document Conformance:
A conforming document must conform to the CDR Framework 1.0, WICD Core 1.0 and WICD Mobile 1.0.
A conforming root document must be a XHTML Basic document.
A conforming script language must be a ECMAScript Compact Profile.
A conforming referenced document can be a SVG Tiny document.
A conforming style language is CSS Mobile Profile.
WICD Mobile 1.0 User Agent Conformance:
A comformant user agent MUST support all previously described comformant content.
A conformant user agent must implement all three of the following specifications: CDR Framework 1.0, WICD Core 1.0 and WICD Mobile 1.0.
A scalable background image does not need to provide support for interaction, such as zooming, panning, linking and mouse events.
WICD Mobile 1.0 content authoring is similar to any other XHTML, CSS, SVG based content authoring. However, due constraints in resources with hardware and user agent implementations, the content authors are encouraged to limit use of complex computation sensitive operations.
More guidelines can be found from Mobile Web Best Practices 1.0.
The editors would like to thank the contributors: