<content>

<content> (content model) contains the text of a declaration for the schema documented. 22.4.4 Element Specifications
Module tagdocs — 22 Documentation Elements
In addition to global attributes In addition to global attributes
autoPrefix controls whether or not pattern names generated in the corresponding RELAXNG schema source are automatically prefixed to avoid potential nameclashes.
Status Optional
Datatype 

<rng:ref name="data.truthValue"/>
data.truthValue
Legal values are:
true
Each name referenced in e.g. a <rng:ref> element within a content model is automatically prefixed by the value of the prefix attribute on the current schemaSpec [Default]
false
No prefixes are added: any prefix required by the value of the prefix attribute on the current schemaSpec must therefore be supplied explicitly, as appropriate.
Used by
elementSpec macroSpec moduleRef
May contain Empty element
Declaration 

<rng:element name="content">
 <rng:ref name="att.global.attributes"/>
 <rng:optional>
  <rng:attribute name="autoPrefix" a:defaultValue="true">
   <rng:choice>
    <rng:value>true</rng:value>
    <rng:value>false</rng:value>
   </rng:choice>
  </rng:attribute>
 </rng:optional>
 <rng:zeroOrMore>
  <rng:group>
   <rng:ref name="macro.schemaPattern"/>
  </rng:group>
 </rng:zeroOrMore>
</rng:element>
element content
{
   att.global.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 macro.schemaPattern defines which elements may be used to define content models. Alternatively, a content model may be expressed using the TEI valList element.