I list below all topic groups, which I have done according to subjects, which they handle. You can return to this topic group by using this menu and the link Table of topic groups on the top of the each page.
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.Acta Systems Oy, IT Press, Satku: Perl examples.
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
When I created button to PAP (Push Access Protocol), I tried to follow terms and
classifications of the pap_1.0.dtd. The
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
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.W3C: Resource Description Framework (RDF) Schema Specification 1.0.
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).
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
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
(elementName1 | elementName2)= alternative child-elements
(elementName1, elementName2)= the correct order of child-elements. The element
elementName1must be before the
(elementName1 & elementName2)= both must occur, in any order. Note, that this can be altered with the
(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
(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
Acan't be another
Aelements; in other words anchors can't be nested.
Note. Attributes can be expressed at the same principle.W3C: How to read HTML DTD.
All empty elements except the
can't have the root element
pap as their parent. The
children of the element pap are then
If an element can have as its children both
address elements are first.
In the button SubmissionP,
elements as its children. The
progress-note elements as first children and
after them a
response-result element. The button
SubmissionC concerns then only the
In the button Cancel the element
cancel-result is a child of
cancel-response. The children of
In the button Notify the children of
quality-of-service elements. The
resultnotification-response element use only the
In the button Query
address elements as its children. The element
statusquery-result is a child of
statusquery-response. The children of
In the button Capabilities the child element is