Aggregated RFC-2119 statements
This section is non-normative.
This appendix contains all the normative statements from the DITA for Technical Content 2.0 specification. They are aggregated here for convenience in this non-normative appendix.
Aggregated error statements
- DTTCERR-0010
- It is an error to use
parse="xml"anywhere other than within<foreign>or a specialization thereof. - DTTCERR-0020
- It is an error to use
parse="xml"anywhere other than within<foreign>or a specialization thereof.
Implementation dependent statements
- DTTCIMP-0010
- Processing expectations for glossary entry topics are highly implementation-specific and will depend on the output format.
- DTTCIMP-0020
- The available height is implementation dependent, but if feasible, it is suggested to be the page or table cell height or some other reasonable value.
- DTTCIMP-0030
- Processors can also define custom, implementation-specific tokens for this attribute.
- DTTCIMP-0040
- Processors can also define custom, implementation-specific tokens for this attribute.
- DTTCIMP-0050
- The necessity and uses of
@encodingfor non-standard values of@parseare implementation-dependent. - DTTCIMP-0060
- Processors can also define custom, implementation-specific tokens for this attribute.
- DTTCIMP-0070
- Processors can also define custom, implementation-specific tokens for this attribute.
- DTTCIMP-0080
- The necessity and uses of
@encodingfor non-standard values of@parseare implementation-dependent.
Aggregated RFC-2119 statements
- DTTCREQ-0010
- When a processor encounters an
<abbreviated-form>element that references a DITA topic, if the referenced topic is not a<glossentry>topic or a specialization of<glossentry>, the title of the topic SHOULD be rendered. - DTTCREQ-0020
- When a processor encounters an
<abbreviated-form>element that references a DITA topic, if the referenced topic is a<glossentry>topic or a specialization of<glossentry>, processors SHOULD render the<abbreviated-form>element in the following ways:- First usage
- Render the contents of the
<glossSurfaceForm>element, if it is not empty. If the<glossSurfaceForm>is empty or does not exist, render the contents of the<glossterm>element. - Second and later usage
- Render the contents of the
<glossAcronym>element, if it is not empty. If the<glossAcronym>is empty or does not exist, render the contents of the<glossterm>element.
- DTTCREQ-0030
- Processors which render the content of
<stepsection>elements among the<step>elements MUST NOT number the<stepsection>elements. - DTTCREQ-0040
- When the
<equation-number>element has empty content, the equation number SHOULD be generated. - DTTCREQ-0050
- When the
<equation-number>element is not empty, the content SHOULD be used as the equation number. - DTTCREQ-0060
- Processors MAY add punctuation or decoration to the number.
- DTTCREQ-0070
- Processors SHOULD process the
MathML as though the
<m:math>element occurs directly in the content of the containing<mathml>element. - DTTCREQ-0080
- Processors SHOULD preserve line the breaks and spaces
that are present in the content of a
<codeblock>element. - DTTCREQ-0090
- Processors SHOULD preserve the
line breaks and spaces that are present in the content of a
<msgblock>element. - DTTCREQ-0100
- Processors SHOULD process the
SVG as though the
<svg>element occurs directly in the content of the containing<svg-container>element. - DTTCREQ-0110
- Processors SHOULD separate the contents of the
<uicontrol>elements in some manner to represent the menu cascade. - DTTCREQ-0120
- Processors SHOULD preserve the
line breaks and spaces that are present in the content of a
<screen>element.