Table of Contents
Advertisement
9
S p e c i f y i n g v a l i d i t y a t t h e h i g h e s t l e v e l i n a f l o w
If you try to save an EDD as a DTD when there are empty general rules, the resulting DTD
will have syntax errors. You need to import the EDD into a template first so that
FrameMaker can insert default general rules for you.
Keep in mind that for an EDD to be valid you need to insert a GeneralRule element in
the definition for every container, table, table part, footnote, or Rubi group—even when you
are not filling in the general rule.
Specifying validity at the highest level in a flow
Every structured flow in a document needs one highest-level element. This element is a
container and holds all other elements in the flow. You need to define at least one highest-
level element for each type of structured flow that can appear in documents.
To specify validity at the highest level in a flow, insert a ValidHighestLevel element
right before or after the element's general rule. For example:
Element (Container): Chapter
General rule: Paragraph+, Section, Section+
Valid as highest-level element.
When defining a highest-level element, you may want to give it a name that identifies the
type of document or flow. For example, in a chapter document the element might be called
Chapter.
Provide a highest-level element for book files as well as for flows in document files. For
example:
Element (Container): Book
General rule: Front, Chapter+, Index?
Valid as highest-level element.
Adding inclusions and exclusions
XML: The specification for XML does not support inclusions and exclusions. If an
EDD uses inclusions and exclusions, when you save the associated FrameMaker file
to XML the software ignores them. The result could be a document that is valid in
FrameMaker, but invalid in XML. When converting an EDD to a DTD, the resulting
XML DTD could contain errors. You should only use inclusions and exclusions in an
EDD that is part of an SGML structure application.
An inclusion is an element that can occur anywhere inside the defined element or its
descendants. Inclusions are often used for elements that might be necessary throughout a
hierarchy, such as cross-references or terms with special formatting. An exclusion is an
element that cannot occur anywhere in the defined element or its descendants.
You can define inclusions and exclusions as part of the content rules for containers, tables,
table parts, footnotes, and Rubi groups. Defining inclusions and exclusions in a few high-
Structure Rules for Containers, Tables, and Footnotes
116
Advertisement
Table of Contents
