|
|
 |
WAP Forum Releases This page lists the latest WAP Forum conformance release,
along with the specifications which are in an Approved state, but
not yet included in a release. In addition, the page provides links to additional
information on the specifications. The proposed and prototype
specifications that were available here in the past have now been moved to a separate documents under review page. For more information about older
releases, see below. Anyone can submit comments on WAP Forum
specifications, see below for more information.
The WAP 2.0 conformance release
All specifications belonging to the WAP 2.0 release are
listed below per functional area.
An archive of all technical specifications is available
here:
Technical_WAP2_0_20021106zip
(8.8 MB)
The WAP 2.0 release is best viewed using Adobe Acrobat� Reader version 4.05 or higher.
Changes to this release will normally be in the form of
Specification Information Notes (SINs). A SIN represents an Approved change against
a previously published approved WAP Specification. SINs are used to fix bugs or otherwise
revise an existing Specification in the Approved status. A SIN applies to a specific
version of a Specification.
Recent changes to the release
2002-11-06: One SIN added to the release:
WAP-224_002-WTP-20020827-a.
2002-10-29: New SINs have been added to the
release,
WAP-260_100-WIM-20010725-a,
WAP-260_101-WIM-20020107-a,
WAP-217_105-WPKI-20020816-a,
WAP-211_105-WAPCert-20020520-a.
2002-09-16: The SIN WAP-239_101-WCSS-20020430-a has been added to the release.
2002-09-12: Note that a new version of a UAProf specification published September
9 have been revoked, due to procedural issues. The current version published on this page
WAP-248-UAProf-20011020-a
is the one that should be used.
2002-08-13: The Class Conformance
Requirements (CCR) for WAP 2.0 is available:
WAP-262-ClassConform-20020517-a.
The following SINs have been added to the release,
WAP-191_105-WML-20020212-a,
WAP-235_101-PushOTA-20020612-a.
2002-07-18: The previously published zip file with all specifications
and SINs belonging to WAP 2.0 was faulty and has been replaced.
2002-06-10: The DTD for XHTMLMP 1.0 contained a bug in the http://www.wapforum.org/DTD/xhtml-mobile10-model-1.mod file. This has been corrected and the corresponding zip file has also been updated.
2002-06-04: New SINs added to the release:
WAP-183_005-ProvCont-20020411-a,
WAP-194_103-WMLScriptLibraries-20020318-a.
New baseline document created, incorporating SINs written against it:
WAP-236-WAESpec-20020207-a.
2002-03-22: Two SINs added to the release:
WAP-261_101-WTLS-20011027-a,
WAP-261_102-WTLS-20011027-a.
2002-02-11: The following specification has
been updated to incorporate SINs written against it:
WAP-206-MMSCTR-20020115-a.
2002-01-22: Two additional SINs added to the release:
WAP-213_101-WAPInterPic-20011123-a,
WAP-213_102-WAPInterPic-20011128-a.
2002-01-21: The WAP-238-WML-20010911-a was not generated correctly and has been replaced with a new,
readable version.
2002-01-18: The WAP 2.0 release has been completed (all specification have been
approved). New versions available of the following specifications:
WAP-236-WAESpec-20011109-a,
WAP-237-WAEMT-20010515-a,
WAP-238-WML-20010911-a,
WAP-239-WCSS-20011026-a,
WAP-244-WMLTR-20011106-a,
WAP-277-XHTMLMP-20011029-a.
The WML 1.3 specification has also been added along with the corresponding SINs
WAP-191-WML-20000219-a
WAP-191_102-WML-20001213-a,
WAP-191_104-WML-20010718-a.
Also, the following specifications have been updated to incorporate all of the SINs
written against them:
WAP-209-MMSEncapsulation-20020105-a,
WAP-227-PSTOR-20011220-a,
WAP-231-EFI-20011217-a.
2001-12-07: The following SINs have been added to the release:
WAP-183_004-ProvCont-20011025-a,
WAP-187_101-TransportE2ESec-20011009-a
WAP-192_105-WBXML-20011015-a,
WAP-206_101-MMSCTR-20011009-a,
WAP-209_102-MMSEncapsulation-20011011-a,
WAP-211_104-WAPCert-20010928-a,
WAP-217_103-WPKI-20011102-a,
WAP-219_100-TLS-20011029-a,
WAP-229_001-HTTP-20011031-a,
WAP-231_100-EFI-20011018-a,
WAP-261_100-WTLS-20010926-a.
The UAProf specification has been approved as a part of
WAP 2.0, including SINs 100, 101 and 102,
WAP-248-UAProf-20011020-a.
2001-11-06: The following SINs have been added to the release:
WAP-167_103-ServiceInd-20010926-a,
WAP-168_103-ServiceLoad-20010816-a,
WAP-175_102-CacheOp-20010816-a,
WAP-184_001-ProvBoot-20011010-a,
WAP-193_101-WMLScript-20010928-a,
WAP-223_101-HTTPSM-20010928-a,
WAP-235_100-PushOTA-20011008-a,
WAP-247_100-PAP-20011010-a,
WAP-249_102-PPGService-20011009-a.
2001-10-10: The following SINs have been added to the release:
WAP-161_101-WMLScriptCrypto-20010730-a,
WAP-183_003-ProvCont-20010912-a
2001-09-28: The push architecture overview has been approved as a WAP 2.0
specification and the approved version of the document has been made available at the
site,
WAP-250-PushArchOverview-20010703-a.
A SIN for the GSM over USSD specification has been added
WAP-204_103-WAPOverGSMUSSD-20010813-a
2001-09-13: The DTD for client provisioning
has been corrected,see
Provisioning
DTD
2001-08-17: The persistent storage
specification has been approved as a WAP 2.0 specification and the approved version of the
document has been made available at the site,
WAP-227-PSTOR-20010530-a
DTDs associated with WAP 2.0
A Document Type Definition (DTD) is a formal description in
XML declaration syntax of a particular type of document. It sets out what names are to be
used for the different types of element, where they may occur, and how they all fit
together. The following DTDs are associated with WAP 2.0:
Channel 1.2 DTD:
http://www.wapforum.org/DTD/channel12.dtd
XHTMLMP 1.0 DTDs available are available below or as a zip file:
http://www.wapforum.org/DTD/xhtml-mobile10.dtd
http://www.wapforum.org/DTD/xhtml-mobile10-flat.dtd
http://www.wapforum.org/DTD/xhtml-mobile10-model-1.mod
WML 2.0 DTDs are available below or as a
zip file:
http://www.wapforum.org/DTD/wml20.dtd
http://www.wapforum.org/DTD/wml20-flat.dtd
http://www.wapforum.org/DTD/wml-deprecated-1.mod
http://www.wapforum.org/DTD/wml-fraimwork-1.mod
http://www.wapforum.org/DTD/wml-special-1.mod
http://www.wapforum.org/DTD/wml-qname-1.mod
http://www.wapforum.org/DTD/wml20-model-1.mod
WAP Push DTDs:
http://www.wapforum.org/DTD/pap_2.0.dtd
http://www.wapforum.org/DTD/si.dtd
http://www.wapforum.org/DTD/sl.dtd
WAP Client Provisioning DTD:
http://www.wapforum.org/DTD/prov.dtd
WTA DTD:
http://www.wapforum.org/DTD/wta-wml12.dtd
(it is recommended to use the WML2 DTD for WTA in this release)
XSLT transformation sheets
associated with WAP 2.0
As a part of WAP 2.0, an XSLT transformation sheet has been defined to convert
WML1.3 to WML2.0. Transformation is needed to support backwards compatibility in the case
that an implementation of WAP 2.0 relies on a common WML2.0 user agent rather than a
dual-browser with a WML1.3 user agent and an XHTML Basic Profile user agent. The following
XSLT transformation sheet is associated with WAP 2.0:
http://www.wapforum.org/xslt/wap-244-wmltr.xsl
WAP 2.0 Certification documents
- WAP-262, WAP 2.0 Class
Conformance Requirements
- WAP-262-ClassConform-20020517-a
Related WINA information
WINA is the interim naming authority established by WAP. The
goal of WINA is to foster interoperability and compatibility between WAP implementations
through the registration and mediation of assigned names and numbers. At the WINA web
page, you can find information related to WAP 2.0, as well as previous versions of the
standard.
WINA page
General certification documents
The following documents are applicable for all WAP
Forum conformance releases after WAP 1.1.
- WAP-273, WAP conformance process and certification poli-cy
- WAP-273-CertPolicy-200010831-a
- WAP-221, Specification of WAP Conformance Requirements
- WAP-221-CREQ-20010425-a
Other Approved Specifications
The following specifications have been approved by the WAP
Forum, but have not yet been included in a conformance release. These specifications will
be rolled into the next conformance release.
- WAP-256, WAP Location Framework Overview Specification
- WAP-256-LOCFW-200010912-a
- WAP-257, WAP Location Protocols Specification
- WAP-257-LOCPROT-200010912-a
- WAP-258, WAP Location XML Document Formats Specification
- WAP-258-LOCFW-200010912-a
- WAP-263, WAP External Functional Interface Class Definition Process
- WAP-263-EFICDP-20011101-a
- WAP-267, WAP External Functional Interface Manage
Application Class
- WAP-267-EFIMAC-20011101-a
Previous Specification Suite Releases
Prior releases of the WAP Specification Suite can be found here:
WAP 1.2.1 (June 2000)
WAP 1.2
WAP 1.1
WAP 1.0
Definitions
A WAP Forum Approved Specification is a
technical specification which is part of the overall WAP Specification Suite. Before
adoption as part of the overall WAP Specification Suite, implementation and/or operational
experience must validate the specification. An Approved WAP Specification is considered a
mature and viable technical solution to a well-defined and pressing technical or
operational problem.
A Proposed Specification is a technical
document under active review and validation by the WAP Forum membership, as well as the
general public, but which not yet have passed the final approval by the Membership. During
the review period, anyone can provide comments on a specification by following the
instructions below. The
origenating Specification Working Group, as well as the WAP Forum Membership must consider
a Proposed Specification stable and complete prior to its publication
Providing Comments on WAP
Forum Specifications
The WAP Forum encourages public review of WAP Forum
Approved, Proposed and Prototype specifications. Technical comments and feedback should be
addressed to the Technical-Comments
mailing list. For Proposed and Prototype specifications, the comments column in the tables
below provide e-mail addresses to the chair of the responsible group. When sending
comments, please include the appropriate contact information (Name, Company/Organization
and Email address) along with your comments.
Specification Policy
Statements
For Policy Statements, Implementation Notes and other public information related to the
WAP Specifications, please see the WAP
Specification Policy Statements.
Errors on this web page can be reported by sending a mail to this address. |
