1
Introduction
(This section is informative)
The WICD Mobile profile is primarily designed to enable
rich multimedia content on mobile handset devices. These are
devices with:
- small, narrow screens (approximately 2 to 4 inch, up to 30-40
characters per line)
- 4- or 8-way joystick navigation (no pointing device)
2 Compound Document by Reference Framework
Compliancy
This document contains information, which is specific to the
WICD Mobile 1.0 profile. 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).
[ assert-implement1:
Conformant WICD Mobile 1.0 user
agents must implement the
including the extended DOM API's and
additional Events. ]
[ assert-implement2:
Conformant WICD Mobile 1.0 user
agents must implement
]
The following image shows the relation between WICD and
CDRF documents. 
The following is a sample WICD Mobile 1.0 markup:
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.1//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic11.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>
3 Document Formats
3.2 ECMAScript 3rd Edition Compact Profile
[ assert-ecmascript:
Conformant WICD Mobile 1.0 user
agents must support
ECMAScript 3rd Edition Compact Profile
(ES-CP) as a scripting language. ]
3.2.1 ECMAScript MIME Type
[ assert-ecmascript-mime:
ECMAScript documents should be associated with the
"application/ecmascript" mime type. ]
3.5 Bitmap formats
[ assert-bitmap-formats:
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. ]
3.6 Audio formats
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.
[ assert-audio-timing: 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.
[ assert-audio-formats:
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. ]
3.7 Video formats
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.
[ assert-video-timing: 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.
[ assert-video-formats:
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. ]