XML FOR DOMINO


database element
Example

Defines the structure of a Domino database.

For more details on database settings, see Database Properties box - Advanced tab.

Containment Hierarchy

Contains: <databaseinfo>, <acl>, <fulltextsettings>, <launchsettings>, %note.types;

Syntax

<!ELEMENT database ( databaseinfo?, acl?, fulltextsettings?, launchsettings?, (%note.types;)* )>

Content

databaseinfo?, acl?, fulltextsettings?, launchsettings?, (%note.types;)*)


Attributes

<!ATTLIST database

%root.attrs;
path%string;#IMPLIED
title%tstring;#IMPLIED
categoriesCDATA#IMPLIED
templatename%string;#IMPLIED
fromtemplate%string;#IMPLIED
type(%database.types;)"standard"
allowstoredforms%boolean;"true"
allowbackgroundagents%boolean;"true"
imageloadsdeferred%boolean;"false"
usejavascriptinpages%boolean;"true"
requiressl%boolean;"false"
allowdesignlocking%boolean;"false"
allowexternalconnections%boolean;"false"
showinopendialog%boolean;"true"
advancedtemplate%boolean;"false"
markmodifiedunread%boolean;"true"
multidbindexed%boolean;"false"
multilingual%boolean;"false"
defaultlanguage%string;#IMPLIED
defaultregion%string;#IMPLIED
defaultsortorder%string;#IMPLIED
maintainunread%boolean;"true"
optimizetablebitmaps%boolean;"false"
overwritefreespace%boolean;"true"
savelastaccessed%boolean;"false"
logtransactions%boolean;"true"
allowsoftdeletion%boolean;"false"
allowspecialhierarchy%boolean;"true"
allowheadlinemonitors%boolean;"true"
increasemaxfields%boolean;"false"
maxupdatedbyentries%integer;#IMPLIED
maxrevisionentries%integer;#IMPLIED
softdeletionsexpirein%integer;#IMPLIED
nourlopen%boolean;"false"
unicodestandardsorting%boolean;"false"
allowdocumentlocking%boolean;"false"
copyprofiledocswithdesign%boolean;"false"
singlecopytemplate%boolean;"false"
uselz1%boolean;"false"
>

advancedtemplate


allowbackgroundagents
allowdesignlocking
allowdocumentlocking
allowexternalconnections
allowheadlinemonitors
allowsoftdeletion
allowspecialhierarchy
allowstoredforms
categories
copyprofiledocswithdesign
defaultlanguage
defaultregion
defaultsortorder
fromtemplate
imageloadsdeferred
increasemaxfields
logtransactions
maintainunread
markmodifiedunread
maxrevisionentries
maxupdatedbyentries
multidbindexed
multilingual
nourlopen
optimizetablebitmaps
overwritefreespace
path
requiressl
savelastaccessed
showinopendialog
singlecopytemplate
softdeletionsexpirein
templatename
title
type
unicodestandardsorting
usejavascriptinpages
uselz1
Defined entities for <database> element

The %database.types; entity defines the types of databases that can exist on a Domino server.

Syntax:

<!ENTITY % database.types "standard | library | addressbook | lightaddressbook | multidbsearch | portfolio | imapproxy | subscriptions | mailbox | personaljournal | mailfile ">

addressbook


imapproxy
library
lightaddressbook
mailbox
mailfile
multidbsearch
personaljournal
portfolio
standard
subscriptions
The %design.elements; entity maps to the various design elements in Lotus Domino Designer. This entity is used in the %note.types; entity.

Syntax:

<!ENTITY % design.elements "form | subform | page | frameset | view | folder | sharedfield | sharedactions | imageresource | appletresource | agent | agentdata | scriptlibrary | databasescript | helpusingdocument | helpaboutdocument | dataconnection ">

The %note.types; entity defines the basic types of notes or root elements in a Domino database. A %note.classes; entity differs from a %note.types; entity in that a note's class is determined by a value stored in the note's header; its 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.types "note | document | profiledocument | %design.elements; ">

Example
See Also