XML FOR DOMINO


note element
Example

Defines the structure of a note in a Domino database. A note is usually represented as a document element or as a defined design element, such as a form or view. Exporting or importing note elements in DXL is for advanced users. More data is interpreted when you access a note as a design element, such as a form or view, than when you access it as a note element.

Containment Hierarchy

Contained by: %note.types;

Contains: %note.prolog;, %note.epilog;

Syntax

<!ELEMENT note ( %note.prolog; , %note.epilog; )>

Content

%note.prolog; , %note.epilog;


Attributes

<!ATTLIST note

%note.attrs;
class(%note.classes;)#REQUIRED
default%boolean;#IMPLIED
private %boolean;#IMPLIED
>

class


default
private
Defined entity for <note> element

The %note.classes; entity lists the types of notes classes that compose a Notes database. The class of a note is determined by a value stored in its header. A %note.classes; entity differs from a %note.types; entity in that a note's type is determined first by its class and is then further specified by the presence or absence of a specific item within the note. For instance, agents and scripts both belong to the FILTER class; yet their note types differ based on the value of the item called $Flags, which they each contain.

Syntax:

<!ENTITY % note.classes "document | helpaboutdocument | form | view | icon | helpindex | helpusingdocument | filter | sharedfield | replicationformula ">

The %note.classes; entity defines the following:

document


filter
form
helpaboutdocument
helpindex
helpusingdocument
icon
replicationformula
sharedfield
view
*Each database contains only a single occurrence of these classes.

Example
See Also