Table of topic groups > Front page of help pages > Help pages > 5. Help for TM WAPPush menu

5. Help for TM WAPPush menu

Topics

• Common
• The correct order of PAP-elements
  • How to read DTD-files
  • Detailed information
• Official recommendations and other help pages

Common

The menu is under construction. I made it according to official DTD-files. Today I have made the PAP (Push Access Protocol) portion. The meaning of this protocol is to give information to the Push Proxy Gateway. Then the user can get special WAP services. I'm not yet familiar to them but I want to know, what PAP could offer.

The PAP-document is before the actual WML-document, which a user of WML browser can read. Then the whole document has several sub documents, which must separate from each others with boundary marks. The whole documents and sub documents must have content type declarations and a boundary definition. Content type and boundary definitions are from the book Inside WAP (a Finnish book), Pekka Niskanen, a worker of Acta Systems Oy (IT Press, 2000). The boundary name end_of_part could be other.

After the wml-document could be information concerning the User Agent Profile with RDF (Resource Description Framework ). In RDF-documents the root element is usually with prefix (rdf:RDF instead of RDF). The content-type for this is also application/xml like to PAP-documents. In fact it is impossible to create very well RDF-menu because it and its assistant languages don't have DTD-files and it is always just a schema. The core schema vocabulary is defined in a namespace informally called rdfs. RDF transfer web metadata.

When I created button to PAP (Push Access Protocol), I tried to follow terms and classifications of the pap_1.0.dtd. The address and quality-of-service elements are classified in push submission message. Because they can be as children elements to elements, which are in the DTD classified into other groups (for example cancel operation and status query elements), I have made for them own buttons. I divided push submission message elements into parent and child elements (SubmissionP and SubmissionC because they are too big together.

I made buttons to RRF according to the Table of Contents of the W3C Candidate Recommendation 27 March 2000 using the same terminology and the same order. Use the recommendation itself as the main help file. I added those attributes, which are mentioned in the recommendation. Note, that resource belongs to rdf-namespace. If it is used inside other namespaces, it needs prefix (rdf:resource). You can always use the attribute with the prefix.

The RDF portion of the menu is not intended to be a comprehensive menu. Every user of the menu can create additional modules to the plugin. That's why this menus doesn't belong to the TM ALL menu.

All elements, which have termination tags can be used by enclosing them into a selection even if the button hint is Insert.... The result is however different concerning line breaks. I have added all required attributes as default attributes like in the TM WML menu.

The correct order of PAP-elements

This information base on the information from the DTD-file, where is entity references (they are called also as DTD-macros) and entity declarations (an example from the page Help for HTMLAll). You can read this information also from the DTD, where you can check, is some child element required or not and how many each child elements can or must be (I might have written mistakenly something wrong).

How to read DTD-files

Because also HTML and XHTML use this kind of notation, I give common hints to read the DTD-files. You can find more thoroughly information from W3C. Note however that XML has more strict rules than HTML and omitting terminations is forbidden. DTD tells the content of some elements as element declarations, which begins <!ELEMENT elementName with possible separator marks (in HTML DTD-files is --, but they are not used in many XML-languages) and after that the content, which can have following information:

• (elementName1 | elementName2) = alternative child-elements
• (elementName1, elementName2) = the correct order of child-elements. The element elementName1 must be before the elementName2.
• (elementName1 & elementName2) = both must occur, in any order. Note, that this can be altered with the ? mark: (elementName1 & elementName2?) - now only the first element is required.
• elementName = one required child-element
• elementName+ = one or more required child-elements
• elementName? = one optional child-element
• elementName* or (elementName1 | elementName1)* = zero or more optional child-elements
• (%Element.Group; | elementAnother)* = on the left is a referation to other parameter entity lists, in this case to <!ENTITY % Element.Group "elementName1 | elementName2 | elementName3 | elementName4">. The information tells that you can use any individual element or elements from an element group in any order and as many times as you want. You can look examples of nested references from Help for HTMLAll).
• +(elementName) = the element may occur
• -(elementName1) = the element must not occur. For example in HTML DTD's (%inline;)* -(A) means that inside the element A can't be another A elements; in other words anchors can't be nested.

Note. Attributes can be expressed at the same principle.

Detailed information

All empty elements except the bad-message element can't have the root element pap as their parent. The children of the element pap are then push-message, push-response, cancel-message, cancel-response, resultnotification-message, resultnotification-response, statusquery-message, statusquery-response, ccq-message, ccq-response and badmessage-response.

If an element can have as its children both address and quality-of-service elements, the address elements are first.

In the button SubmissionP, push-message has address and quality-of-service elements as its children. The push-response element use progress-note elements as first children and after them a response-result element. The button SubmissionC concerns then only the push-response element.

In the button Cancel the element cancel-result is a child of cancel-response. The children of cancel-result are address elements.

In the button Notify the children of resultnotification-message are address and quality-of-service elements. The resultnotification-response element use only the address element.

In the button Query statusquery-message use address elements as its children. The element statusquery-result is a child of statusquery-response. The children of statusquery-result are address elements and a quality-of-service element.

In the button Capabilities the child element is address.

Official recommendations and other help pages

• Resource Description Framework (RDF) Schema Specification 1.0
• Help for TM WML menu
• Help for TM WMLScript menu
• Help for TM CSS menu (An introduction to CSS with frames; In Finnish).
• Help for TM XSLT menu
• Help for HTMLAll menu
• Help for Perl menu