Example messages include news, stock quotes, weather, traffic reports, and notification of events such as email arrival.
The response to the push request is an XML document (push-response, section 9.3) that indicates initial acceptance or failure.
At minimum the PPG MUST validate against the DTD [XML] the control entity in the message and report the result in the response.
The PPG MAY indicate, using progress-note (if requested by the Push initiator in the progress-notes-requested attribute), that other validations have been completed.
A typical response message may contain progress notes for each stage of internal processing.
If the Push Initiator desires information related to the final outcome of the delivery, then it MUST request a result notification information in the push submission and provide a return address (e.g. URL).
If the push submission is indicated as rejected in step two in figure 3, then no result notification will be sent.
This operation allows the Push Initiator to query the PPG for the capabilities of a specific device.
The response is a multipart/related document containing the ccq-response (section 9.11) element in an XML document and, in the second entity, the actual client capabilities information in RDF [RDF] as defined in the User Agent Profile [UAPROF].
There are scenarios in which a Push Initiator may want to send identical messages to multiple recipients.
This section is intended to clarify behaviour related to operations on multiple recipients.
In addition, a single address transmitted on a wireless network may be received by multiple devices (e.g. broadcast).
This type of service is expected for the distribution of information of interest to a broad population (e.g. news, weather, and traffic).
This section is intended to clarify behaviour related to operations involving multicast and broadcast addresses.
Examples of this type of information include the wireless device address, the delivery priority of the message, etc.
The PPG may be configured to perform some transformation on recognisable content (e.g. HTML to WML) for certain wireless devices.
The control entity is a MIME body part which holds an XML document containing one pap element as defined in section 9.1.