<content>
<content> (content model) contains the text of a declaration for the schema documented. [22.4.4 Element Specifications] | |||||||||
Module | tagdocs — 22 Documentation Elements | ||||||||
Attributes | att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
| ||||||||
Member of | |||||||||
Contained by | tagdocs: elementSpec macroSpec moduleRef | ||||||||
May contain | Empty element | ||||||||
Declaration |
element content { att.global.attributes, att.global.linking.attributes, att.global.analytic.attributes, att.global.facs.attributes, att.global.change.attributes, attribute autoPrefix { "true" | "false" }?, macro.schemaPattern* } | ||||||||
Example | This content model allows either a sequence of paragraphs or a series of msItem elements optionally preceded by a summary: <content> <rng:choice> <rng:oneOrMore> <rng:ref name="model.pLike"/> </rng:oneOrMore> <rng:group> <rng:optional> <rng:ref name="summary"/> </rng:optional> <rng:oneOrMore> <rng:ref name="msItem"/> </rng:oneOrMore> </rng:group> </rng:choice> </content> | ||||||||
Note | As the example shows, content models may be expressed using the RELAX NG syntax directly. To avoid ambiguity when schemas using elements from different namespaces are created, the name supplied for an element in a content model will be automatically prefixed by a short string, as specified by the prefix attribute on schemaSpec. The autoPrefix attribute may be used to reverse this behaviour. The macro
|