ITP recognizes the text __INC(filename) within a DID Document and tries to replace this text with the contents of the file filename.
The text __INC(filename) can be written anywhere on a single line (even within comments) but cannot contain layout (spaces or line breaks) or word processor instructions (bold, italics or any other instructions) between the initial '_' and the closing ')'. The filename cannot contain letters with special accents (such as ö, é or ñ).
The include phase for subdocument takes place during DID creation, before the actual translation of the DID document. ITP generates an error document if subdocuments could not be found during the include phase. This error document contains all successfully included subdocuments and error messages for the subdocuments that ITP could not find.
When developing DIDs in the, ITP/MDK Repository, the subdocument file should be located in the Includes folder that is located in the DIDs folder.
When developing DIDs with the ITP/SDK MP, the filename should be either a fully qualified path to the file or a filename relative to a user-defined set of directories. This set of directories is determined by the include path setting.
ITP allows multiple levels of subdocuments.
The following restrictions apply to the subdocument support:
How and where the subdocument support searches for subdocuments depends on the way you specify the subdocument in the master document:
Specification |
Examples |
Effect |
Absolute |
D:\PATH\FILE.EXT \\SERVER\SHARE\PATH\FILE.EXT |
The filename is included. ITP ignores the include path setting. |
Relative |
PATH\FILE.EXT ..\PATH\FILE.EXT |
ITP searches the file, relative to every directory in the include path setting. |
|
D:PATH\FILE.EXT \PATH\FILE.EXT |
ITP does not work with a current drive or current directory. Therefore these filenames make no sense and are illegal for ITP subdocuments. They will cause an error. |
The subdocument support will always continue if it failed to include one or more subdocuments.