Sommaire: Cours wireless telephony application interface specification

Extrait du cours wireless telephony application interface specification

1 Scope
Wireless Application Protocol (WAP) is a result of continuous work to define an industry wide specification for developing applications that operate over wireless communication networks. The scope for the WAP Forum is to define a set of specifications to be used by service applications. The wireless market is growing very quickly, and reaching new customers and services. To enable operators and manufacturers to meet the challenges in advanced services, differentiation and fast/flexible service creation WAP defines a set of protocols in transport, session and application layers. For additional information on the WAP architecture, refer to “Wireless Application Protocol Architecture Specification »[WAP].
2 Document Status
This document is available online in the following formats:
•PDF format at http://www.wapforum.org/.
2.1 Copyright Notice
© Copyright Wireless Application Protocol Forum Ltd, 1999. Terms and conditions of use are available from the Wireless Application Protocol Forum Ltd. web site at http://www.wapforum.org/docs/copyright.htm.
2.2 Errata
Known problems associated with this document are published at http://www.wapforum.org/
2.3 Comments
Comments regarding this document can be submitted to the WAP Forum in the manner published at http://www.wapforum.org/
3 References
The following section describes references relevant to this document.
3.1 Normative references
[ISO8601] “Data elements and interchange formats – Information interchange – Representation of dates and times”, International Organization For Standardization (ISO), 15-June-1988 .“Data elements and interchange formats – Information interchange – Representation of dates and
times, Technical Corrigendum 1”, International Organization For Standardization (ISO) -Technical Committee ISO/TC 154, 01-May-1991
[RFC2119] « Key words for use in RFCs to Indicate Requirement Levels », S. Bradner, March 1997. URL:ftp://ds.internic.net/rfc/rfc2119.txt
[RFC1630] « Uniform Resource Identifiers (URI) », T. Berners-Lee, et al., June 1994. URL:ftp://ds.internic.net/rfc/rfc1630.txt
[WAE] « Wireless Application Environment Specification », WAP Forum, 1998. URL:http://www.wapforum.org/
[WAP] « Wireless Application Protocol Architecture Specification », WAP Forum, 1998. URL:http://www.wapforum.org/
[WML] « Wireless Markup Language », WAP Forum, 1999. URL: http://www.wapforum.org/
[WMLScript] « WMLScript Language Specification », WAP Forum, 1999. URL: http://www.wapforum.org/
[WSP] « Wireless Session Protocol Specification », WAP Forum, 1999. URL: http://www.wapforum.org/
[WTA] « Wireless Telephony Application Specification », WAP Forum, 1999. URL:http://www.wapforum.org/
[XML] « Extensible Markup Language (XML), W3C Proposed Recommendation 10-February-1998, REC-xml-19980210 », T. Bray, et al, February 10, 1998. URL: http://www.w3.org/TR/REC-xml
3.2 Informative references
[RFC1738] « Uniform Resource Locators (URL) », T. Berners-Lee, et al., December 1994. URL:ftp://ds.internic.net/rfc/rfc1738.txt
4 Definitions and abbreviations
The following section describes definitions and abbreviations common to this document.The key words « MUST », « MUST NOT », « REQUIRED », « SHALL », « SHALL NOT », « SHOULD », « SHOULD NOT », »RECOMMENDED », « MAY » and « OPTIONAL » in this document are to be interpreted as described in [RFC2119].
4.1 Definitions
The following are terms and conventions used throughout this specification.Card – a navigable part of a WML document (deck). May contain information to present on the screen, instructions for gathering user input, etc.Client – a device (or application) that initiates a request for connection with a server.Content – synonym for resources.Deck – a WML document. May contain WMLScript.

……..

Si le lien ne fonctionne pas correctement, veuillez nous contacter (mentionner le lien dans votre message)
Wireless telephony application interface specification pdf (276 KO) (Cours PDF)