"WML 2.0：支持XHTML和TCP/IP协议的无线标记语言规范"

2星需积分: 3 107 浏览量更新于2023-12-20 收藏 389KB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

第二代的无线标记语言(WML 2.0)是根据“可扩展的超文本标记语言”(XHTML)开发的规范。它采用了XHTML的调整扩充机制，使WML2.0可以进行语言转化，并且能支持XHTML和TCP/IP协议。这使得WML 2.0的浏览器能够方便地上网，显示因特网的内容。WML 2.0的规范由Wireless Application Protocol Forum, Ltd.在2001年制定，保留了所有权利。使用条款和条件可从WAP Forum的网站获取。WML 2.0的版本日期为2001年9月11日。WAP Forum网站提供了此文档的勘误和更新列表，以SIN文档的形式发布，这些文档可能会在没有通知的情况下进行修订或删除。 WML 2.0的规范参考了XHTML，并在其基础上进行了调整和扩展。这使得WML 2.0具有灵活的语言转化能力和更广泛的协议支持。通过对XHTML的应用，WML 2.0能够更好地满足用户需求，提供更丰富的内容和更便捷的上网体验。 WML 2.0的发展是为了满足无线应用和互联网内容浏览的需要。通过支持TCP/IP协议，WML 2.0使得移动设备可以轻松地访问因特网，显示因特网内容，从而满足用户对移动设备上网的需求。同时，WML 2.0还保留了WAP的特性，确保了兼容性和互操作性。 WML 2.0的规范在2001年9月11日发布，由WAP Forum制定。WAP Forum是一个专注于无线应用协议发展的组织，致力于推动无线技术的进步和应用。WML 2.0的发布标志着WAP Forum在无线标记语言方面的持续努力和进步，为移动互联网的发展提供了基础支持。总之，WML 2.0是一种满足移动设备上网需求的无线标记语言。它借鉴了XHTML的特性，并在此基础上调整和扩展，以实现更好的语言转化能力和更广泛的协议支持。WML 2.0的发布标志着无线技术的不断进步，为移动互联网的发展提供了重要支持和保障。 WML 2.0的规范是WAP Forum的重要成果，也是无线技术发展的重要里程碑。

资源详情

资源推荐

WAP-238-WML-20010911-a, Version 11-Sep-2001 Page 12 (69)







2001, Wireless Application Protocol Forum, Ltd.

5. User Agent Behaviour (Normative)

5.1. User Agent Behaviour and Features in WAE

The specification covers the elements of the language (see section 6), the use of style with WML (see section 7) and

other aspects of user agent behaviour necessary to implement WML as part of the Wireless Application Environment.

However WML2 depends on user agent behaviour and features described outside of this specification. To fully

understand, implement and use WML2, this specification must be considered in conjunction with the Wireless

Application Environment specification [WAE] and other specifications referenced in both this specification and

[WAE].

5.2. User Agent Context

The user agent context consists of variables and navigation history.

5.2.1. Variables

A WML variable is a name-value pair, where the value is any string in the document character set.

This section describes WML variables in the user agent context. The user agent MUST implement WML variables.

WML variables can be used in the place of strings and are substituted at run-time with their current value.

A variable is said to be set if it has a value not equal to the empty string. A variable is not set if it has a value equal to

the empty string, or is undefined in the current user agent context.

5.2.2. Navigation History

The navigation history is a logical stack of the resources in the navigational path the user traversed to arrive at the

current resource.

This section describes the navigation history maintained by the user agent. The user agent MUST implement the

navigation history model and support all the operations on it defined below.

WML2 includes a simple navigational history model that allows the author to manage backward navigation in a

convenient and efficient manner. The user agent history is modelled as a stack of entries that represent the resources in

the navigational path the user traversed to arrive at the current location. The stack is configured temporally, such that

the newest entry is at the top of the stack and the oldest entry is at the bottom of the stack. Three operations may be

performed on the history stack:

•

Reset - the history stack may be reset to a state where it only contains the current entry. See the

wml:newcontext attribute(section 6.2.1) and newcontext

attribute (section 6.2.3) for more information.

•

Push - a new entry is pushed onto the history stack as an effect of forward navigation.

•

Pop - the current entry (top of the stack) is popped as a result of backward navigation.

As each body/card is accessed via an explicitly specifiedURI, (e.g., via the href attribute in wml:go element,) an

entry for the body/card is added to the history stack even if it is identical to the most recent entry. At a minimum, each

entry must record the resource request information that comprises the absolute URI of the body/card, the method (get or

post) used to access the body/card, the value of any postfields, any XHTML form data name-value pairs, and any

request headers. Document content is not stored in the history. Variable references are never stored in the history. Any

variable references in the resource request information must be replaced with the current value of the variables before

the entry is added to the stack.

The user agent MUST return the user to the previous body/card specified in the history if a prev task is executed (see

section 5.3.2). The execution of prev task pops the current entry from the history stack.

If the body/card is part of a document that was originally fetched using an HTTP post method, and the user agent

MUST re-fetch the document to establish the body/card, then the user agent MUST reissue any post data associated

WAP-238-WML-20010911-a, Version 11-Sep-2001 Page 13 (69)







2001, Wireless Application Protocol Forum, Ltd.

with fetching the original document. The post data values must be the same values used to fetch the original document.

Refer to section 5.3.2 for more information on the semantics of the prev task. See [CACHE] for more information on

caching semantics.

5.3. Navigation Reference Processing Model

A task is a navigational directive executed by the user agent in response to an event such as the activation of a wml:do

element or the expiration of a timer. The navigation reference processing model defines the navigational tasks and the

operations those tasks perform on the user agent context.

The user agent MUST implement all the tasks defined in this section. In addition, the user agent MUST implement the

task failure behaviour.

The following tasks are defined in this section:

•

The go task

•

The prev task

•

The noop task

•

The refresh task

5.3.1. The Go Task

The user agent MUST perform the following steps to execute a go task:

If the originating task contains wml:setvar

elements, the variable name and value in each wml:setvar

element is converted into a simple string by substituting all referenced variables. The resulting collection of

variable names and values is stored in temporary memory for later processing. See section 5.5.1.1 for more

information on variable substitution.

The target URI is identified and fetched by the user agent. The href attribute value is first converted into a

simple string by substituting all referenced variables.

The access control parameters for the fetched document are processed as specified in section 6.16.

The destination is located using the fragment identifier specified in the URI.

If a fragment identifier is not specified as part of the URI, the first body/card in the document is the

destination.

If the wml:use-xml-fragments attribute on the html

element is true (default state)

If a fragment identifier is specified as part of the URI and the document contains a matching element (

attribute of the element is identical to the fragment identifier), the enclosing body/card is the destination.

If the matching element is a

body

or wml:card that body/card is the destination. If the destination is

within the current body/card, the user agent should ensure the matching element is visible to the user.

ii.

If a matching element cannot be found, the first segment in the document is the destination.

If the

wml:use-xml-fragments attribute on the html element is

false

If a fragment

identifier is specified as part of the URI and the document contains a matching body/card

(id attribute of the body/card is identical to the fragment identifier), that body/card is the destination

ii.

If a matching body/card cannot be found, the first body/card in the document is the destination.

The variable assignments resulting from the processing done in step #1 (the wml:setvar element) are applied to

the current user agent context.

WAP-238-WML-20010911-a, Version 11-Sep-2001 Page 14 (69)







2001, Wireless Application Protocol Forum, Ltd.

If the destination contains a newcontext

wml:newcontext

attribute, a new user agent context is created

as described in sections 6.2.1 and 6.2.3.

Create a stack entry. If the destination contains any forms, initialise each form according to section 5.4.2 Form

Initialisation, then store all locally-scoped form control variables in the entry.

An entry referring to the destination is pushed onto the history stack.

If the destination specifies an enterforward intrinsic event binding, the task associated with the event binding is

executed and processing stops. See section 5.6.1 for more information.

10.

If the destination contains a wml:timer element, the timer is started as specified in section 6.16.11.

11.

The destination is displayed using the current variable state and processing stops.

5.3.2. The Prev Task

The user agent MUST perform the following steps to execute a prev task:

If the originating task contains wml:setvar

elements, the variable name and value in each wml:setvar

element is converted into a simple string by substituting all referenced variables. The resulting collection of

variable names and values is stored in temporary memory for later processing. See section 5.5.1.1 for more

information on variable substitution.

The history stack is popped. The target URI is the top of the history stack. The target URI is identified and fetched

by the user agent. The processing that occurs if there is no previous entry in the history stack is implementation

dependent.

The destination is located using the fragment identifier specified in the URI.

If a fragment identifier is not specified as part of the URI, the first body/card in the document is the

destination.

If the wml:use-xml-fragments attribute on the

html

element is true

If a fragment identifier is specified as part of the URI and the document contains a matching element (

attribute of the element is identical to the fragment identifier), the enclosing body/card is the destination. If

the matching element is a body or wml:card , that body/card is the destination. If the destination is

within the current body/card, the user agent should ensure the matching element is visible to the user.

ii.

If a matching element cannot be found, the first body/card in the document is the destination.

If the wml:use-xml-fragments attribute on the html element is false

If a fragment identifier is specified as part of the URI and the document contains a matching body/card

(id attribute of the body/card is identical to the fragment identifier), that body/card is the destination.

ii.

If a matching body/card cannot be found, the first body/card in the document is the destination.

The variable assignments resulting from the processing done in step #1 (the wml:setvar element) are applied to

the current user agent context.

If the destination contains any locally scoped form data, it is refreshed with the form data stored in the entry at the

top of the history stack.

If the destination specifies an enterbackward intrinsic event binding, the task associated with the event binding is

executed and processing stops. See section 5.6.1 for more information.

If the destination contains a wml:timer element, the timer is started as specified in section 6.16.

The destination is displayed using the current variable state and processing stops.

剩余68页未读，继续阅读

hastenlife

粉丝: 0
资源: 2

"WML 2.0：支持XHTML和TCP/IP协议的无线标记语言规范"

WML 2.0 规范

无线标记语言（WML）教程 2.0

惠尔谱wml7001bc说明书

>> wml 不允许使用类 'comm.MSKModulator' 的对象组成数组和括号样式的编制索引功能。只能将 类 'comm.MSKModulator' 的对象用作标量，或者用作元胞数组。 出错 wml (line 6) sMSK = modulator(data); % 进行sMSK调制

代码实现 Docx4j 给不同的节设置不同的页眉

使用Java生成ofd发票文件

有关Java系统开发的外文文献

用java写一段通过word模板生成docx文件并转pdf的代码并可通过浏览器下载

how to split a docx file to docx files by title using docx4j

使用 Docx4j 操作word,并替换word中的占位符，使用Java编写代码

利用Java的docx技术制作一张考研准考证

java 替换word文档中的文字 可以用哪些第三方工具 分别用代码写出来

docx4j 调整html段落边界与文字之间的间距

请问你知道蛋白质功能分类预测最新模型有什么吗？

docx4j 设置页眉

ssh密钥怎么查看

WordprocessingMLPackage 获取当前页眉

docx4j 实现word读取获取图片和文档

dox4j html转换成word,使用Docx4J生成 html

最新资源

>> wml 不允许使用类 'comm.MSKModulator' 的对象组成数组和括号样式的编制索引功能。只能将类 'comm.MSKModulator' 的对象用作标量，或者用作元胞数组。出错 wml (line 6) sMSK = modulator(data); % 进行sMSK调制

java 替换word文档中的文字可以用哪些第三方工具分别用代码写出来