Admin CliCours
Sommaire: Course pdf service indication spécification
1.SCOPE
2.DOCUMENT STATUS
2.1COPYRIGHT NOTICE
2.2ERRATA
2.3COMMENTS
3.REFERENCES
3.1NORMATIVE REFERENCES
3.2INFORMATIVE REFERENCES
4.DEFINITIONS AND ABBREVIATIONS
4.1DEFINITIONS
4.2ABBREVIATIONS
5.INTRODUCTION
6.THE SERVICE INDICATION CONTENT FORMAT
6.1SERVICE INDICATION CHARACTER SET
6.2THE SI ELEMENT
7.SEMANTICS
7.1INTRODUCTION
7.2RECEPTION
7.3PRESENTATION
7.4SERVICE INVOCATION
7.5EXPIRATION
8.SI REFERENCE INFORMATION
8.1DOCUMENT IDENTIFIERS
8.2DOCUMENT TYPE DEFINITION (DTD)
9.A COMPACT BINARY REPRESENTATION OF SERVICE INDICATION
9.1EXTENSION TOKENS
9.2ENCODING SEMANTICS
9.3NUMERIC CONSTANTS
10.EXAMPLE
11.STATIC CONFORMANCE REQUIREMENTS
11.1CLIENT FEATURES
1.2PUSH PROXY GATEWAY FEATURES
Extrait du course pdf service indication spécification
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 providing new 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 Forum Ltd, 1998, 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
3.1 Normative references
[HTML4] « HTML 4.0 Specification, W3C Recommendation, revised on 24-Apr-1998 », D. Raggett et al.,April 24 1998. URL: http://www.w3.org/TR/1998/REC-html40-19980424
[RFC2119] « Key words for use in RFCs to Indicate Requirement Levels », S. Bradner, March 1997.
URL: http://www.ietf.org/rfc/rfc2119.txt
[WAE] “Wireless Application Environment Overview”, WAP Forum, 04-Nov-1999,
URL: http://www.wapforum.org/
[WBXML] “WAP Binary XML Content Format”, WAP Forum, 04-Nov-1999,
URL: http://www.wapforum.org/
[WINA] « WAP Interim Naming Authority », WAP Forum,
URL:http://www.wapforum.org/wina/
[WML] “Wireless Markup Language”, WAP Forum, 04-Nov-1999,
URL: http://www.wapforum.org/
[XML] “Extensible Markup Language (XML)”, W3C 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
[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
[PushOTA] “WAP Push OTA Specification”, WAP Forum, 08-Nov-1999
URL: http://www.wapforum.org/
[PushPAP] “WAP Push Access Protocol Specification”, WAP Forum, 08-Nov-1999
URL: http://www.wapforum.org/
[RFC2396] “Uniform Resource identifiers (URI): Generic Syntax”, T. Berners-Lee, et al., August 1998.
URL: http://www.ietf.org/rfc/rfc2396.txt
[WAP] “Wireless Application Protocol Architecture Specification”, WAP Forum, 30-Apr-1998
URL: http://www.wapforum.org/
4. Definitions and Abbreviations
4.1 Definitions
The following are terms and conventions used throughout this specification.
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 by [RFC2119].
Application – A value-added data service provided to a WAP Client. The application may utilise both push and pull data transfer to deliver content
Application-Level Addressing – the ability to address push content between a particular user agent on a WAP client and push initiator on a server.
……..
Si le lien ne fonctionne pas correctement, veuillez nous contacter (mentionner le lien dans votre message)Course pdf service indication spécification (247 KO) (Cours PDF)
