Exclusions; How Content Rules Translate To Markup Data - Adobe 65030365 - FrameMaker - PC Developer's Manual

9
H o w c o n t e n t r u l e s t r a n s l a t e t o m a r k u p d a t a
even though the footnote may be a valid inclusion in the table because table footnotes are
allowed only in titles and cells.

Exclusions

To add an exclusion to an element definition, insert an Exclusion element anywhere after
the general rule (or optional validity specification) and before the format rules. Then type
the tag of the element you want to exclude.
For example, you might use an exclusion to prevent end users from creating nested
Procedure elements:
Element (Container): Procedure
General rule: Step+
Exclusions: Procedure
The most common uses of exclusions are to prevent nesting and to counter an inclusion
for a particular context.
If you want more than one exclusion, for each additional exclusion, insert an Exclusion
element and type the tag, or put multiple element names in the same element, separated
by commas.

How content rules translate to markup data

In FrameMaker, the general rule and the inclusions and exclusions use a syntax that is
based on SGML model groups and declared content. (The occurrence indicators,
connectors, and parentheses are the same in both environments.) On import or export
between an EDD and a DTD, the content information about child elements is preserved.
Note that you do not need to put parentheses around the entire general rule in FrameMaker.
When you convert an EDD to a DTD, FrameMaker also translates content symbols in
general rules:
•
The FrameMaker content symbol <TEXT> translates to a content token of #PCDATA.
(#PCDATA can be combined with element tags, as <TEXT> can be in FrameMaker.)
• The FrameMaker general rule <TEXTONLY> translates to declared content of RCDATA.
• The FrameMaker general rule <ANY> translates to the reserved name ANY in a markup
content model.
•
The FrameMaker general rule <EMPTY> translates to a declared content of EMPTY.
When you convert a DTD to an EDD, FrameMaker performs the translations in reverse. In
addition, a declared content of CDATA translates to <TEXTONLY> in FrameMaker.
For more detailed information on how content rules translate to XML or SGML, see
Chapter 16, "Translating Elements and Their Attributes." For information on how structured
tables translate to XML or SGML, see Chapter 18, "Translating Tables."
Structure Rules for Containers, Tables, and Footnotes 118