The <meta> Element

The <meta> element places an item of arbitrary meta-information in a WML deck. This item is structured as a property name and its value. You can put any number of <meta> elements into the <head> element. This can add keywords for indexing purposes, store hints about the content of the deck, and store any other information. No standard properties have yet been defined for WML, but conventions will develop, just as they did with HTML.

Tip

Note that some browsers may not support all the features of the <meta> element.

Attributes of the <meta> Element

name (string; optional)

Gives the name of this property. Meta-information with this attribute is intended for server-side applications, so it may be removed before it gets to the browser.

http-equiv (string; optional)

An alternative for the name attribute (you can’t specify both on the same <meta> element). If this attribute is present, it specifies that the property should be sent to the browser via HTTP or WSP headers (WAP gateways and WSP headers are explained in Appendix B ). For example, this element tells any proxy servers or gateways (as well as the browser itself) not to cache the deck:

<meta http-equiv="Cache-control" content="no-cache"/>
forua (boolean; optional)

If present and set to true, indicates that the property is intended for the use of the browser. (ua comes from user agent, the term that the WAP specifications use to refer to the browser.)

content (string; required)

Specifies the value of the property ...

Get Learning WML, and WMLScript now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.