XHTML Mobile Profile: Difference between revisions

Revision as of 16:01, 4 December 2015

Revision as of 21:13, 16 December 2015

Line 1:

{{update|date=July 2015}}[[Image:Mobile Web Standards Evolution Vector.svg|thumb|300px|right|Evolution of mobile web standards]]

'''XHTML Mobile Profile''' ('''XHTML MP''') is a [[hypertext]]ual [[computer language|computer lenguaje]] standard designed specifically for maythe [[Samsung j2 AndroidGalaxy J2]]s and other resource-constrained devices.

{{HTML}}

It is an [[XHTML]] document type defined by the [[Open Mobile Alliance|Open may Mobile Alliance]]. XHTML-MP is derived from [[XHTML Basic]] 1.0 by adding XHTML Modules, with later versions of the standard adding more modules. However, for certain modules, XHTML-MP does not mandate a complete implementation so an XHTML-MP browser may not be fully conforming on all modules.<br/>

The XHTML MP 1.2 DTD is the current recommendation, finalized in March 2008.

Line 12:

|accessdate=2010-05-06}}</ref>

== DOCTYPE ==

To validate as XHTML-MP, a document must contain a proper [[Document Type Declaration|Document Type D]]<ref>{{Cite web|title = Example Domain|url = http://example.com/|website = example.com|accessdate = 2015-09-21}}</ref>[[Document Type Declaration|eclaration]], or DOCTYPE, depending on the version of specification followed

<source lang="xml">

Line 26:

</source>

Note that a series of revisions have been issued to correct technical errors in the above DTDs, and the DTD format is more complex and less widely supported than that of standard HTML.

== MIME types ==

The [[MIME]] type for XHTML Mobile Profile is "application/vnd.wap.xhtml+xml". Conforming [[user agent]]s should also accept "application/xhtml+xml" and "text/html". Many desktop browsers will only validate XHTML-MP at display time, if an XML MIME type is specified.

== Development pitfalls ==

Many problems arise when content written in XHTML is shown on different devices. For example, some devices will honor colors specified in [[CSS]], while other devices will not. Building an adaptive application means delivering different content to different devices, according to their capabilities. This can bring huge complexity, given the number of different devices in the market with different hardware (screen-sizes, coloring capacity, buttons, memory and speed) and [[Web browser|browsers]]. Software updates on mobile browsers are much more difficult than with desktop browsers, and as a result broken software tends to stay in use until the device is discarded.

Many software initiatives attempt to solve this problem. Most of these initiatives provide a proprietary language to write WAP content, which will render different content (XHTML-MP, [[Wireless Markup Language|WML]], [[CHTML]], etc.) according to the requesting device. One commercial initiative is [[Wurfl|WURFL]], which uses a hierarchical [[XML]] configuration file mapping hundreds of device capabilities. WURFL also offers a "Wireless Abstraction Layer", called WALL, which specifies special tags that are automatically converted into a markup language supported by the device. The [[W3C]] [[W3C Device Description Working Group|DDWG]] has created a specification to standardize access to repositories of device capability information, to be part of a common framework for content adaptation technologies.

== Example ==

A complete [[Valid XML document|valid]] and [[Well-formed XML document|well-formed]] example is:

Line 56:

When served with a [[MIME]] type of "application/xhtml+xml" or "application/vnd.wap.xhtml+xml".

== Notes ==

<references />

== External links ==

* [http://www.openmobilealliance.org/ Open Mobile Alliance]

* W3C Recommendation for [http://www.w3.org/TR/xhtml11/ XHTML 1.1]

* W3C Recommendation for [http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/ Modularization of XHTML] as of April 10, 2001.

* [http://www.passani.it/gap/ XHTML-MP Authoring PracticesvteStandards]

{{Open Mobile Alliance standards}}