WMLScript Developer's Guide

[Cover] [Previous Section] [Next Section] [Index]

Current chapter: Chapter 5 - Pragmas
Section 26 out of 57 total sections , Section 4 out of 4 sections in this chapter


Meta-Information

Meta-information pragmas specify a file's property name and content. Meta-information pragmas can also specify a file's scheme, which specifies a form or structure that may be used to interpret the property value--the values vary depending on the type of meta-data. The attribute values are string literals.

Meta-pragmas do not define any properties, nor do they define how user agents must interpret meta-data. User agents are not required to act on the meta-data.

Meta-pragmas can have the following attributes:



Name

The Name pragma specifies meta-information used by the origin servers. The user agent should ignore any meta data named with this attribute. Network servers should not emit WMLScript content containing name meta-pragmas.

For example:

use meta name "Created" "18-June-1999";  


HTTP Equiv

The HTTP Equiv pragma specifies meta-information indicating that the property should be interpreted as an HTTP header. Meta-data named with this attribute should be converted to a wireless session protocol (WSP) or HTTP response header if the file is compiled before it arrives at the user agent.

For example:

use meta http equiv "Keywords" "Script, Language";  


User Agent

The User Agent pragma specifies meta-information intended for user agents. This meta-data must be delivered to the user agent and must not be removed by any network intermediary.

For example:

use meta user agent "Type" "Test";  


[Cover] [Previous Section] [Next Section] [Index]


Part Number DKDS-41-002, UP.SDK Release 4.1, December 2000

Copyright © 1994-2000 Openwave Systems Inc. All rights reserved.
Please send comments and questions to sdk-doc-comments@openwave.com.