PCDATA

It turns out also that this element has some PCDATA contents, and that it has a seq column value of zero.

Prose-oriented XML, in particular, tends to intersperse PCDATA and tags rather freely.

However, a section can be specialized to eliminate PCDATA, yielding an element-only content model similar to the body level of most DTDs.

And the PCDATA and _XML columns are places to hold the actual element contents (either with or without any embedded character-level markup).

Text in an XML document is generally parsed character data, or (in Document Type Definition terms) PCDATA.

PCDATA is text that will be parsed by a parser . Tags inside the text will be treated as markup and entities will be expanded.

Likewise, a _paras list contains some paragraphs, which are themselves initialized with PCDATA.

As with PCDATA, this class should be inherited from, but no further specialization is required.

I recommend listing PCDATA first in such a list (as DTDs require), but this is not currently mandatory.

An XML element that contains PCDATA should inherit from this, but does not need to provide any further specialization.

Tip: This element may contain literal text, entity references, and #PCDATA.

In other words, you don't need to mark text with the T4 style as opposed to leaving it as PCDATA for the surrounding paragraph.

Text: Simple string data stored as #PCDATA, break, or non-XML characters.

PCDATA may be used directly, and so is not really abstract.