|
On this page, you will find specifications for i-mode compatible XHTML and instructions on how to create websites for i-mode. |
What’s XHTML ?
You can view your web site created using i-mode compatible XHTML from XHTML compatible FOMA i-mode handset models by simply uploading it to a web server accessible from the Internet.
Please note that NTT DOCOMO does not offer Web site development services.
0-9, # and * can be used as accesskeys for the "directkey functions."
Features of i-mode compatible XHTML
- i-mode compatible XHTML was developed to be compatible with i-mode compatible HTML based on the WAP Forum’s (now known as the OMA <Open Mobile Alliance>) XHTML-MP.
- Compatible with all main WAP 2.0 functions.
- Generally a dual browser with i-mode compatible HTML.
- Compatible with Shift-JIS and UTF-8 character encodings. GIF and JPEG images are supported.
- Scripting languages are not supported.
- Half-size kana characters can be used.
i-mode Compatible HTML & XHTML Correspondence Table
i-mode Compatible HTML & XHTML Correspondence Table (in Japanese only)
Points to Consider when Creating i-mode Compatible Content
This is an introduction to the specifications for i-mode compatible content, guidelines for creating content that is viewable by all i-mode compatible handset models, and other information. You need to be aware of this information because it forms the basis of creating i-mode content.
XHTML Specifications
i-mode compatible XHTML versions
i-mode compatible XHTML is classified into multiple categories. Depending on the tags to be used, the handset model may need to be identified prior to use.
User Agent
User agent is an HTTP header (HTTP_USER_AGENT) that can identify the model of an accessing i-mode handset. By obtaining the HTTP header through CGI on your Web server, you can determine the model of the accessing i-mode handset. You can use this function to offer content that is maximized for viewing by individual i-mode handset models.
References
- "HTML 4.01 Specification",W3C Recommendation 24 December 1999,D.Ragget,et al.,
URL:
(Page will open in a new window.)http://www.w3.org/TR/1999/REC-html401-19991224 - "Extensible Markup Language (XML) 1.0 (Second Edition)",W3C Recommendation 6 October 2000,T.Baray,et al.,
URL:
(Page will open in a new window.)http://www.w3.org/TR/2000/REC-xml-20001006 - "Modularization of XHTMLTM",W3C Recommendation 10 April 2001,M.Altheims,et al.,
URL:
(Page will open in a new window.)http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410 - "XHTMLTM Basic 1.0",W3C Recommendation 19 December 2000,M.Ishikawa,et al.,
URL:
(Page will open in a new window.)http://www.w3.org/TR/2000/REC-xhtml-basic-20001219 - "Cascading Style Sheets,level2",B.Bos,et al.,12 May1998,
URL:
(Page will open in a new window.)http://www.w3.org/TR/1998/REC-CSS2-19980512 - "XHTML Mobile Profile",WAP Forum,WAP-277-XHTMLMP-20011029-a,
URL:
(Page will open in a new window.)http://www.wapforum.org/what/technical.htm - "WAP CSS",WAP ForumTM,WAP-239-WCSS-20011026-a,
URL:
(Page will open in a new window.)http://www.wapforum.org/what/technical.htm - "XHTMLTM 1.1-Module-based XHTML",W3C Recommendation 31 May 2001,Murray Altheim,et al.,
URL:
(Page will open in a new window.)http://www.w3.org/TR/2001/REC-xhtml11-20010531/
Please be aware that the i-mode compatible pictograms specifications etc. given on this page may change without prior notice.
Corporate names and product names are trademarks or registered trademarks of their respective owners.
(Page will open in a new window.)![]()
In order to view PDF files, you must have the
(Page will open in a new window.)Adobe® ReaderTM plug-in offered free of charge from Adobe Systems, Inc.


