W3C

CDI WICD Profile

Editor's draft September 2007

This Version:
NONE
Latest Version:
NONE
Editors:
Steve Speicher (IBM Corporation) <sspeiche@us.ibm.com>

Abstract

This document specifies WICD (Core/Full) 2.0, a Compound Document profile based on XHTML, CSS, SVG and XForms, which is targeted at desktop agents.

Compound Document is the W3C term for a document that combines multiple formats.

WICD stands for Web Integration Compound Document.

Status of this Document

In early development of the CDI WICD profiles, it will be done in one document. Then split into appropriate documents: core and full profile.

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 a First Public Working Draft of the Compound Documents by Inclusion Framework (editor's draft). Public comments to this Working Draft can be made 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 Clients Activity within the W3C Interaction Domain.

This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

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.

Table of Contents

1. Introduction

This section is informative.

Combining content delivery formats can often be desirable in order to provide a seamless experience to the user.

For example, XHTML-formatted content can be augmented by SVG objects, to create a more dynamic, interactive and self adjusting presentation.

A set of standard rules is required in order to provide this capability across a range of user agents and devices.

These are examples of Compound Documents:

This document defines a generic language-independent processing model for combining arbitrary document formats.

The Compound Document Framework is language-independent. While it is clearly meant to serve as the basis for integrating W3C's family of XML formats within its Interaction Domain (e.g., MathML, SMIL, SVG, VoiceXML, XForms, XHTML, XSL) with each other, together with CSS and the DOM; it can also be used to integrate non-W3C formats with W3C formats or integrate non-W3C formats with other non-W3C formats.

1.1. Conformance

Everying in this specification is normative except for diagrams, examples, notes and sections marked non-normative.

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 [RFC2119].

This specification defines the following classes of products:

conforming implementation
A user agent that implements all interfaces described in this specification and follows all must-, required- and shall-level of critera in this specification.
conforming document
A document that follows all must-, required- and shall-level of critera in this specification that apply to document authors.
conforming authoring tool
One that produces conforming documents.

1.2. Reference and Inclusion

document relationships

1.3.1. WICD Core 2.0

WICD Core is the foundation of rich multimedia content and describes rules for combining Hypertext Markup Language (XHTML) and scalable child objects, such as Scalable Vector Graphics (SVG) in a non device specific manner. WICD (pronounced "wicked") is an acronym for Web Integrated Compound Document.

WICD builds upon CDRF 1.0 and CDIF 2.0.

1.3.2. WICD Profiles 2.0

Profiles designed to enable rich multimedia content on a variety of devices such as: mobile handset devices, dekstop-type agents, and others.

WICD 2.0 profiles will require both CDI and CDR integration. There will be no CDI only profiles.

2. Profile Contents

Fill in references and text to profile contents

2.1. XHTML 1.1

Conformant WICD Full 2.0 by Inclusion user agents must support XHTML 1.1 - Module-based XHTML as a root document and language.

Conformant WICD Full 2.0 by Inclusion user agents must support XHTML 1.1 - Module-based XHTML as a child language.

2.1.1. XHTML MIME Type

XHTML documents authored for the WICD Full 2.0 by Inclusion profile should be associated with the "application/xhtml+xml" mime type.

2.2. SVG 1.2 Tiny

Conformant WICD Full 2.0 by Inclusion user agents must support Scalable Vector Graphics Tiny 1.2 [SVGT12] specification as a child language.

Per Hamburg07F2F, this profile will be the CDI version of the WICD work from CDR, therefore causing new items like XForms and SMIL Timing to fall to a new profile.

2.3. XForms 1.1

Conformant WICD Full 2.0 by Inclusion user agents must support XForms 1.1 [XFORMS11] specification as a child language.

2.4. SMIL Timing Module

Conformant WICD Full 2.0 by Inclusion user agents must support SMIL Timing Module [SMILTIME] specification as a child language.

2.5. CSS

Fill in reference

2.6. ECMAScript

Fill in reference

3. Identification

What the profile identifier is and how it should be used.

ACTION-662 on Steve

4. Document interfaces

Define how SVGDocument and HTMLDocument are minimally needed and if there are any conflicts to resolve (like title.

ACTION-663 on Doug

5. Compounding Semantics

5.1. SVG in XHTML

ACTION-661 on Doug

5.2. XHTML in SVG

ACTION-660 on Doug

Per Hamburg07F2F, this profile will be the CDI version of the WICD work from CDR, therefore causing new items like XForms and SMIL Timing to fall to a new profile.

5.3. XForms in XHTML

5.4. XForms in SVG

5.5. XHTML in XForms

5.6. SVG in XForms

6. Appendix: Schema

Fill in with schema definition

Acknowledgements

This section is informative.

The editors would like to thank the following contributors: