D2d "lablog", User's Manual

Contents are defined as empty.

Contents are defined as empty.

Contents are defined as empty.

Contents are defined as empty.

Contents are defined as empty.

Contents are defined as empty.

[ author
('a' .. 'z' | 'A' .. 'Z' | '0' .. '9' | '_' | '.')+ ], 
('+', 
 [ author
 ('a' .. 'z' | 'A' .. 'Z' | '0' .. '9' | '_' | '.')+ ])* 

('0' .. '9')~+ 

'0' .. '9', '0' .. '9', '0' .. '9', '0' .. '9', 
'0' .. '9', '0' .. '9', '0' .. '9', '0' .. '9'

STR.kind?, STR.E.X.lang?, 
(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle | 
 STR.PHY.src | STR.PHY.verbatimXml | 
 STR.E.nl | STR.E.ldots | STR.E.label | 
 STR.E.ref | STR.E.pers | STR.E.opus | 
 STR.E.persop | STR.E.emph | STR.E.xemph | 
 STR.E.xlang | STR.LINK.treeInclude | 
 STR.LINK.link | STR.BIB.cite | STR.IM.image | 
 STR.LI.list | STR.TA.table | STR.footnote | 
 STR.footnotemark | STR.footnotetext)*  | 
(STR.p | STR.source)+ 

Attention: The first tag is implicit, ie. may not appear in source text.

#implicit name, authors, date, reference* , 
(STR.p | STR.source)* 

(issue | docmat | package)* 

Attention: The first tag is implicit, ie. may not appear in source text.

#implicit name, authors, date, prior, costs, 
desc, note* 

('a' .. 'z' | 'A' .. 'Z' | '0' .. '9' | '_' | '.')+ 

Attention: The first tag is implicit, ie. may not appear in source text.

#implicit authors, date, 
(ACCEPTED | FIXED | CLOSED | WONTFIX | 
 WORKSFORME | REOPENED)?, prior?, costs?, 
(STR.p | STR.source)* 

Attention: The first tag is implicit, ie. may not appear in source text.

#implicit name, (issue | docmat)* 

'0' .. '9'

('a' .. 'z' | 'A' .. 'Z' | '0' .. '9' | '_' | 
 '.' | '/' | ':')+ 

A first small solution for bibliographic data, citation keys and bibliographic lists.
Its structure is based on "bibTeX" and our experiences in bib-style programming, but heavily trying to modernize and orthogonalize.
The grammar definition of the entries is (of course!-) independent of the "kind" of entry, because the complex requirements and implications on the semantical level cannot adequately be expressed by a regular expression. But we decided to coarsely reflect these requirements by grouping the components of an entry. Inside most groups the fields may be permutated.

1. First we require key(implicit), kind, title and one or more authors.
2. Additionally subtitle, latextitle (later:htmltitle !?!)
3. Then may follow references to copies of the text, which have formalized structure, namely url(s), isbn(s), issn(s), doi(s), etc.
4. Then follows either a simple crossref to the collection containing the article,
5. or the standard bibliographic co-ordinates in case of stand-alone publications (place, date, publisher, etc.)
6. At last there may follow abstracts and keywords in different languages, and a list of library signatures where a printed copy is available.

If there is only one single sub-document cited from a collection, its bibliographic co-ordinates may be inlined into the entry for the article. But in contrast to BibTex, we recommend the solution with two(2) separate entries. Nevertheless, we put the "formal references" in the middle of both groups, because in the single-entry case these may either describe just the article, i.e. the head of the entry, or the whole volume, i.e. the tail of the entry.

Please note that the items contained in editors are tagged with author, as the items in authors. Firstly, the code for rendering is inherited, and secondly editors are professional authors, in most cases.

Please note that the problem of a generic, standardized and widely accepted bib-entry format is still unsolved. We plan a whitepaper on this subject, and a preliminary link collection is found in metatools/doc/papers/recherche/recherche_biblio.html.

A citation is a reference to a bibliographic entry, plus possibly a location indication ("pg 12 to 13"). CURRENTLY both is free text, only excluding the delimiter "!".
Every cite is rendered as a xhtml link to the bibliographic entry. This is assumed to be in the same file, OR in the file given by the stylesheet parameter "$user.bibLocation".

STR.BIB.key ~ 
('!' ~ [ locus (0x0001 .. 0xfffe - '!')~+ ] ~ '!')?

The identifier for a bibliographic entry.
This could be replaced by something more restricted, like "alpha~+ ~ digit~*". The key must appear in the bib entry and in all cite-elements. When using this standard rendering script it is also immediately the visible representation of the citation/link. This is a signficant difference to BibTex, and could of course be done differently by some more elaborated rendering script.

(STR.BIB.S.ascii_alpha U '-'U'_' U STR.E.S.decimalDigit)~+ 

This module contains semantic (and a few physical) elements/text particles. Most of them can appear in every context. This module must be instantiated with the contents for emphasizing.

Something emphasized.

(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle | 
 STR.PHY.src | STR.PHY.verbatimXml | 
 STR.E.nl | STR.E.ldots | STR.E.label | 
 STR.E.ref | STR.E.pers | STR.E.opus | 
 STR.E.persop | STR.E.emph | STR.E.xemph | 
 STR.E.xlang | STR.LINK.treeInclude | 
 STR.LINK.link | STR.BIB.cite | STR.IM.image)* 

Such a label binds an identifier to that certain location of the text body where itself happens to appear.
By setting the swich $user.showlabels="yes", these labels and others will be printed in the output, for proof reading.
Putting a label is possible nearly anywhere. If it is in the middle of some text flow, it just marks this special text position. But if it is in a structured object, e.g. the caption of a diagram, its meaning is possibly referring to this diagram. This interpretation and the way a reference is generated may depend on the "ref" elements.

STR.E.S.ascii_lower U STR.SET.ascii_upper ~ 
(STR.SET.alpha U '_' U '-' U STR.E.S.decimalDigit)~* 

Draws three low dots surrounded by spaces.

Contents are defined as empty.

Forces a line break, but not a new paragraph.

Contents are defined as empty.

Title of an opus, a work of art, or any product, (This is a candidate for replacement with some more sophisticated, parser based definition.) Our standard to_xhtml_1_0 script renders it to a span/class=opus, which normally results in slanted small caps.

Personal name. (This is a candidate for replacement with some more sophisticated, parser based, but locale specific definition.) Our standard to_xhtml_1_0 script renders it to a span/class=pers, which normally results in small caps.

Name of its author and name of an opus. Behaves like the sequence of #pers and #opus. Any separation char must be appended to the former.

[ ppers (STR.E.S.all - '!')* ] ~ "!" ~ 
[ popus (STR.E.S.all - '!')* ] ~ "!"

Refering is possible nearly anywhere. Mostly it is to a label.
A hyper-ref link will be generated and its textual appearance will be constructed automatically. There are many different strategies, eg. generating text like "in this list" or "in section 2.1.2 (TITLE OF THE SECTION)". These strategies are selectable and respect the current base language of the text.
(This is achieved by calling the named template "muliDefault", which makes translations into the "default" language.)
The implementation of each rendering strategy starts always with the Xslt template matching "a:ref" and works as follows:

1. Identify the positional context of the reference, e.g. the innermost enclosing section, table, list, etc.
2. Find the label element referred to.
3. If not found, an error is generated and an alerting meta-element inserted in the output.
4. Otherwise, start a mode=getreftext visiting of the label, with the refering context stored to parameters.
5. This visiting traverses upward, up to a nearest common parent, while accumulating the text corresponding to the downward navigation so far.
6. In case of lists and tables as part of TEXT FLOW, the generation of navigation text is delayed, until the next hosting level is found and numbering/counting will be possible.

   The text for sections, chapters, parts etc. is constructed to

           Abschnitt  17.3.1 ("<title-of-the section>")
           ^                 ^ iff user.refTitle=='inline'
           ^                   (otherwise it may be rendered as toolTip)
           ^ translated to doc's default language
      

"floatings" are identified by their genuine reference mechanism.
"lists", "list points", "tables" and "table rows" by counting relative to the nearest "container", which is a list, a table, a floating, a section, etc.
Iff reference and label are in a common container (list, table, or lowest level section), this part of the reference text is abbreviated to "this list"/"this table"/"this section", etc.
There is currently NO further abbreviation implemented, like "next section" or "preceding chapter".

If you want to determine the refering text appearance freely by yourself, using all mark-up currently available, you can always use an explicit "#link" construct, using only the local part of the link target ("fragment identifier", in w3c speak)
So you can link to "mylabel" directly by
"... and #link#loc mylabel#text here is the #emph!real! text#/link ..."

STR.E.S.ascii_lower U STR.SET.ascii_upper ~ 
(STR.SET.alpha U '_' U '-' U STR.E.S.decimalDigit)~* 

Something strongly emphasized.

(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle | 
 STR.PHY.src | STR.PHY.verbatimXml | 
 STR.E.nl | STR.E.ldots | STR.E.label | 
 STR.E.ref | STR.E.pers | STR.E.opus | 
 STR.E.persop | STR.E.emph | STR.E.xemph | 
 STR.E.xlang | STR.LINK.treeInclude | 
 STR.LINK.link | STR.BIB.cite | STR.IM.image)* 

A short sentence/sequence of words in some foreign lanugage, -- less than a whole paragraph. Our standard to_xhtml_1_0 rendering creates a span element with an xml:lang attribute, which you may render by css as you like.

Attention: The first tag is implicit, ie. may not appear in source text.

#implicit STR.E.X.lang, 
(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle | 
 STR.PHY.src | STR.PHY.verbatimXml | 
 STR.E.nl | STR.E.ldots | STR.E.label | 
 STR.E.ref | STR.E.pers | STR.E.opus | 
 STR.E.persop | STR.E.emph | STR.E.xemph | 
 STR.E.xlang | STR.LINK.treeInclude | 
 STR.LINK.link | STR.BIB.cite | STR.IM.image)* 

Primitive elements for embedding of and linking to other documents.

The target where to open the new link. This cannot be rendered in xhtml 1.0 strict! A javascript based implementation must be provided by the user whenever this "target" feature shall be used in xhtml 1.0 strict. The standard xslt script will ignore it and emit a warning iff $user.xhtmlVariant ist set to "strict".

Contents are defined as empty.

The target where to open the new link. This cannot be rendered in xhtml 1.0 strict! A javascript based implementation must be provided by the user whenever this "target" feature shall be used in xhtml 1.0 strict. The standard xslt script will ignore it and emit a warning iff $user.xhtmlVariant ist set to "strict".

The target where to open the new link. This cannot be rendered in xhtml 1.0 strict! A javascript based implementation must be provided by the user whenever this "target" feature shall be used in xhtml 1.0 strict. The standard xslt script will ignore it and emit a warning iff $user.xhtmlVariant ist set to "strict".

Contents are defined as empty.

Inter document link, very similar to classical html <a> element. But it is a little bit higher level!

Attention: The first tag is implicit, ie. may not appear in source text.

#implicit STR.LINK.url, 
((STR.LINK.link.blank | STR.LINK.link.top | 
  STR.LINK.link.inframe | STR.LINK.link.framename)? & 
 STR.LINK.link.text? & STR.LINK.loc? & 
 STR.LINK.link.refdate?)

The location/fragment in the document (what normally appears behind a hashmark!-) A link must contain either an url or a loc entry, or both.

The calendaric date when the meant contents of the link had been retrieved.

The text to print when the link is rendered. It is defined by a generic parameter, so anything may appear there, depending on the instantiation of this module.
If this field is left out, then the url will be taken as text.
In this case, if the url starts with a digit, then the prefix replacing this digit is taken from the stylesheet parameter $user.linktextprefices. This allows more readable, more symbolic references to frequently used mount points.
If the text is present and starts with an exclamation mark "!", then this is also replaced by this prefix.

(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle | 
 STR.PHY.src | STR.PHY.verbatimXml | 
 STR.E.nl | STR.E.ldots | STR.E.label | 
 STR.E.ref | STR.E.pers | STR.E.opus | 
 STR.E.persop | STR.E.emph | STR.E.xemph | 
 STR.E.xlang | STR.LINK.treeInclude | 
 STR.BIB.cite | STR.IM.image)* 

The target where to open the new link. This cannot be rendered in xhtml 1.0 strict! A javascript based implementation must be provided by the user whenever this "target" feature shall be used in xhtml 1.0 strict. The standard xslt script will ignore it and emit a warning iff $user.xhtmlVariant ist set to "strict".

Contents are defined as empty.

Includes an xml text corpus into the rendering process. "url" gives the file position, and "mode" gives the mode parameter to the "apply-templates" call.
CURRENTLY PATH is not yet operative, because there are problems serializing the dynamic xpath extension required for its execution.

Attention: The first tag is implicit, ie. may not appear in source text.

#implicit STR.LINK.url, STR.LINK.path, 
STR.LINK.mode?

The url of a link or a resource.
(This is currently NOT YET parsed, but can be any sequence of characters. Errors will occur later, when the link is used !-)
Iff the url starts with a digit=n, then there must be an n-th entry in the self-structured list in the stylesheet parameter $user.linkurlprefices, and the digit is replaced by this.

Physical mark-up is mostly deprecated. It follows the (old!) html way of physical mark-up. In this basic model this can only be applied to physical mark-up itself/recursively. The declaration is naive, allowing multiple (nested) application of the same modifier. It can NOT be applied to semantic mark-up. Additionally this module defines some html/xml specific elements.

Explicitly select blinking text. Not only deprecated, but also bad manners.
The xslt rule generates a <span style="text-decoration:blink;">, because the old <blink> tag has not been taken over to xhtml 1.0 strict. Explicitly select stroke-out text. Deprecated.

(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle)* 

Explicitly select bold text. Deprecated. Consider to use basic.inlineElements:xemph instead.

(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle)* 

Explicitly select superscript. Deprecated.

(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle)* 

Explicitly select subscript. Deprecated.

(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle)* 

Explicitly select italic text. Deprecated. Consider to use basic.inlineElements:emph instead. Explicitly select underlined text. Deprecated.
The xslt rule generates a <span style="text-decoration:underline;">, because the old <u> tag has not been taken over to xhtml 1.0 strict.

(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle)* 

Explicitly select larger font. Deprecated.

(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle)* 

Explicitly select small caps. Deprecated. Consider to use basic.inlineElements:opus or basic.inlineElements:pers instead.

(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle)* 

Explicitly select smaller font. Deprecated.

(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle)* 

Inserts an html-<span style='xxx'>

Attention: The first tag is implicit, ie. may not appear in source text.

#implicit STR.PHY.style, 
(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle)* 

(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle)* 

(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle)* 

A by-pass when generating html/xhtml documents. This element is intended to contain special html fragments which shall be included verbatim in the output. This is achieved simply by an xslt rule which disables output escaping.

Currently only four hex digits are decoded for character values, so that the higher unicode planes (beyond 0x0_FFFF) can currently (201200208) not be described on the d2d input side. (They can be output by xslt).

0x0001 .. 0xfffe

STR.E.S.ascii_lower U STR.SET.ascii_upper

STR.E.S.ascii_lower U STR.SET.ascii_upper

'a' .. 'z'

'A' .. 'Z'

'0' .. '9'

' ' U \t U \n U \r

If you leave it out, some alternative text from the enclosing elements must be found for rendering. This searched for by the named template 'copyAltFromContext', which otherwise will fail with an error.

STR.IM.image.file & STR.IM.image.alt? & 
STR.IM.image.width? & STR.IM.image.height? & 
STR.IM.image.align? & STR.IM.image.showLabel?

Contents are defined as empty.

A very simple list module.

STR.E.S.ascii_lower U STR.SET.ascii_upper ~ 
(STR.SET.alpha U '_' U '-' U STR.E.S.decimalDigit)~* 

(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle | 
 STR.PHY.src | STR.PHY.verbatimXml | 
 STR.E.nl | STR.E.ldots | STR.E.label | 
 STR.E.ref | STR.E.pers | STR.E.opus | 
 STR.E.persop | STR.E.emph | STR.E.xemph | 
 STR.E.xlang | STR.LINK.treeInclude | 
 STR.LINK.link | STR.BIB.cite | STR.IM.image | 
 STR.LI.list | STR.TA.table | STR.footnote | 
 STR.footnotemark | STR.footnotetext | STR.p)* 

(STR.LI.list.symbol? & 
 (STR.LI.list.startnum | STR.LI.list.continues)? & 
 STR.E.label?), STR.LI.list.i+ 

longminus, openSquare, diamond, openDiamond are not yet supported.

CURRENTLY the starting number of a numbered list CANNOT be set anymore! Once, in former html versions, this was possible. NOW it is advised to use CSS-three for this purpose, but this is not yet on the market.
THEREFORE we ignore the value of "startnum" and of "continues".
IT COULD be built by rendering the list-items explicitly, not using the <ol> construct, but <xsl:number> and <html:dd> instead. But we are not sure whether this is sensible.

('0' .. '9')~+ 

@listSymbol

Values for kind, style, width of cell borders, following CSS2.0 syntax. Valid for the whole table.

(STR.SET.alpha U '_' U '-' U STR.E.S.decimalDigit)~+ 

Most simple table model; sufficient for many use cases, but can of course be replaced by something more elaborate, when necessary.
The nomenclature follows html.

Labels at the explicit positions refer to the table or the table row; references to labels appearing anywhere in the text will contain the full address path "table <T>, row <R>, column <C>". Numbering starts with one(1).

(STR.TA.border? & STR.E.label?), STR.TA.tr* 

STR.TA.c?, 
(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle | 
 STR.PHY.src | STR.PHY.verbatimXml | 
 STR.E.nl | STR.E.ldots | STR.E.label | 
 STR.E.ref | STR.E.pers | STR.E.opus | 
 STR.E.persop | STR.E.emph | STR.E.xemph | 
 STR.E.xlang | STR.LINK.treeInclude | 
 STR.LINK.link | STR.BIB.cite | STR.IM.image | 
 STR.LI.list | STR.TA.table | STR.footnote | 
 STR.footnotemark | STR.footnotetext | STR.p)* 

(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle | 
 STR.PHY.src | STR.PHY.verbatimXml | 
 STR.E.nl | STR.E.ldots | STR.E.label | 
 STR.E.ref | STR.E.pers | STR.E.opus | 
 STR.E.persop | STR.E.emph | STR.E.xemph | 
 STR.E.xlang | STR.LINK.treeInclude | 
 STR.LINK.link | STR.BIB.cite | STR.IM.image | 
 STR.LI.list | STR.TA.table | STR.footnote | 
 STR.footnotemark | STR.footnotetext | STR.p)* 

STR.E.label?, (STR.TA.td*  | STR.TA.th* )

This module defines the structural elements like paragraphs, chapters, etc. It starts plugging the sub-modules together, and distributing parametrization, without yet defining the very top of the corpus structure.

STR.symbol?, 
(STR.kind?, STR.E.X.lang?, 
 (#chars | 
  STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
  STR.PHY.blink | STR.PHY.strikeout | 
  STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
  STR.PHY.smaller | STR.PHY.indexlo | 
  STR.PHY.indexhi | STR.PHY.spanstyle | 
  STR.PHY.src | STR.PHY.verbatimXml | 
  STR.E.nl | STR.E.ldots | STR.E.label | 
  STR.E.ref | STR.E.pers | STR.E.opus | 
  STR.E.persop | STR.E.emph | STR.E.xemph | 
  STR.E.xlang | STR.LINK.treeInclude | 
  STR.LINK.link | STR.BIB.cite | STR.IM.image | 
  STR.LI.list | STR.TA.table | STR.footnote | 
  STR.footnotemark | STR.footnotetext)*  | 
 STR.p+ )

STR.symbol?

STR.symbol?, 
(STR.kind?, STR.E.X.lang?, 
 (#chars | 
  STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
  STR.PHY.blink | STR.PHY.strikeout | 
  STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
  STR.PHY.smaller | STR.PHY.indexlo | 
  STR.PHY.indexhi | STR.PHY.spanstyle | 
  STR.PHY.src | STR.PHY.verbatimXml | 
  STR.E.nl | STR.E.ldots | STR.E.label | 
  STR.E.ref | STR.E.pers | STR.E.opus | 
  STR.E.persop | STR.E.emph | STR.E.xemph | 
  STR.E.xlang | STR.LINK.treeInclude | 
  STR.LINK.link | STR.BIB.cite | STR.IM.image | 
  STR.LI.list | STR.TA.table | STR.footnote | 
  STR.footnotemark | STR.footnotetext)*  | 
 STR.p+ )

[ pkind
STR.E.S.ascii_lower U STR.SET.ascii_upper ~ 
(STR.SET.alpha U '_' U '-' U STR.E.S.decimalDigit)~* ] ~ 
("+" ~ 
 [ pkind
 STR.E.S.ascii_lower U STR.SET.ascii_upper ~ 
 (STR.SET.alpha U '_' U '-' U STR.E.S.decimalDigit)~* ])~* 

The paragraph is the central means for organizing text, eg. wrt. language and kind.

When rendering to xhtml, the items contained in "kind" are prepended with "paragraphkind_" and then stored as "css class names", so that visual appearance can be controlled via css.
Furthermore, setting the variable user.p_kind_filter lets only pass those paragraphs with a non-empty intersection with this value.
ATTENTION: the values of "kind" are currently not restricted by an enumeration type (since enumeration are not yet rewritable!), but are free identifiers. So typos are not recognized and can cause missing or ill-rendered text.

Due to its central role in organization, the contents of p also includes tables and lists, which cannot be rendered in xhtml:p. The difference is bridged by the rotation algorithm. The transition between the possible contents is like this:

             d2d:h2                     xhtml:              
               |
               p                         p      list  p     table
      /    /   |   \    \              /  \           |
 chars link  list chars table       chars  link     chars  
      

In the other direction, a d2d:p can be contained also in containers like list item or table cell. Luckily, this is identical to xhtml:

          table/tr/td      
                   |
                   p
          list/i       = ul(ol)/li
               |                 |
               p                 p
      

STR.kind?, STR.E.X.lang?, 
(#chars | 
 STR.PHY.bold | STR.PHY.ital | STR.PHY.ulin | 
 STR.PHY.blink | STR.PHY.strikeout | 
 STR.PHY.scaps | STR.PHY.hh | STR.PHY.larger | 
 STR.PHY.smaller | STR.PHY.indexlo | 
 STR.PHY.indexhi | STR.PHY.spanstyle | 
 STR.PHY.src | STR.PHY.verbatimXml | 
 STR.E.nl | STR.E.ldots | STR.E.label | 
 STR.E.ref | STR.E.pers | STR.E.opus | 
 STR.E.persop | STR.E.emph | STR.E.xemph | 
 STR.E.xlang | STR.LINK.treeInclude | 
 STR.LINK.link | STR.BIB.cite | STR.IM.image | 
 STR.LI.list | STR.TA.table | STR.footnote | 
 STR.footnotemark | STR.footnotetext)* 

Larger unit of program source text, rendered as a text block on its own. Its input mode is "verbatim". This means (1) respecting whitespace and line breaks, (2) must be ended by an explicit end token, (3) all command characters will be ignored, except of those DIRECTLY followed by a tag of an explicitly mentioned direct sub-element (here: "label").

(#chars | STR.E.label | STR.LINK.treeInclude)* 

(STR.E.S.all - STR.SET.whitespace)~+