Home
HCL Domino Designer Basic User Guide and Reference
Basic product usage information and programming language reference information.
Programming Overview and User Interface
This section contains general guidelines and examples that show where to use Java, LotusScript, and the formula language.
XML for Domino
The following topics cover some general guidelines for using XML in Domino applications and list all the elements, attributes, and entities in the Domino Document Type Definition (DTD):
The Domino DTD
The Domino Document Type Definition (DTD) describes the structure of DXL, the Domino version of Extensible Markup Language (XML). The DTD contains the definitions of the XML tags that you can use to validate your XML documents while converting external XML data into Domino databases or to understand any XML documents produced while exporting internal Domino databases into XML.
subform (Domino DTD)
Represents a subform as a named design element. A subform is a shared resource that saves several form elements as a single object. For instance, you can create a subform that contains fields that display a company logo or copyright information and can insert the subform into several different forms that require this standard information.

subform (Domino DTD)

Represents a subform as a named design element. A subform is a shared resource that saves several form elements as a single object. For instance, you can create a subform that contains fields that display a company logo or copyright information and can insert the subform into several different forms that require this standard information.

Containment Hierarchy

Contained by: %design.elements;

Contains: %named.design.note.prolog;, <globals>, <code>, <actionbar>, <body>, %note.epilog;

Syntax

<!ELEMENT subform ( %named.design.note.prolog;, globals?, code*, actionbar?, body, %note.epilog; )>

Content

%named.design.note.prolog;, globals?, code*, actionbar?, body, %note.epilog;

Contains any one of the contents of %named.design.note.prolog; entity, an optional <globals> element, any number of <code> elements, an optional <actionbar> element followed by a <body> element, and any one of the contents of the %note.epilog; entity.

Attributes

<!ATTLIST subform


Attribute
%named.design.note.attrs;