WICD Mobile 1.0

A Definitions

The terms used in this document are specified in Compound Document by Reference Framework 1.0.

B Conformance

Everything in this specification is normative except for diagrams, examples, notes and sections marked informative.

This specification defines conformance for several classes of products:

• User Agent

• Content

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 "This specification recommends ...", or some similar wording.

WICD Mobile 1.0 User Agent Conformance:

1. Conformant WICD Mobile 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.

2. Conformant WICD Mobile 1.0 user agents must implement "WICD Core 1.0".

3. Conformant WICD Mobile 1.0 user agents must support XHTML Basic 1.1 as the root document.

4. Conformant WICD Mobile 1.0 user agents must support ECMAScript 3rd Edition Compact Profile (ES-CP) as a scripting language.

5. Conformant WICD Mobile 1.0 user agents must support CSS Mobile Profile 2.0 as well as the additional specified CSS properties.

6. Conformant WICD Mobile 1.0 user agents must support Scalable Vector Graphics (SVG) Tiny 1.2 specification while referenced from XHTML.

7. When declaring support for WICD Mobile 1.0, a conforming user agent should use an "Accept" header with the value: application/xhtml+xml; profile="http://www.w3.org/2007/wicd-mobile".

8. Future versions of the WICD Mobile profile, which are compatible with WICD Mobile 1.0, must use the same profile string, using the same format, but with a later date.

9. Conformant WICD Mobile 1.0 user agents must support the Document Object Model (DOM) Level 3 Core Specification subset defined in the SVG Tiny 1.2 specification [http://www.w3.org/TR/SVGMobile12/svgudom.html#dom] for all namespaces.

10. Conformant WICD Mobile 1.0 user agents must support the features described in Appendix C Document Object Model (DOM) Level 3 Core Subset Extensions for all namespaces.

11. Conformant WICD Mobile 1.0 user agents must support the Document Object Model (DOM) Level 3 Events Specification Subset defined in the SVG Tiny 1.2 Specification [http://www.w3.org/TR/SVGMobile12/svgudom.html#events] for all namespaces.

12. Conformant WICD Mobile 1.0 user agents must support the features described in Appendix D Document Object Model (DOM) Level 3 Events Extensions for all namespaces.

13. Conformant WICD Mobile 1.0 user agents must support the HTML DOM features described in Appendix E Document Object Model (DOM) Level 2 HTML Subset for the nodes in the XHTML namespace.

14. Conformant WICD Mobile 1.0 user agents must support the SVG Micro DOM (uDOM) specification for nodes in the SVG namespace.

15. Conformant WICD Mobile 1.0 user agents must support the ElementTraversal interface on all DOM objects which implement the org.w3c.dom.Element interface.

16. Conformant WICD Mobile 1.0 user agents must support the DocumentView interface on all implementations of the org.w3c.dom.Document interface.

17. Conformant WICD Mobile 1.0 user agents must support the Window Object 1.0 specification on all implementations of the org.w3.dom.AbstractView interface.

18. Conformant WICD Mobile 1.0 user agents must support the mapping from XHTML event attributes to the corresponding DOM3 events.

19. Conformant WICD Mobile 1.0 user agents must support the SVG Event to DOM Event Mapping.

20. Conformant WICD Mobile 1.0 user agents must support the XMLHttpRequest Object.

21. Conformant WICD Mobile 1.0 user agents, for devices that have a multi directional (2D) joystick input device, must implement the "Two Dimensional Focus Navigation Model" with support for "Flattened Children". For guidance see Navigation Models in WICD Core 1.0.

22. In a static situation, focus should go back, all the way, to where it came from, when a user navigates focus in backward direction.

23. Conformant WICD Mobile 1.0 user agents should allow activation of hierarchical child elements using the "Ok" key.

24. Conformant WICD Mobile 1.0 user agents, implemented on devices, that have at least two soft keys and no dedicated escape key, should allow deactivation of hierarchical child elements, using longpress Soft2.

25. Conformant WICD Mobile 1.0 user agents should support Multipart/related packaging. These agents will advertise "multipart/related" capability with their HTTP request accept headers.

26. Internet Media Type implementations must in general treat unrecognized subtypes of "multipart" as being equivalent to Multipart/mixed. Agents supporting a WICD Profile are therefore expected to support both, related and mixed.

27. Conformant WICD Mobile 1.0 user agents must support DOM Level 3 event flow (capture and bubble) for all namespaces, including SVG Tiny 1.2.

WICD Mobile 1.0 Document Conformance:

1. XHTML Basic 1.1 documents should be associated with the application/xhtml+xml mime type.

2. ECMAScript documents should be associated with the "application/ecmascript" mime type.

3. In conforming WICD 1.0 content, audio referenced from an XHTML object element must have a width and height of zero.

C Document Object Model (DOM) Level 3 Core Subset Extensions

NodeList

The org.w3c.dom.NodeList interface, defined in the DOM Core Level 3 Specification must be supported for the HTMLDocument.getElementsByTagName() method.

interface NodeList {
  Node     item(in unsigned long index);
  readonly attribute unsigned long   length;
};

getAttribute and setAttribute methods on Element

The SVG Working Group has resolved that the getAttribute and setAttribute methods were missing from the SVG Tiny 1.2 CR specification uDOM DOM Level 3 Core subset by error. Therefore, the next revision of the SVG Tiny 1.2 specification will include the getAttribute and setAttribute methods on the org.w3c.dom.Element interface.

adoptNode

http://www.w3.org/TR/DOM-Level-3-Core/core.html#Document3-adoptNode

Conformant WICD Mobile 1.0 user agents must support the adoptNode method on the Document interface, as defined in the DOM Core Level 3 specification.

D Document Object Model (DOM) Level 3 Events Extensions

The CustomEvent type allows applications to use application-domain events. The support for dispatchEvent on EventTarget (in addition to what is supported in the SVG Tiny 1.2 uDOM), provides a way to dispatch the event to the document tree. Finally, support for DocumentEvent provides a way to create CustomEvent instances which can then be dispatched.

CustomEvent

http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-CustomEvent

// Introduced in DOM Level 3:
interface CustomEvent : Event {
  readonly attribute DOMObject detail;
  void     initCustomEventNS(in DOMString namespaceURI, 
                             in DOMString typeArg, 
                             in boolean canBubbleArg, 
                             in boolean cancelableArg, 
                             in DOMObject detailArg);
};

EventTarget

http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-EventTarget

// Introduced in DOM Level 2:
interface EventTarget {
  void    addEventListener(in DOMString type, 
                           in EventListener listener, 
                           in boolean useCapture);

  void    removeEventListener(in DOMString type, 
                              in EventListener listener, 
                              in boolean useCapture);

  // Modified in DOM Level 3:
  boolean dispatchEvent(in Event evt) raises(EventException, DOMException);

  // Introduced in DOM Level 3:
  void    addEventListenerNS(in DOMString namespaceURI,   
                             in DOMString type, 
                             in EventListener listener, 
                             in boolean useCapture, 
                             in DOMObject evtGroup);

  // Introduced in DOM Level 3:
  void    removeEventListenerNS(in DOMString namespaceURI, 
                                in DOMString type, 
                                in EventListener listener, 
                                in boolean useCapture);
};

DocumentEvent

http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-DocumentEvent

Conformant WICD Mobile Profile User Agent must support the following subset of the DocumentEvent interface. Note that in a conformant WICD Mobile Profile User Agent, "CustomEvent" is the only required event type.

// Introduced in DOM Level 2:
interface DocumentEvent {
  Event   createEvent(in DOMString eventType)  raises(DOMException);
};

createEvent

Parameters

eventType of type DOMString

The eventType parameter specifies the name of the DOM Events interface to be supported by the created event object, i.e. "CustomEvent". The CustomEvent init method must be called after creation in order to initialize the Event's values. A user wishing to synthesize some kind of CustomEvent would invoke DocumentEvent.createEvent("CustomEvent"). The CustomEvent.initCustomEventNS method could then be called on the newly created CustomEvent object to set the details of the event to be dispatched.

Return Value

Event

The newly created event object.

Exceptions

DOMException NOT_SUPPORTED_ERR: Raised if the implementation does not support the Event interface requested. In WICD Mobile 1.0, only the CustomEvent interface is required.

E Document Object Model (DOM) Level 2 HTML Subset

The normative definition of the Document Object Model (DOM) Level 2 HTML is defined here.

// File: html2.idl
#ifndef _HTML2_IDL_
#define _HTML2_IDL_

#include "dom.idl"

#pragma prefix "dom.w3c.org"

module html2
{
  typedef dom::DOMString DOMString;
  typedef dom::Document Document;
  typedef dom::NodeList NodeList;
  typedef dom::Element Element;

  interface HTMLElement;
  interface HTMLFormElement;

  interface HTMLDocument : Document {
    NodeList             getElementsByName(in DOMString elementName);
  };

  interface HTMLElement : Element {
    attribute DOMString  id;
    attribute DOMString  className;
  };

  interface HTMLFormElement : HTMLElement {
    void                 submit();
    void                 reset();
  };

  interface HTMLInputElement : HTMLElement {
    attribute boolean    checked;
    attribute DOMString  value;
    void                 select();
  };

  interface HTMLTextAreaElement : HTMLElement {
    attribute DOMString  value;
    void                 select();
  };

  interface HTMLObjectElement : HTMLElement {
    // Introduced in DOM Level 2:
    readonly attribute Document  contentDocument;
  };

  interface HTMLOptionElement : HTMLElement {
    attribute boolean selected;
  }
 
};

#endif // _HTML2_IDL_

F References

G Authoring Guidelines (Non-Normative)

The WICD Mobile specification allows authors to use XHTML, CSS, and SVG together in a predictable way. WICD Core defines basic principles that all comformant content and user agents must apply. Exact language versions and capabilities are defined in the WICD profiles. Content authors are encouraged to see the profiles for guaranteeing use of right feature set.

In addition to this specification, the Mobile Web Best Practices 1.0 document provides useful guidelines for delivering content to Web-enabled mobile devices. WICD Mobile is a superset of the capabilities articulated in the default delivery context section of this document.

H Acknowledgements (Non-Normative)

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.

I Changes Log (Non-Normative)

2007-07-16

• Added 3.6.12 Event Flow: Capture and Bubble to align with conformance section.(SS)

2007-07-01

• Prepeared CR state. (TM)

2007-04-27

• Fixed the link under 3.6.5 HTML DOM. (TM)

2007-04-20

• Added XHTML Basic 1.1 to status section as WICD Mobile dependency. (TM)

2007-04-17

• Inserted missing links. (TM)

2007-04-16

• Removed "WICD Full" from exit criteria in the status section. (TM)

• Outcommented changelog entries before 22. December 2006. (TM)

• Listing additional CSS attribute requirements 3.3 CSS Mobile Profile 2.0 (TM)

2007-04-05

• Removed the following text: "3.6.6 Focus Traversal - Conformant WICD Mobile 1.0 user agents must support the Focus Traversal features described in Appendix [***] for all namespaces." (TM)

• Added missing item in Conformance section: "Conformant WICD Mobile 1.0 user agents must support the SVG Event to DOM Event Mapping." (TM)

• Added missing item in Conformance section: "Conformant WICD Mobile 1.0 user agents must support the XMLHttpRequest Object." (TM)

• Added missing item in Conformance section: "Conformant WICD Mobile 1.0 user agents should support Multipart/related packaging. These agents will advertise "multipart/related" capability with their HTTP request accept headers." (TM)

• Added missing item in Conformance section: "Internet Media Type implementations must in general treat unrecognized subtypes of "multipart" as being equivalent to Multipart/mixed. Agents supporting a WICD Profile are therefore expected to support both, related and mixed." (TM)

2007-04-02

• Removed section "F Focus Traversal Support". (TM)

2007-03-31

• Split F References into Normative and Informative. (TM)

• Using author list, sorted by last name. (TM)

• Changed UA identification profile string from "/2005/12/" to "/2007/03/". (TM)

2007-03-15

• Fixed document validity. (JQ)

• Removed occurrence of "we recommend". (JQ)

• Replaced "MIME Type" with "Internet Media Type". (JQ)

• Replaced "Non-Normative" with "Informative" in the xmlspec stylesheet. (JQ)

• Added XmlHttpRequest Object dependency in the status. (JQ)

2007-03-14

• Fixed typos. (JQ)

• Updated abstract [missing links to be fixed.] (JQ)

• Added dummy links in 2 Compound Document by Reference Framework Compliance [to be fixed.] (JQ)

• Moved examples from 2 Compound Document by Reference Framework Compliance to 1 Introduction. (JQ)

• Changed should to must and mime type to Media Type in 3.2.1 ECMAScript Internet Media Type and added link to RFC 4329. (JQ)

• Added conformance criterion to support DOM Level 3 event flow in all namespaces. (JQ)

• Improved link consistency. (JQ)

• Commented out diff-marked version from status and linked to last call comments. (JQ)

2007-03-13

• Updated status of the document to CR. (JQ)

• Sorted contributors by last name instead of first. (JQ)

• Added "Everything in this specification is normative except for diagrams, examples, notes and sections marked informative" in the beginning of B Conformance. (JQ)

2007-03-12

• Changed 3.6.9 Window interface to simply require Window Object 1.0, and updated attached conformance criterion. (JQ)

• Removed "In addition to the Document interface attributes and methods defined in the SVG Tiny 1.2 uDOM specification" from the adoptNode description in C Document Object Model (DOM) Level 3 Core Subset Extensions. (JQ)

2007-01-25

• Added missing "HTMLOptionElement" fragment (3 lines) to 3.6.5 HTML DOM (TM)

2006-12-11

• Updated reference to "CSS Mobile Profile 2.0 Specification" [CSS Mobile Profile 2.0 Specification]. (JQ)