If you want finer control, you can still leave them as inclusions
on FORM, but then make them exclusions on any elements in %body.content
(or any descendants of any elements in %body.content) where you don't
want them. For example, you could exclude them from TABLE.
Note that exclusions take precedence over inclusions. So once you've
excluded them, an inclusion nested within has no effect. For example,
once you've excluded them from TABLE, that would mean you could no
longer have them in a FORM within a TABLE.
The other option is not to include them on FORM, but to try to place
them in a more complex content model within FORM, but I'm sure Dave
has thought of this, and for whatever document analysis related reason
(I don't pretend to know much about the HTML 3.0 document needs analysis),
he has opted not to do this.
paul
Paul Grosso
VP Research Chief Technical Officer
ArborText, Inc. SGML Open
Email: [email protected]
or [email protected]