A structural vocabulary module defines a new topic or map type as a specialization of a topic or map type.
The topic or map element type must set the
@DITAArchVersion attribute to
the version of DITA in use, typically by referencing the arch-atts
parameter entity. It must also set the
@domains attribute to the
included-domains entity. These attributes give processors a reliable way
to check the architecture version and look up the list of domains available in the document
The following example shows how these attributes are defined for the
<concept> element in DITA 1.3:
<!ATTLIST concept %concept.attributes; %arch-atts; domains CDATA "&included-domains;">
Specialized topics typically use a parameter entity to define what topic types are permitted to nest. While there are known exceptions described below, the following rules apply when using parameter entities to control nesting.
For example, the name of the parameter entity for the concept topic is concept-info-types.
For example, the following parameter entity sets up default
nesting so that
<concept> will nest only other
<!ENTITY % concept-info-types "%concept;">
As an additional example, the following parameter entity sets up a default that will not allow any nesting:
<!ENTITY % glossentry-info-types "no-topic-nesting">
Default topic nesting in a structural module often set up to use the %info-types; parameter entity rather than using a specific element. When this is done consistently, a shell that includes multiple structural modules can set common nesting rules for all topic types by setting %info-types; entity. The following example shows a structural module that uses %info-types; for default topic nesting:
<!ENTITY % concept-info-types "%info-types;">
For example, with the following content
model defined for
<concept>, a document-type shell that uses
the concept specialization can control which topics are nested in
<concept> by redefining the
concept-info-types parameter entity:
<!ENTITY % concept.content "((%title;), (%titlealts;)?, (%abstract; | %shortdesc;)?, (%prolog;)?, (%conbody;)?, (%related-links;)?, (%concept-info-types;)*)" >
In rare cases, it might not be desirable to control topic nesting with a parameter entity. For example:
Return to main page.
Standards Track Work Product
|Copyright © OASIS Open 2016. All Rights Reserved.||25 October 2016|