Copyright © 2006 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
This document specifies WICD Full 1.0, a Compound Document profile based on XHTML, CSS and SVG, targeted at desktop 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/.
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.
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
2 Compound Document by Reference
Framework Compliancy
3 Profile Requirements
3.1 XHTML
1.1
3.2 ECMAScript 3rd Edition
3.3 CSS
2.1
3.4 SVG Tiny
1.2
3.5 Bitmap
formats
3.6 Audio
formats
3.7 Video
formats
3.8 User Agent
Identification
3.9 DOM Level 3
3.10 XMLHttpRequest
A Definitions
B Conformance
C References
D Authoring Guidelines
(Non-Normative)
E Acknowledgements
(Non-Normative)
F Changes Log (Non-Normative)
(This section is informative)
The WICD Full 1.0 profile is designed to enable rich multimedia content on desktop and high capability handheld agents. These are agents with:
Conformant WICD Full 1.0 user agents must implement the
including the extended DOM API's and additional Events.Conformant WICD Full 1.0 user agents must implement
WICD Full 1.0 is a superset of WICD Mobile 1.0.
The image below shows the relation between WICD and CDRF documents.
Conformant WICD Full 1.0 user agents must support XHTML 1.1 - Module-based XHTML as the root document.
Conformant WICD Full 1.0 user agents must support ECMAScript 3rd Edition as a scripting language.
Conformant WICD Full 1.0 user agents must support Cascading Style Sheets, level 2 revision 1 [CSS21] specification.
Conformant WICD Full 1.0 user agents must support Scalable Vector Graphics Tiny 1.2 [SVGT12] specification.
The conformant user agents 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 [SVGT12] 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 Full 1.0 content in several ways. It may be linked 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 Full 1.0 content, audio referenced from an XHTML object element must have a width and height of zero.
In SVG, starting, stopping or changing the volume may be triggered by user interaction or by animations.
For accessibility, conforming WICD Full 1.0 user agents should provide the option of switching off audio. [UAAG].
Some audio formats may be mandated in this profile. Any audio format supported by the device must also be supported for use with the <audio> element in SVG and <object> element in XHTML.
Video may be incorporated into WICD Full 1.0 content in several ways. It may be linked 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, starting, pausing, rewinding or stopping the video may be triggered by user interaction or by animations.
For accessibility, conforming WICD Full 1.0 user agents must provide the option of pausing, rewinding, or stopping video.
Some video formats may be mandated in this profile. Any video format supported by the device must also be supported for use with the <video> element in SVG and <object> element in XHTML.
When declaring support for WICD Full 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"
Future versions of the WICD Full profile, which are compatible with WICD Full 1.0, must use the same profile string, using the same format, but with a later date. (Example: application/xhtml+xml; profile="http://www.w3.org/2007/06/wicd")
Conformant WICD Full 1.0 user agents must support Document Object Model (DOM) Level 3 Core Specification.
Conformant WICD Full 1.0 user agents must support Document Object Model (DOM) Level 3 Events Specification.
Conformant WICD Full 1.0 user agents must support the additional features described in WICD Mobile 1.0 Appendix F Focus Traversal Support.
Conformant WICD Full 1.0 user agents must support the SVG Micro DOM (uDOM) specification.
Conformant WICD Full 1.0 user agents must support the ElementTraversal interface on all DOM objects which implement the org.w3c.dom.Element interface.
Conformant WICD Full 1.0 user agents must support the DocumentView interface on all implementations of the org.w3c.dom.Document interface.
In conformant WICD Full 1.0 user agents, the org.w3c.dom.AbstractView associated with an org.w3c.dom.DocumentView must be an implementation of the Window interface as defined in the Window Object 1.0 specification.
Conformant WICD Mobile 1.0 user agents must support the XMLHttpRequest Object.
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 Full 1.0 User Agent Conformance:
Conformant WICD Full 1.0 user agents must implement the Compound Document by Reference Framework 1.0 (CDR 1.0) including the extended DOM API's and additional Events.
Conformant WICD Full 1.0 user agents must implement WICD Core 1.0.
WICD Full 1.0 is a superset of WICD Mobile 1.0.
Conformant WICD Full 1.0 user agents must support XHTML 1.1 - Module-based XHTML as root document.
Conformant WICD Full 1.0 user agents must support ECMAScript 3rd Edition as a scripting language.
Conformant WICD Full 1.0 user agents must support the Cascading Style Sheets, level 2 revision 1 [CSS21] specification.
Conformant WICD Full 1.0 user agents must support the Scalable Vector Graphics Tiny 1.2 [SVGT12] specification.
The conformant user agent 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 [SVGT12] 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.
When declaring support for WICD Full 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".
Conformant WICD Full 1.0 user agents must support Document Object Model (DOM) Level 3 Core Specification.
Conformant WICD Full 1.0 user agents must support Document Object Model (DOM) Level 3 Events Specification.
Conformant WICD Mobile 1.0 user agents must support the XMLHttpRequest Object.
WICD Full 1.0 Document Conformance:
XHTML documents authored for the WICD Full 1.0 profile should be associated with the "application/xhtml+xml" mime type.
ECMAScript documents authored for the WICD Full 1.0 profile should be associated with the "application/ecmascript" mime type.
WICD Full 1.0 authoring is similar to authoring any other XHTML, CSS, and SVG based content except that conformant user agents are guaranteed to show this content properly together. Therefore, authors are encouraged to take advantage of each individual languages while designing content.
To enable the largest possible audience for the content, authors should make the content scalable and test with different sizes of windows and screens. All WICD Full 1.0 user agents have the same visualization capabilities, but the physical screen sizes (and their resolutions) may differ a lot.
The editors would like to thank the contributors: