DocServer DTD

Elements

FrontierDocs

Verb

Syntax

I’m not sure about whitespace here. Probably significant, though.

There can be more than one syntax element, for cases where there are two ways to do something – “local” for instance.

Parameter List

This is an element which exists only to contain a series of other elements, like HTML lists.

Parameter Item

Each parameter gets its own list parameter list item.

Action

Returns

Examples

The Example element would be the place where strange entities would be most likely.

An Example element can have any number of input/output pairs. This arrangement is like a definition list in HTML.

Input

Whitespace is significant here.

Output

Whitespace is significant here.

Comment

This is a normal text element which describes the example item.

Errors

Note List

This is an element which exists only to contain a series of other elements, like HTML lists.

Note Item

Each note gets its own note list item.

See Also

This is an element which exists only to contain a series of other elements, like HTML lists.

Reference

Each Reference gets its own reference list item.

Entities

We getsome of these (>, <, etc.) for free as part of the XML spec it looks like. However, we’ll still need more for things specific to Frontier such as the comment character (

Unfortunately, I have no idea how to specify entities in a DTD. That part of the spec is currently going over my head.

comment character

This is very important, since the comment shows up all over the place, in many of the DocServer examples.

typographic quotes

“”‘’

These aren’t quite as important. These show up in the DocServer quotes page, I’m not sure where else.

comparison symbols

[not equal][less equal][greater equal]

These show up in DocServer’s pages for ‘<=’ and ‘>=’.