Copyright © 2007 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
This document specifies WICD Core 1.0, a device independent Compound Document profile based on XHTML, CSS and SVG.
Compound Document is the W3C term for a document that combines multiple formats.
WICD stands for Web Integration Compound Document and is based on the idea of integrating existing markup language formats in preference to inventing new markup.
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 W3C Candidate Recommendation of WICD Core 1.0. This document is based upon the WICD Core 1.0 published on 22 November 2006. The current document contains editorial improvements, and minor changes in response to Last Call comments. The disposition of Last Call comments is available (first last call comments, second last call comments). Changes are summarized in F Changes Log to review changes since the last Working Draft.
Publication as a Candidate Recommendation 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.
The Compound Document by Reference Framework (CDRF) and Web Integration Compound Document (WICD) Core have dependencies on the following documents:
Document Object Model (DOM) Level 3 Events Specification
The Compound Document Format Working Group will advance CDRF 1.0 and WICD Core 1.0 to Proposed Recommendation no sooner than 01 September 2007; the Working Group estimates that by 01 December 2007 the following exit criteria have been met:
the dependent documents must have reached CR status;
there are at least two implementations of CDRF and WICD Core enabled user agents;
each individual test case in the WICD Core test suite shall be passed by at least two implementations.
It is not required, as a condition to exit CR, that a single implementation passes all CDRF and WICD profile test cases. Once CDRF and WICD reach Recommendation status, however, implementations should aim for 100% compliance.
Implementation results will be released publicly. These results are only serving as proof of CDRF and WICD profiles implementability. They are only a snap shot of the actual implementation behaviors at one moment of time and should not be construed as describing the conformance status of implementations at any later date.
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. 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.
Feedback on this specification should be sent 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 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.
1 Introduction
1.1 Scope of this Specification
1.2 Related Specifications
1.3 Relationship to Referenced Specifications
2 Root, Parent and Child Documents
2.1 Referencing Child Documents
3 Scalable Child Content
3.1 Scalable Child Content Formats
3.2 Scalable Child Content Use Cases
3.3 Scalable Child Content Layout
4 Other Child Content Formats
4.1 Raster formats
4.2 Audio formats
4.3 Video formats
4.4 Child content accessibility guidelines
5 Hyperlinking
5.1 Link Activation
6 Focus Handling
6.1 Focus Modes
6.2 Focus Navigation
6.3 Focus Event triggered Child Content Animations
7 Font Support
7.1 System Fonts
7.2 Font Naming
7.3 Font Sharing
8 Content Encoding
9 Synchronization Support
9.1 Temporal Synchronization of Media
9.2 Timeline Initialization
9.3 Play Animations while Document is loading
10 Intended Layout
10.1 Media Queries
10.2 Style sheet being provided for specific agent classes
10.3 No style sheet being provided to handheld agents
A Definitions
B Object <param> attributes defined in WICD Core
C Conformance
D References
D.1 Normative
D.2 Informative
E Acknowledgements (Non-Normative)
F Changes Log (Non-Normative)
(This section is informative)
This Web Integration Compound Document (WICD) Core specification describes rules for combining Extensible Hypertext Markup Language (XHTML), Cascading Style Sheets (CSS), and Scalable Child Content formats, such as Scalable Vector Graphics (SVG), in a device independent manner. WICD Core 1.0 is based upon the Compound Document by Reference Framework 1.0 (CDRF) and serves as a foundation for the creation of rich multimedia content profiles.
(This section is informative)
The image below shows the relation between CDF and WICD specifications.
CDRF describes generic rules and behavior for combining sets of standalone XML formats.
NOTE: 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., CSS, MathML, SMIL, SVG, VoiceXML, XForms, XHTML, XSL) with each other, it can also be used to integrate non-W3C formats with W3C formats or integrate non-W3C formats with other non-W3C formats.
The WICD Mobile 1.0 profile is designed to enable rich multimedia content on mobile handset devices. It may also be appropriate for other handheld devices. However, WICD Mobile addresses the special requirements of mass-market, single-handed operated devices and enables publishers to target these type of devices without having to evaluate the user agent identification string. In this profile, child documents are embedded by reference (CDRF).
WICD Mobile 1.0 builds upon WICD Core 1.0.
The WICD Full 1.0 profile is designed to enable rich multimedia content on desktop-type agents. It may also be appropriate for high capability handheld devices with a pointing device. In this profile, child documents are embedded by reference (CDRF).
WICD Full 1.0 builds upon WICD Mobile 1.0.
This document may contain clarifications, refinements, or specific implementation examples of content specified in referenced documents. Should there be a conflict with any text in this document and the referenced document, then the referenced document is the normative reference.
A document that references other documents is a parent document. A root document is the topmost parent document. A document is a child document, if it is referenced by other documents. A child document can be a parent document at the same time.
Any profile, conforming to WICD Core 1.0, must support XHTML as root document.
In XHTML, there are many elements (like object, img, iframe) that are used to reference child documents. In a similar way, child documents can be referenced from CSS declarations.
Any profile, conforming to WICD Core 1.0, must support the XHTML <object> element as a means of referencing Scalable Child Content.
Scalable Child Content appears as rectangular objects, which in their normal presentation, can always fit the screen or destination box, because they are scalable and usually meant to be viewed as a whole. Scalable Child Content can have a Document object model (e.g. SVG). It can also be native content (have a binary format or be applications).
Any profile, conforming to WICD Core 1.0, must support SVG documents as a Scalable Child Content format.
Later versions of WICD Core may mandate additional formats. Different WICD profiles may support different versions of SVG.
Scalable Child Content can be referenced from a parent document as foreground objects, as background images or as overlay objects.
Any Scalable Child Content format must support these three use cases: Scalable Foreground Child Content, Scalable Background Image and Scalable Overlay Objects (Sprites).
Scalable Foreground Child Content is referenced using the XHTML <object> element. It appears on the main XHTML layer, just like raster images.
User agents must support Scalable Foreground Child Content, which may be animating, interactive and may have embedded links.
The following example shows how a SVG document is referenced from a XHTML document:
<!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">
<head>
<title>static render example</title>
</head>
<body>
<object data="icon.svg" type="image/svg+xml" width="100%">
<param name="render" value="static" />
</object>
</body>
</html>Using a XHTML 1.1 [XHTML™ 1.1 - Module-based XHTML] param element with name="render", the document author can specify whether a frozen, static, or dynamic rendering is desired. The terms static and dynamic have the same meaning as in SVG. The term frozen implies a single conversion to a raster image. Dynamic rendering is the default behavior. The value of the param element is case sensitive. Unrecognized param values shall be treated as default values. If more than one "render" parameter is provided for an element, then only the last one shall be used.
Authors are encouraged to set the render param whenever referencing multiple non-animating child objects. This may allow user agents to implement performance and memory optimizations. For example, a grid of icons can be rendered as frozen with a script setting the focused icon to dynamic.
An <object> element <param> child element with name="render" and value="dynamic" shall result in a dynamic rendering. Links shall be activatable. Animations shall play, if the timeline has started. Modifications made by script shall update the rendering. The rendering shall also update, if the size of the rendering area changes.
An <object> element <param> child element with name="render" and value="static" shall result in a static rendering. Links shall be activatable. Animations shall not play. Modifications made by script shall update the rendering. The rendering shall also update, if the size of the rendering area changes.
An <object> element <param> child element with name="render" and value="frozen" shall result in a static rendering to a raster image. Links shall not be activatable. Animations shall not play. Scripts in the SVG are disabled, but scripts outside of the SVG may still affect the DOM tree and must result in the SVG being updated. The rendering shall also update, if the size of the rendering area changes.
If not specified in the content, the behavior is as if <param name="render" value="dynamic"> had been specified.
The terms "static" and "dynamic" are defined in the Conformance section of the [Scalable Vector Graphics (SVG) Tiny 1.2 Specification].
Example:
<object data="icon.svg" type="image/svg+xml" width="100%" > <param name="render" value="static" /> <object>
For accessibility, a conformant WICD user agent must, at user option, provide a means to override author settings of this parameter. This ensures that users can a) mask unwanted distractions or b) interact with SVG interactive elements that would be masked by a 'frozen' rendering. See 5 Hyperlinking and 6 Focus Handling.
For SVG child objects, the document time used for rendering a frozen or static image shall be that given by the SVG 'snapshotTime' attribute. If no 'snapshotTime' is present in the animation, a document time of zero (0) must be used. Other Scalable Child Content formats may use a similar mechanism. Scalable Child Content lacking such capability should use a time of zero (0) for still-image rendering.
User agents must support Scalable Child Content (e.g. SVG) to be used as CSS background images.
Agents may support declarative animated background images. Scalable Child Content, used as a background image, will not provide support for scripting and interaction, such as zooming, panning, linking and user interaction events. Authors should only provide non-animating or non-interactive animating content for use as a background image. For SVG content, a snapshotTime should be provided if the optimal time for a static rendering is not zero seconds. For other formats, if there is a similar feature, it should be used. Agents that do not support animated background images, may generate a still-image presentation of the provided object. A still-image presentation of an animating object may be generated per description in 3.2.1.1 Still-Image Rendering, by using name="render" value="frozen".
The following example shows how a SVG document is placed on the XHTML background, using the CSS background-image attribute:
Use of background-image:
<html>
<body style="background-image:url(background.svg);background-attachment:fixed">
<p>This in foreground</p>
</body>
</html>The following example will set an SVG image background.svg as a fixed, non-repeating (i.e. not tiled) non-scrolling ('pinned') background, using the individual properties:
Pinned background:
body {
background-color: white;
background-image: url(background.svg);
background-repeat: no-repeat;
background-attachment: fixed;
background-position: center center
}or using the shorthand:
Pinned background, shorthand:
body { background: white url(background.svg) no-repeat fixed center center }If background.svg has its width and height set in px, then this is well-defined. If the default is declared (width="100%" height="100%"), then it will display as large as possible, where the background area to be be covered is treated as a viewport.
WICD user agents must support content layering using CSS absolute positioning in x, y and z order. This will detach a child element from the main XHTML layer and create a new transparent layer.
WICD user agents must make all visible and focusable points in the XHTML layer and the positioned Overlay Object reachable and activatable.
WICD user agents must support transparency for Overlay Objects.
Scalable Overlay Objects, referred to from the XHTML, page may be put in front of, or behind, the default XHTML layer.
Any transparent areas in the Overlay Object and in the XHTML root document must allow the layer behind to be visible.
A detailed description of the stacking level for different layers can be found in Appendix E in the [Cascading Style Sheets, level 2 revision 1 CSS 2.1 Specification] specification.
Example:
.svg-sprite
{
position: absolute;
left: 0;
top: 0;
width: 100%;
border: 0px;
}
<body>
<div>
<object class="svg-sprite" data="sprite.svg" type="image/svg+xml" />
<p>Hello 1</p>
<object data="foo.svg" type="image/svg+xml" width="100" height="50" />
<p>Hello 2</p>
</div>
</body>User agents must support interactivity in overlay elements.
User agents must support overlay images with embedded links.
Scalable Child Content is referenced by using width and/or height attributes with values relative to the destination box (which may be the full available rendering area (canvas) of the user agent or maybe a table cell). In case the Scalable Child Content has its own fixed aspect ratio, it is enough to provide only one size attribute value (width -or- height) of the object element (through CSS or directly in XHTML), when referencing it.
[Cascading Style Sheets, level 2 revision 1 CSS 2.1 Specification] contains a detailed description of the required Visual formatting model - Inline, replaced elements.
(This section is informative)
If only one size attribute value is provided, a fixed aspect ratio child element will get 'rightsized' proportionally, by being scaled to fit into the destination box.
Rightsizing example:
<object data="icon.svg" type="image/svg+xml" width="100%" />
The following illustration shows how a square, scalable element with a fixed aspect ratio, has been scaled into an available area with a requested width of 100%.
The following illustration shows, how two scalable elements with fixed aspect ratio, have been scaled into an available area, both with a requested width of 100%.
When an embedded child document fragment (such as SVG) specifies its horizontal width and omits a height specification, then the actual extent of the image is defined by the content within it. On placing such an image into a user agent, the viewport is usually a window on a 'galley' view of the entire document. In such cases, the element should float to the top of the available galley as no height is specified. This is shown in the illustrations above. Where the aspect ratio rules for the embedded graphic force the width to be less than the user agents window width, then the image should be centered horizontally (see 'Leftover Margins' below). If the dominant text layout direction is vertical text, the aforementioned rules should be adapted to the different layout flow direction in the case of 'height' being the only sizing specification.
Rendering scalable, but fixed aspect-ratio content into a fixed-sized destination area will often result in leftover margins. In case of SVG child documents: When the viewbox and the resulting viewport do not have the same aspect ratio, and preserveAspectRatio is not set to 'none' (the default being 'xMidyMid') some space is left in between the borders of the viewbox and that of the viewport.
The following illustration shows, how a square, scalable element, with a fixed aspect ratio, has been scaled into an available area (destination box) with a requested width of 100%. Because the viewport has a wider aspect ratio than the child object's viewBox, the viewport and viewBox cannot align exactly. Assuming the SVG content's root 'svg' element has 'preserveAspectRatio' of 'xMidYMid meet' (the default value), the child element's viewport will gain the width and height of the destination box, but the width and height of the resulting viewbox will be equal to the height of the available area.
Leftover margins will appear to the left and right of the child element's viewbox.
The following illustration shows, how a square, scalable element, with a fixed aspect ratio, is being scaled into an available area with a requested height of 100%. Because the viewport has a taller aspect ratio than the child object's viewBox, the viewport and viewBox cannot align exactly. Assuming the SVG content's root 'svg' element has 'preserveAspectRatio' of 'xMidYMid meet' (the default value), the child element's viewport will gain the width and height of the destination box, but the width and height of the resulting viewbox will be equal to the width of the available area.
Leftover margins will appear above and below the child element's viewbox.
When rendering scalable, but fixed aspect-ratio content into a fixed-sized destination box, the child content must render the entire viewport, including any leftover margins.
In the absence of a background color or image on the element that established the viewport (for example html:object or svg:svg) its background is transparent. In order to maximize the visual quality of the content, the parent document must be visible through the leftovers (as well as through the child content itself where it is transparent).
A defined background applies to the entire viewport (including the leftovers) so that content that spills outside of the viewbox into the leftovers is still on the correct background.
Any UI event, such as a mouse click, that hits the leftover areas, is dispatched in the same manner as UI events over non-leftover areas (i.e., to the child document)
(This section is informative)
The rendering of a WICD document may result in an overlap of content, originating from different namespaces, for example, an SVG graphic on top of some XHTML. Some user agents may provide monolithic implementations for all namespaces, whilst others may render each namespace by a separate block of executable code. For example, by providing a so-called 'plug-in' interface for each renderer.
In the case where an existing XHTML implementation is to be extended via the addition of a namespace supporting transparency (such as SVG) it is possible to provide a combined output using alpha-compositing by allowing the SVG implementation access to the output of the XHTML rendering. This would assume the XHTML base layer is opaque and the SVG layer on top would be responsible for retrieving the rendered output pixel data from the XHTML renderer and combining it with the SVG to support SVG layering on top of the XHTML. Such an approach removes the need to add any transparency support to an existing XHTML implementation whilst adding support for transparency support when new namespaces are added.
Such an approach to supporting a foreground transparency layer can be easily implemented given access to the result of rendering output of an existing implementation. In order to support such a feature, the XHTML implementation would need to notify a plugin that its rendering is complete.
The viewer must support JPEG/JFIF [Scalable Vector Graphics (SVG) Tiny 1.2 Specification], PNG [Portable Network Graphics (PNG) Specification (Second Edition)] and GIF 89a (non-interlaced, non-transparent, non-animated) raster image formats. Other image formats may be supported in addition. 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 a width and height of zero.
In SVG, starting, stopping or changing the volume may be triggered by user interaction or animations.
No audio format is mandated in WICD profiles.
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 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 video may be triggered by user interaction or by animations.
No video format is mandated in WICD profiles.
Any video format supported by the device must also be supported for use with the <video> element in SVG and <object> element in XHTML.
For accessibility, conforming WICD Core 1.0 user agents must provide the option of pausing, rewinding, or stopping video. See section 3.2 of [User Agent Accessibility Guidelines 1.0].
For accessibility, conforming WICD Core 1.0 user agents must allow the user to slow the presentation rate of rendered audio and animation content (including video and animated images). See section 4.4 of [User Agent Accessibility Guidelines 1.0].
For accessibility, conforming WICD Core 1.0 user agents must allow the user to stop, pause, and resume rendered audio and animation content (including video and animated images) that last three or more seconds at their default playback rate. They must also allow the user to navigate efficiently within rendered audio and animations (including video and animated images) that last three or more seconds at their default playback rate. See section 4.5 of [User Agent Accessibility Guidelines 1.0].
WICD compliant agents should support seamless hyperlinking originating from any of the supported document formats to all supported content types. If it is possible to link from XHTML to some other supported content type (for example: XHTML linking to RSS, Java or multimedia content), then it should also be possible to link to the same content types from any other supported document format which supports hyperlinking (for example: SVG linking to RSS, Java or multimedia content).
If linking from XHTML to any of the supported content types will result in content type specific treatment, then linking to that same format from any other supported document format (such as from SVG) should result in the same content type specific treatment. If a WICD compliant agent supports linking from XHTML to URI schemes other than http:// (for examples wtai://, tel://, mailto://, etc.), then these URI schemes should also be supported, when linked-to from any of the other supported document formats that support hyperlinking (such as from SVG).
All URI schemes, supported for hyperlinking and the related functionality, should be supported, independent of the originating document format.
When linking from XHTML to SVG, as well as from SVG to XHTML the user agent should stay the same.
(This section is informative)
Link activation behavior for hyperlinks within a child object is defined by the child object's relevant language specification. For example, if the parent document is XHTML and the child object is SVG, then the SVG specification defines the behavior for what happens when a hyperlink within the SVG object is activated.
Link activation behavior for hyperlinks within a parent object is defined by the parent object's relevant language specification.
Link activation behavior for hyperlinks within a child object is defined by the child object's relevant language specification.
Nested hyperlinks are more complicated. The following illustrates nested hyperlinks. Suppose the parent document is XHTML as follows:
<!-- parent.html --> <html:a href="LargeMap.html"> <html:object type="image/svg+xml" data="child.svg" /> </html:a>
And the child SVG document contains the following:
<!-- child.svg --> <svg:a xlink:href="DetailedCountyMap.html"> <svg:text>county map</svg:text> </svg:a>
The <svg:text> element is surrounded by two hyperlinks: a near one defined within the same SVG file and a farther one defined within the parent XHTML file. Nested hyperlinks for Compound Documents are processed in a manner consistent with the following model:
hyperlink-related event processing is compatible with the DOM3 Event model. Thus, an event such as a mouse click or a keyboard action which maps to DOMActivate will participate in capture, target and bubble phases according to the DOM3 Event specification.
elements which define hyperlinks (e.g., the <html:a> and <svg:a> elements) define implicit DOMActivate event listeners for the target and bubble phases (i.e., the useCapture parameter on the implicit addEventListenerNS() call is false), with a default action to execute a hyperlink to the identified resource.
the target element for pointer device events is established by first determining the most deeply nested child document which has content that intersects with the geometric (x,y) location of the event. Within the child document, the target element is chosen following the rules defined within the child document's language specification. (For example, the SVG specification says that the target element for pointer events generally is the topmost element on the canvas.)
The implication is that the behavior of nested hyperlinks depends on how the hyperlink is activated. Here are some examples which illustrate common possibilities:
Suppose the user gives focus to an <html:a> within the parent XHTML document above and then hits the "Enter" key to activate that link. In the example above, the <html:a> element is the event target. This would cause execution of the hyperlink to "LargeMap.html".
Suppose the user gives focus to an <svg:a> within the child SVG document and then hits the "Enter" key to activate that link. In the example above, the <svg:a> element is the event target. This would cause execution of the hyperlink to "DetailedCountyMap.html".
Suppose the user uses a mouse or other pointer device to click on the word "county map" in the above example. Because this pointing device event occurs over geometry controlled by both the parent XHTML and child SVG documents, and because the SVG document is the most deeply nested, then the target element will be chosen according to the rules in the SVG specification. In the example above, this will cause the <svg:text> element to be the event target. The <svg:a> element will receive the event after bubbling from the <svg:text> element, which will cause a hyperlink to "DetailedCountyMap.html".
Since the child document's language specification defines hyperlinking behavior, here are recommendations for language specifications for languages which might be used as child documents within the context of Compound Documents:
If specifications provide a mechanism for hyperlinking they must also define a way to target specific frames. In addition it must be defined how the current document can be replaced (the document the link is defined in), the parent document and the root document.
Relevant language specifications should include a mechanism for defining the possible targets for the hyperlink. For example, the HTML4 specification includes a 'target' attribute on the 'html:a' element which supports targets of _blank, _self, _parent, _top and <frametarget> (see http://www.w3.org/TR/html401/types.html#type-frame-target). The SVG Tiny 1.2 specification also supports a 'target' attribute on the 'svg:a' element with the same list of possible values, except with the addition of an "_replace" keyword (see http://www.w3.org/TR/SVGMobile12/linking.html#AElementTargetAttribute). The WebCGM specification also supports targets of _blank, _self, _parent, _top, _replace and <frametarget> (see http://www.w3.org/TR/REC-WebCGM/REC-03-CGM-IC.html#webcgm_3_1_2_2).
NOTE: The keyword _self does not mean the same in SVG as it does in HTML. In HTML it replaces the current document and in SVG it replaces the parent document.
Relevant language specifications should provide a clear definition of the behavior of the "_self" keyword. For SVG and WebCGM, when there is a parent HTML document which references an SVG or WebCGM graphic via html:object, the "_self" keyword causes the HTML document to be replaced by the linked content. However, when a parent HTML document references a child HTML document via html:object or html:iframe, some HTML browsers implement the "_self" keyword, so that only the child HTML document is replaced. Because of this, relevant language specifications should be clear about User Agent behavior in response to the "_self" keyword. One strategy to consider: if the primary usage scenario falls under the category of "replaced element" (see http://www.w3.org/TR/REC-CSS2/conform.html#replaced-element), as is the case with SVG, then defining "_self" to replace the parent document is appropriate.
For language specifications such as SVG which define "_self" to replace the parent document, it might be appropriate to support a "_replace" feature similar to what exists in SVG Tiny 1.2 and WebCGM. This feature causes a hyperlink to replace the child document only and to leave parents and other ancestor documents unchanged. (For example, if an SVG document is referenced by a parent HTML document via an 'html:object' element, and if the SVG document has an 'svg:a' element with target="_replace", then when that hyperlink is activated, the SVG document gets replaced but there are no changes within the parent HTML document.)
Sometimes in industry practice a plugin user agent is used to handle certain types of child documents. For example, plugins might handle SVG or MathML child documents. In these scenarios the plugin may only be able to handle particular formats via the "_replace" keyword. (For example, a MathML plugin might be able to handle only MathML content.) Because of this, relevant language specifications, that support "_replace" (or alternative syntax for the same feature), should clearly specify requirements, when "_replace" references content of the same type and content of other types. (For example, only content of the same type can be referenced with "_replace", or any type can be referenced with "_replace", but then error-processing must be defined for unknown or unsupported content.)
One potential area of ambiguity in the context of Compound Document is the meaning of the "_self" and "_parent" keywords. (See HTML4's definition at http://www.w3.org/TR/html401/types.html#type-frame-target and SVG Tiny 1.2's definition at http://www.w3.org/TR/SVGMobile12/linking.html#AElementTargetAttribute). For example, suppose a parent XHTML document references a child SVG document via an 'html:object' element and suppose the SVG document has an 'svg:a' element with target="_self". The SVG Tiny 1.2 specification says that "_self" causes both the XHTML parent frame and the child SVG to be replaced when the hyperlink is activated.
However, there are potential ambiguities if the parent language format supports its own particular notions of nested regions (e.g., frames, panes or sub-documents). It is strongly recommended that relevant language specifications clearly define how its own nested region features relate to the hyperlinking keywords _self, _parent, and _top.
WICD compliant user agents must provide the ability for users with a keyboard or joystick input device (and without a pointing device), to navigate to any focusable element in the root document and all of its descendants.
The language specifications that are used with this framework define what elements are focusable. For example, focusable items in an SVG document are defined by the SVG 1.2 focusable attribute [SVGMobile12, Element focus].
In XHTML, <object> elements are, by default, focusable and participate in the focus traversal. However, conforming WICD user agents must remove child content from the focus traversal, if the <object> element's child <param> element is set to the attribute name="focusable" and the attribute value="skip".
<object data="static-icon.svg" type="image/svg+xml" width="50%" > <param name="focusable" value="skip" /> </object>
In some situations, like in a user activatable mode for making all non interactive elements focusable, a user agent may still allow the user to focus on a child element which was originally removed from focus traversal. For instance, a user agent may allow a user to focus on a static SVG image for the purpose of saving it or interacting with it in other ways.
This section defines two modes of child element focusability.
By using the <object> element's child <param> element with the attribute name="focusable", the author of the parent document can specify whether "flat" or "hierarchical" focusability is desired for a child.
If more than one "focusable" parameter is provided for an element, then only the last one shall be used. Unrecognized param values shall be ignored.
The default focus mode depends on the User Agent. If a specific behavior is desired the content author must specify which focus mode to use.
Authors use <param name="focusable" value="hierarchical" /> to select hierarchical (activatable) focus handling for a referenced child. A user, navigating to such a child element, will have the option to activate it, or to move on, to the next focusable element. Activating the child, will provide the user with access to the child's interactivity and its focusable elements, such as embedded links and its access keys. The user must deactivate an activated child element, in order to gain access to the parents focus traversal again.
<object data="interactive.svg" type="image/svg+xml" width="80%"> <param name="focusable" value="hierarchical" /> </object>
Hierarichal Focus Handling:
Authors use <param name="focusable" value="flat" />, to make focusable elements of the child become direct participants of the parents focus traversal. Access keys, defined by child documents, may not become accessible to the user, if they are also defined by the parent or by other child element.
<object data="multifocus.svg" type="image/svg+xml" width="80%"> <param name="focusable" value="flat" /> </object>
Some types of child content will have to be "hierarchical", to properly function in the context of a Compound Document. Trying to make such child content become part of the parents "flat" focus navigation, may result in situations, where a user, using a keyboard or joystick input device, may get trapped inside a child element, with no ability to leave it again. This may happen, if the child content consumes some (or all) key events, used by the user agent focus traversal management. For instance, if key events are handled by script. Or, for example, when the child content enables zoom and pan functionality. A parent document author may also choose to make a child element "hierarchical" for other, more practical reasons. For instance, when the child has too many focusable sub elements, for the parent document to be comfortably usable.
This section describes several focus navigation models. WICD Core does not mandate a specific focus navigation model. But device-specific WICD profiles should define which focus navigation models are required. WICD profiles may require at least one of the following navigation models.
Focus Navigation can be one dimensional (linear focus ring). And on devices with a multidirectional input device (like a joystick), focus navigation can also be two dimensional (spatial).
In addition, focus navigation in a Compound Document can be hierarchical (6.1.1 Hierarchical Child Focus) or flat (6.1.2 Flattened Child Focus). This results in at least four possible focus navigation models:
One dimensional focus navigation with hierarchical child elements
One dimensional focus navigation with flattened elements
Two dimensional focus navigation with hierarchical child elements
Two dimensional focus navigation with flattened child elements
The different models are described below. Several illustrations show how focus may travel from the first focusable element in a parent document ("XHTML Link 1") to the last focusable element ("XHTML Link 8"). There is always at least one path traveling through all focusable elements of a Compound Document. In case of two dimensional focus navigation, there may be multiple ways to navigate from the first focusable element to the last.
Desktop agents, tablet's and PDA's usually allow navigation of a web document using a pointing device (mouse or stylus). Additionally, on desktop agents, the tab key can be used to navigate over focusable elements. Here, all focusable elements of a single Web document are chained in one linear path, based on the order of occurrence in the source document. This creates the so-called focus navigation ring, where advancing over the last focusable element brings the focus back to the first focusable element.
In the example shown above, the XHTML parent document contains its own focusable elements, as well as one SVG child element with focusable sub elements. Focus navigation starts from "XHTML Link 1". All focusable elements of the parent XHTML document are included in one, linear focus traversal path. The child is made accessible as one single focusable element, initially. Its focusable sub elements are not flattened into the parent document. The child needs to be manually activated by the user, for its focusable sub elements to become accessible. An activated child has to be deactivated, for the focus to be brought back up to the level of the parent XHTML document. Deactivating a child element will make the SVG child element gain focus again as a whole. Advancing the focus further will then move focus to "XHTML Link 5".
In this second model, focusable elements of a child are flattened into the focus traversal path of the parent.
As shown in the above illustration, focus moves directly from "XHTML Link 4" to "SVG Link 1". Flattened child elements do not get focused as a whole. No manual activation of a child element is required. Infact, content authors may make it impossible for users to visually detect any borders between the parent document and flattened child elements.
In this 3rd model, focus can travel freely in any direction as long as there is another focusable element. The next focusable elements are always calculated, after a focus advance event is triggered by the user. This must be done in realtime, because scripts and animations may change presentation and location of focusable elements at any time. However, child elements do get focused as a whole and will need to be activated, for their sub elements to become accessible.
In this model, focus navigation events may also be used to scroll the document. This is needed when the user agent implements scrolling functionality for documents that cannot be fully displayed.
In the illustration above, there are multiple ways of navigating through the Compound Document. Focus may travel from "XHTML Link 1" to "XHTML Link 3". But it may also travel from "XHTML Link 1" to "XHTML Link 2". Focus traversal does not relate to the order of focusable elements in the source documents. Instead, focus traversal relates to the rendered location of neighboring focusable elements.
This model is a combination of the two previous models. Focus can travel freely in any direction and focusable child elements may be flattened into the focus traversal path of the parent. A child with flattened elements does not get focused as a whole. It does therefore not need to be activated by the user.
The illustration above only shows one of many ways focus may travel through a Compound Document. Here, focus travels from "XHTML Link 1" down to "XHTML Link 3" and further down to "SVG Link 1". Child element activation is not required. Another movement down will move the focus directly to "SVG Link 3". The user can now move right to "SVG Link 4" and then down again, to "XHTML Link 6" and "XHTML Link 8".
(This section is informative)
The Current Focus Point Algorithm can be used to implement two dimensional focus traversal. It allows for natural traversal over randomly arranged focusable elements, using a multidirection input device (i.e., joystick).
The following illustration shows a complex WICD document, with twenty-five focusable elements of different shape and size.
Current Focus Points are not shown to the user. They mark invisible coordinates on visited, focusable elements. These coordinates represent entry points, where traversal from a previous focusable element to the current focusable element has taken place. The following illustration shows a cutout of the above example. It shows the otherwise invisible Focus Points (1,2,3), as they are created, when a user navigates over focusable elements C -> D -> E.
When the user navigates to the right from element 'D', the Current Focus Point Algorithm calculates the next visible, focusable element to the right of the current Focus Point ('2', which was attached to element 'D' on focus entry from element 'C'). Element 'E' is found as a result and a Focus Point ('3') is attached to it. Element 'E' will now gain focus from element 'D'.
The following illustration highlights another cutout from the original example.
This cutout shows how focus travels along the following elements: K -> L -> K -> M -> L -> M -> N -> L -> N -> O. Ten Focus Points are created during this process. (Actually, Focus Points 1,2,3 are created on the same horizontal axis. The same is true for 4,5,6 and 7,8,9,10.)
One important characteristic of the Current Focus Point Algorithm is shown above: when leaving element 'L' going down, the focus always travels back to the element ('K','M' or 'N') from which element 'L' was before entered.
The Current Focus Point is always used as a starting point for the 6.2.2.1 Distance Function calculation towards neighboring focusable elements. The Current Focus Point Algorithm consists of three phases:
Phase 1: All focusable elements are searched from the direction of the navigation. The search includes content that is currently visible in that direction and content that becomes visible if the viewport changes. Focusable elements are searched from the direction of navigation. The search includes content that is currently visible in that direction and content that becomes visible if the viewport changes.
Phase 2: A new location for the current focus point is calculated based on the Euclidian distance between the current focus point and each focusable element, direction of navigation, etc. The current focus point is moved in the direction of navigation. This movement may keep the point within the current focusable element or it may move it out of the current focusable element. Then, the current focus point movement is adjusted by the 6.2.2.1 Distance Function.
The distance function takes the location of the current focus point and the locations and shapes of available focusable content in the area. It then calculates the most suitable location for the point movement. The distance function enables the selection of close focusable elements in cases where a more unintuitive selection would otherwise be made.
Phase 3: If the focus point moves to another element, focused element is changed accordingly.
The distance function takes into account the following metrics:
The Euclidian distance (dotDist) between the current focus point position and its potential position in each of the candidates determined in phase 1. If the two positions have the same coordinate on the axis orthogonal to the navigation direction, dotDist is forced to 0 in order to favor elements in direction of navigation.
The absolute distance (dx or dy) on the navigation axis between the opposing edges of the currently focused element and each of candidates determined in phase 1.
The absolute distance (xdisplacement or ydisplacement) on the axis orthogonal to the navigation axis between the opposing edges of currently focused element and each of candidates determined in phase 1. When dx (dy) != 0, xdisplacement (ydisplacement) = 0. These values are used to compensate for the situations where an element is close on the navigation axis, but very far on the orthogonal axis. In such a case, it is more natural to navigate to another element, which may be further away on the navigation axis, but approximately on the same level on the other axis.
The overlap (Overlap) between the opposing edges of currently focused element and each of candidates determined in phase 1. Elements are rewarded for having high overlap with the currently focused element. To prevent the longer boxes from always winning the focus over shorter boxes when longer boxes are partially outside of viewport, the visible width has been set as an upper limit for the overlap.
The distance function (df) is:
df = dotDist + dx + dy + 2 * (xdisplacement + ydisplacement) - sqrt(Overlap)
An example of focus event triggered animations is the implementation of scalable buttons which render their own visual feedback. Such buttons are allowed to contain animation, but no interaction. They will provide a scalable alternative to the use of images as the source of links that can be traversed.
Focus events are enabled for each child content by setting the "focusanimation" object param element.
<object data="focus-button.svg" type="image/svg+xml"> <param name="focusanimation" value="onfocusevent" /> </object>
With the "focusanimation" parameter set to "onfocusevent",
the child content must be rendered as a static image, using the SVG 'snapshotTime' attribute (as described under 3.2.1.1 Still-Image Rendering).
If the child content does not have focus, it behaves like a static image.
Upon receiving focus, the root element shall be resumed.
Upon losing focus, all focusout animations of the child content are allowed to finish. By focusout animation, we mean all animations, that were triggered by a focusout event and all the animation elements they trigger in their turn. The focusout event has finished its active duration, when the last animation has finished its active duration. Then the root element is paused and its rendering becomes static.
The default "focusanimation" mode is "none".
The following SVG example applies to declarative animation:
<svg id="SVGRoot">
...
<rect ... >
<animate begin="SVGRoot.focusin" ... />
<animate begin="SVGRoot.focusout" ... />
</rect>
...
</svg>
The following XHTML code makes use of focus events in order to implement SVG child document rendered focus animations on multiple anchor elements. The user agents default focus outline is disabled using CSS.
<style type="text/css">
a.svglink:focus { outline: none }
</style>
<object type="image/svg+xml" data="header.svg" /> <!-- defaults to 'play' -->
<a href="foo1.html" class="svglink">
<object type="image/svg+xml" data="foo1.svg">
<param name="focusanimation" value="onfocusevent" />
</object>
</a>
<a href="foo2.html" class="svglink">
<object type="image/svg+xml" data="foo2.svg">
<param name="focusanimation" value="onfocusevent" />
</object>
</a>
Authors should take note of the following:
The 'focusin'-animation does not timeout and may loop any number of times.
The 'focusout'-animation should be limited to one second.
The 'focusout'-animation must not loop.
Standalone components or renderers, such as SVG engines, do not always provide a default system font.
In the context of WICD Core, however, user agents must at least provide one default system font (including a missing glyph, AKA 'Replacement Character', Unicode notation U+FFFD) to all components, such as browsers, SVG engines and other renderers. If there isn't enough information in the font to display a particular character, then the missing glyph is used.
Whatever I18N support a WICD implementation provides should not be worse than that of the platform on which it is running.
WICD Core specification cannot mandate any particular font, nor a specific font technology. But it mandates the availability of at least one default font, available to all renderers. This allows content providers to print text in any component (or renderer), as simply as in XHTML.
The default system font(s) may be raster or vector based. Ideally, the same default system font(s) are made available for all components.
The following SVG sample markup must generate visible text:
<svg xmlns="http://www.w3.org/2000/svg"
viewBox="0 0 250 50"
baseProfile="tiny" version="1.2">
<text x="20" y="20" font-size="30" fill="#000">Fahrvergnuegen</text>
</svg>
In both XHTML (using CSS) and SVG, font selection is done by the font-family property as described in CSS [Cascading Style Sheets, level 2 revision 1 CSS 2.1 Specification].
In desktop usage, authors frequently choose fonts that they know are installed by default on particular platforms.
On mobile:
there are typically fewer fonts available, perhaps only one
the fonts are unlikely to have the same names as desktop platforms
Conforming WICD Core 1.0 content should specify serif, sans-serif, or monospaced (three of the 'generic font families') as the last item in the list of font family names.
In SVG, named fonts, or subsets of fonts, can be supplied along with the content. This ensures that the desired look and feel is preserved regardless of the fonts available on a particular platform.
Content (XHTML, SVG, CSS, script, etc) may be compressed with gzip [IETF RFC 1952] or deflate [IETF RFC 1951]. Conforming WICD viewers must correctly support gzip-encoded and deflate-encoded content.
If they support HTTP/1.1, they must support these encodings according to the HTTP/1.1 specification [IETF RFC 2616]; in particular, the client must specify with an "Accept-Encoding:" request header (section 14.4 of [IETF RFC 2616]) which of the encodings it accepts, including at a minimum gzip and deflate, and then decompress any gzip-encoded and deflate-encoded data streams.
If the content is compressed with gzip or deflate, conforming WICD aware servers must indicate this with the "Content-Encoding: gzip" or "Content-Encoding: deflate" headers, as appropriate.
WICD documents may have various animating objects like SVG images, videos, audio streams, and animating images. Therefore, there is a need to define how the various media elements are synchronised when presented on a screen or audio device.
Document formats conforming to WICD Core must use the Timing and Synchronization model defined in the SMIL specification.
The document begin for WICD documents is when the load event is dispatched on the root document.
The document end for WICD documents is when the unload event is dispatched on the root document.
The elements which support timing are all those that reference timed media. In the case of an XHTML root document, the 'object' element supports timing.
Unless defined otherwise, the root document executes all timed children in parallel, following the semantics of the SMIL 'par' element. In other words, the root document of WICD has an implicit value for the SMIL 'timeContainer' attribute of 'par'.
Other profiles of WICD may allow the 'timeContainer' attribute.
Using a param element with name="timeline", the document author can specify whether the timeline on Scalable Child Content is started. This is useful for conserving system resources when multiple Scalable Children are used, and only animate in certain situations. Using scripting, the animations on individual children can be started and stopped by changing the value attribute.
A param element with name="timeline" and value="disable" shall prevent the timeline of the Scalable Child Content from starting or, if already started, shall stop it. Thus, animations will not play.
A param element with name="timeline" and value="enable" shall allow the timeline of the Scalable Child Content to start. Thus, for dynamic rendering, animations will play. If previously stopped, the timeline shall reset and re-start.
If there is no param element with name="timeline", the timeline of the Scalable Child Content shall start. Thus, for dynamic rendering, animations will play.
Only dynamic renderings can have their timeline started and stopped. Frozen and static renderings have no timeline and thus cannot be started and stopped.
A param element with name="render" and value="frozen" or value="static" shall result in a rendering which is not dynamic and thus, animations shall not play even if a param element with name="timeline" has a value="enable".
The behavior of playing animations while loading a document is dependent on the capabilities of the root namespace of the document.
XML documents may use a parse first and then process model where the entire DOM is built and then handed to the user agent for processing, or may use a parse and process in parallel model where the document is processed immediately by the user agent.
When loading more than one animation during document load, synchronization of animations may be desirable. However XHTML has no inherent capability of providing this synchronization and XHTML eventing cannot guarantee synchronization of animations while the document is loading.
SVG and SVG Tiny do have synchronization capabilities that can be used when these namespaces are the root of a child document. The timeline for synchronization occurs when the first child document capable of synchronization begins. For example, an XHTML document has a referenced child SVG Tiny document whose timeline begins when the user agent begins processing the referenced child document which may animate a progress load bar while the rest of the composite document loads.
Conforming WICD user agents must implement Media Queries [Media Queries].
Due to the wide range of devices that may support WICD, it is crucial for content authors to be able to provide CSS that fits best for each device that the content authors target. For instance, if the content authors want to deliver WICD content for devices that have different screen aspect ratio, [Media Queries] allows different style sheets to be applied to allow scalable content to be fitted based on the devices' aspect ratio, e.g. depending on the orientation of the screen, the content can be authored in a way that scalable content fits 100% vertically or horizontally.
A user agent that discovers a CSS style sheet, provided for its own device class (either by media attribute - for instance set to "handheld" - or by a Media Query expression), should assume the content was created with specific properties "in mind". The agent is then expected to deactivate any custom adaptation techniques (for example rendering wide screen content on a narrow screen) and display the intended layout "as is".
(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 style sheet reference for the "handheld" media type, do not require such treatment. Such documents should be rendered as is.
The terms used in this document are specified in Compound Document by Reference Framework 1.0.
The param attribute with the name "render" and the values "dynamic", "frozen" and "static" are specified in 3.2.1 Scalable Foreground Child Content.
The param attribute with the name "focusable" and the values "hierarchical", "flat" and "skip" are specified in 6 Focus Handling.
The param attribute with the name "focusanimation" and the values "none" and "onfocusevent" are specified in 6.3 Focus Event triggered Child Content Animations.
The param attribute with the name "timeline" and the values "enable" and "disable" are specified in 9.2 Timeline Initialization.
This specification defines conformance for several classes of products:
Profiles
User agents
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 [IETF RFC 2119]. However, for readability, these words do not appear in all uppercase letters in this specification.
All sections are normative unless they are marked with "(This section is Informative)".
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.
Profile Conformance
Any profile, conforming to WICD Core 1.0, must support XHTML as root document.
Any profile, conforming to WICD Core 1.0, must support the XHTML <object> element as means to reference Scalable Child Content.
Any profile, conforming to WICD Core 1.0, must support SVG documents as Scalable Child Content format.
User Agent Conformance
Multiple SVG child documents may be referenced from the same XHTML document.
Multiple SVG child documents may animate in parallel.
Any Scalable Child Content format must support these three use cases: Scalable Foreground Child Content, Scalable Background Image and Scalable Overlay Objects (Sprites).
Scalable Foreground Child Content is referenced using the XHTML <object> element. It appears on the main XHTML layer, just like raster images.
User agents must support multiple Scalable Foreground Children, which may be animating, interactive and may have embedded links.
An <object> element <param> child element with name="render" and value="dynamic" shall result in a dynamic rendering. Links shall be activatable. Animations shall play, if the timeline has started. Modifications made by script shall update the rendering. If the rendering area changes size, the rendering shall update.
An <object> element <param> child element with name="render" and value="static" static rendering. Links shall be activatable. Animations shall not play. Modifications made by script shall update the rendering. The rendering shall also update, if the size of the rendering area changes.
An <object> element <param> child element with name="render" and value="frozen" shall result in a one-time static rendering to a raster image. Links shall not be activatable. Animations shall not play. Modifications made by script shall not update the rendering. The rendering shall also not update, if the size of the rendering area changes. The original SVG, once rendered, may be discarded by the client.
The default value for <param name="render"> is "dynamic".
For SVG child objects, the document time used for rendering a frozen or static image shall be that given by the SVG 'snapshotTime' attribute. If no 'snapshotTime' is present in the animation, a document time of zero (0) must be used. Other Scalable Child Content formats may use a similar mechanism. Scalable Child Content lacking such capability should use a time of zero (0) for still-image rendering.
User agents must support Scalable Child Content (e.g. SVG) to be used as CSS background images.
If background.svg has width and height in px, then this is well-defined. If it is the default (width="100%" height="100%") then it will display, as large as will fit, where the background area to cover is seen as a viewport.
WICD user agents must support content layering using CSS absolute positioning in x, y and z order. This will detach a child element from main XHTML layer and create a new transparent layer.
WICD user agents must make all visible and focusable points in the XHTML layer and the positioned Overlay Object reachable and activatable.
WICD user agents must support transparency for Overlay Objects.
Scalable Overlay Elements, referred to from the XHTML page, may be put in front of, or behind, the default XHTML layer.
Any transparent areas in the Overlay Object and in XHTML root documents must make the layer behind visible.
User agents must support interactivity in overlay elements.
User agents must support overlay images with embedded links.
If only one size attribute value is provided, when referencing Scalable Child Content, a fixed aspect ratio child element will get 'rightsized' proportionally, by being scaled to fit into the destination box.
When rendering scalable, but fixed aspect-ratio content into a fixed-sized destination box, the child content must render the entire viewport, including any leftover margins.
In the absence of a background color or image on the element that established the viewport (abbr html:object or svg:svg) its background is transparent. This is in order to maximize the visual quality of content the parent document should be visible through the leftovers (as well as through the child content itself where it is transparent).
A defined background applies to the entire viewport (including the leftovers) so that content that spills outside of the viewbox into the leftovers is still on the correct background.
Any UI event, such as a mouse click, that hits on the leftover areas, is dispatched in the same manner as UI events over non-leftover areas (i.e., to the child document)
When rendering any content over non-animated content, transparency must be supported. Otherwise transparency should be supported.
The viewer must support JPEG/JFIF [Scalable Vector Graphics (SVG) Tiny 1.2 Specification], PNG [Portable Network Graphics (PNG) Specification (Second Edition)] and GIF 89a (non-interlaced, non-transparent, non-animated) raster image formats. Other image formats may be supported in addition. 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.
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 a width and height of zero.
Any audio format supported by the device must also be supported for use with the <audio> element in SVG and <object> element in XHTML.
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).
Any video format supported by the device must also be supported for use with the <video> element in SVG and <object> element in XHTML.
WICD compliant agents should support seamless hyperlinking originating from any of the supported document formats to all supported content types. If it is possible to link from XHTML to some other supported content type (for example: XHTML linking to RSS, Java or multimedia content), then it should also be possible to link to the same content types from any other supported document format which supports hyperlinking (for example: SVG linking to RSS, Java or multimedia content).
If linking from XHTML to any of the supported content types will result in content type specific treatment, then linking to that same format from any other supported document format (such as from SVG) should result in the same content type specific treatment. If a WICD compliant agent supports linking from XHTML to URI schemes other than http:// (for examples wtai://, tel://, mailto://, etc.), then these URI schemes should also be supported, when linked-to from any of the other supported document formats that support hyperlinking (such as from SVG).
All URI schemes, supported for hyperlinking and the related functionality, should be supported, independent of the originating document format.
When linking from XHTML to SVG, as well as from SVG to XHTML the user agent should stay the same.
WICD compliant user agents must provide the ability for users with a keyboard or joystick input device (and without a pointing device), to navigate to any focusable element in the root document and all of its descendants.
The language specifications that are used with this framework define what elements are focusable. For example, focusable items in an SVG document are defined by the SVG 1.2 focusable attribute [SVGMobile12, Element focus].
In XHTML, <object> elements are, by default, focusable and participate in the focus traversal. However, conforming WICD user agents must remove child content from the focus traversal, if the <object> element's child <param> element is set to the attribute name="focusable" and the attribute value="skip".
By using the <object> element's child <param> element with the attribute name="focusable", the author of the parent document can specify whether "flat" or "hierarchical" focusability is desired for a child.
If more than one "focusable" parameter is provided for an element, then only the last one shall be used. Unrecognized param values shall be ignored.
The default focus mode is "hierarchical".
Authors use <param name="focusable" value="flat" />, to make focusable elements of the child become direct participants of the parents focus traversal. Access keys, defined by child documents, will not become accessible to the user, if they are also defined by the parent or by some other child element.
Authors use <param name="focusable" value="hierarchical" /> to select hierarchical (activatable) focus handling for a referenced child. A user, navigating to such a child element, will have the option to activate it, or to move on, to the next focusable element. Activating the child, will provide the user with access to the child's interactivity, its focusable elements, such as embedded links and its access keys. The user must deactivate an activated child element, in order to gain access to the parents focus traversal again.
Focus events are enabled for each child content by setting the "focusanimation" object element parameter.
With the "focusanimation" parameter set to "onfocusevent", the child content must be rendered as a static image, using the SVG 'snapshotTime' attribute (as described under 3.2.1.1 Still-Image Rendering).
If the child content does not have focus, it behaves like a static image.
Upon receiving focus, the root element shall be resumed.
Upon losing focus, all focusout animations of the child content are allowed to finish. By focusout animation, we mean all animations, that were triggered by a focusout event and all the animation elements they trigger in their turn. The focusout event has finished its active duration, when the last animation has finished its active duration. Then the root element is paused and it's rendering becomes static.
The default "focusanimation" mode is "none".
In the context of WICD Core, user agents must at least provide one default system font (including a missing glyph, AKA 'Replacement Character', Unicode notation U+FFFD) to all components, such as browsers, SVG engines and other renderers. If there isn't enough information in the font to display a particular character, then the missing glyph is used.
Whatever I18N support a WICD implementation provides should not be worse than that of the platform on which it is running.
The following SVG sample markup must generate visible text: <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 250 50" baseProfile="tiny" version="1.2"> <text x="20" y="20" font-size="30" fill="#000">Fahrvergnuegen</text> </svg>
In both XHTML (using CSS) and SVG, font selection is done by the font-family property as described in CSS [Cascading Style Sheets, level 2 revision 1 CSS 2.1 Specification].
Conforming WICD Core 1.0 content should specify serif, sans-serif, or monospaced (three of the 'generic font families') as the last item in the list of font family names.
Content (XHTML, SVG, CSS, script, etc) may be compressed with gzip [IETF RFC 1952] or deflate [IETF RFC 1951]. Conforming WICD viewers must correctly support gzip-encoded and deflate-encoded content.
If they support HTTP/1.1, they must support these encodings according to the HTTP/1.1 specification [IETF RFC 2616]; in particular, the client must specify with an "Accept-Encoding:" request header (section 14.4 of [IETF RFC 2616]) with those encodings that it accepts, including at minimum gzip and deflate, and then decompress any gzip-encoded and deflate-encoded data streams.
If the content is compressed with gzip or deflate, conforming WICD aware servers must indicate this with the "Content-Encoding: gzip" or "Content-Encoding: deflate" headers, as appropriate.
Document formats conforming to WICD Core must use the Timing and Synchronization model defined in the SMIL specification.
The document begin for WICD documents is when the complete host document has been loaded by the user agent.
The document end for WICD documents is when the associated application exits or switches context to another document.
The elements which support timing are all those that reference timed media. In the case of an XHTML root document, the 'object' element supports timing.
Unless defined otherwise, the root document executes all timed children in parallel, following the semantics of the SMIL 'par' element. In other words, the root document of WICD has an implicit value for the SMIL 'timeContainer' attribute of 'par'.
An <object> element param element with name="timeline" and value="disable" shall prevent the timeline of the Scalable Child Content from starting or, if already started, shall stop it. Thus, animations will not play.
An <object> element param element with name="timeline" and value="enable" shall allow the timeline of the Scalable Child Content to start. Thus, for dynamic rendering, animations will play. If previously stopped, the timeline shall reset and re-start.
If there is no param element with name="timeline", the timeline of the Scalable Child Content shall start. Thus, for dynamic rendering, animations will play.
A param element with name="render" and value="frozen" or value="static" shall result in a rendering which is not dynamic and thus, animations shall not play even if a param element with name="timeline" has a value="enable".
Conforming WICD user agents must implement Media Queries [Media Queries].
A user agent that discovers a CSS style sheet, provided for its own device class (either by media attribute - for instance set to "handheld" - or by a Media Query expression), should assume the content was created with specific properties "in mind". The agent is then expected to deactivate any custom adaptation techniques (for example rendering wide screen content on a narrow screen) and display the intended layout "as is".
The editors would like to thank the contributors:
Ola Andersson, Ikivo
Daniel Appelquist, Vodafone
Mark Baker, Research in Motion, Limited, (formerly) Justsystem
L. David Baron, The Mozilla Foundation
Robin Berjon, Expway
Kurt Cagle, Mercurial Communications Inc.
Cyril Concolato, Groupe des Écoles des Télécommunications (GET)
Erik Dahlström, Opera Software
Alex Danilo, W3C Invited Experts
Jean-Claude Dufourd, Streamezzo
Andrew Emmons, Bitflash Division of Open Text
Hae Seok Lee, Infraware
Torkel Hambraeus, Ikivo
Vincent Hardy (Previous Working Group Chair), Sun Microsystems, Inc.
Takanari Hayama, Vodafone
Scott Hayman, Research In Motion Limited
Ian Hickson, (formerly) Opera Software
Masayasu Ishikawa, (Working Group Team Contact) W3C
Dean Jackson (previous Working Group Team Contact), W3C
Kevin Kelly (Working Group Chair), IBM
Anne van Kesteren, Opera Software
Rhys Lewis, Volantis
Chris Lilley, W3C
Lars-Gunnar Lundgren, Obigo
Vincent Mahe, France Telecom
Charles McCathieNevile, Opera Software
Timur Mehrvarz, Vodafone
Kunio Ohno, Justsystems Corporation
Lasse Pajunen, Nokia
Lars Piepel, Vodafone
Antoine Quint, Fuchsia Design
Julien Quint, DAISY Consortium
Nandini Ramani, Sun Microsystems, Inc.
Seung Chul Yeh, Infraware
Svante Schubert, Sun Microsystems, Inc.
Bradley Sipes, Ikivo
Steve Speicher, IBM
Peter Stark, Sony Ericsson
Petri Vuorimaa, Helsinki University of Technology
Daniel Zucker, ACCESS Co., Ltd.
Prepeared CR state. (TM)
Fixed document-internal linking. (Converted from "[reference to "xxx" removed since]" to "specref ref="rightsizing-inf"") (TM)
Updated the link to CSS21 "Visual formatting model" under 3.3.1 Rightsizing to point to newly modified section "Inline, replaced elements". (TM)
Moved text about 3.3.1.1 Rightsizing Behavior into a new *Informative* section. (TM)
Updated status of the document to CR. (TM)
Outcommented changelog entries before 22. December 2006. (TM)
Split D References into Normative and Informative. (TM)
Using author list, sorted by last name. (TM)
Fixed typos. (JQ)
Removed expansion of abbreviation CDRF in description of WICD Mobile. (JQ)
Updated wording for render with value="frozen" in 3.2.1.1 Still-Image Rendering. (JQ)
Updated wording for "snapshotTime" in 3.2 Scalable Child Content Use Cases. (JQ)
Changed "render/static" to "name='render' value='frozen'" in 3.2 Scalable Child Content Use Cases. (JQ)
Changed sample caption to "rightsizing example" and fixed typos in 3.3.1 Rightsizing. (JQ)
Changed "the parent document should be visible through the leftovers..." to "must be visible." in 3.3.2 Leftover Margins. (JQ)
Removed "If animation were supported in XHTML, then it would also be a requirement that the plugin is notified every time a change occurs in the rendered output. Such a change would most likely require an off-screen buffer to be used in order to 'double-buffer' so as to avoid flicker." from 3.3.3.1 Introduction. (JQ)
Changed 3.3.3.2 Transparency requirements to "transparency must be supported." (JQ)
Added caption (in real text) to figure in 6.1.1 Hierarchical Child Focus. (JQ)
Changed "The default focus mode is 'hierarchical'" to "The default focus mode depends on the User Agent. If a specific behavior is desired the content author must specify which focus mode to use." in 6.1 Focus Modes. (JQ)
Added "All sections are normative unless they are marked with '(This section is Informative)'" in C Conformance. (JQ)
Updated text on load event in 9.1 Temporal Synchronization of Media and changed "switched contents" to unload event. (JQ)
Modified text on "time zero(0)" and "snapshotTime" under 6.3 Focus Event triggered Child Content Animations based on Eric Dahlström's comments (TM).
Modified text on "focusout events" under 6.3 Focus Event triggered Child Content Animations based on Eric Dahlström's comments (TM).
Changed the order of sub-sections under "6 Focus Handling", by swapping 6.2 and 6.3 (TM).
Removed outcommented text (TM).
Marked focusin/focusout conventions as authors guides under 6.3 Focus Event triggered Child Content Animations based on Eric Dahlström's comments (TM).
Modified text on "losing focus" under 6.3 Focus Event triggered Child Content Animations based on Eric Dahlström's finding (TM).
Modified text on "non interactive elements made focusable" under 6 Focus Handling (TM)
Modified text and removed informative statement under 6.2 Focus Navigation based on Steve's wording (TM)
Added normative statement under 6.2 Focus Navigation based on Steve's wording (TM)
Modified definition of param "render/static" and param "render/frozen" under 3.2.1.1 Still-Image Rendering based on Chris's wording (TM)