The value may be specified as UTF-8 text or as base64 encoded data,
or a URI may be provided to the location of the attribute value.

A line may be continued by starting the next line with a single space
or tab, e.g.,

dn: cn=Barbara J Jensen,dc=exam
ple,dc=com

Lines beginning with a sharp sign ('#') are ignored.

Multiple attribute values are specified on separate lines, e.g.,

cn: Barbara J Jensen
cn: Babs Jensen

If an value contains a non-printing character, or begins
with a space or a colon ':', the <attrtype> is followed by a
double colon and the value is encoded in base 64 notation. e.g.,
the value " begins with a space" would be encoded like this:

cn:: IGJlZ2lucyB3aXRoIGEgc3BhY2U=

If the attribute value is located in a file, the <attrtype> is
followed by a ':<' and a file: URI. e.g., the value contained
in the file /tmp/value would be listed like this:

where a value of 1 for deleteoldrdn means to delete the values
forming the old rdn from the entry, and a value of 0 means to
leave the values as non-distinguished attributes in the entry.
The newsuperior line is optional and, if present, specifies the
new superior to move the entry to.

For a changetype of delete, no additional information
is needed in the record.

Note that attribute values may be presented using base64 or in
files as described for entry records. Lines in change records
may be continued in the manner described for entry records as
well.

CHANGE RECORD EXAMPLE

The following sample LDIF file contains a change record
of each type of change.

INCLUDE STATEMENT

The LDIF parser has been extended to support an
include
statement for referencing other LDIF files. The
include
statement must be separated from other records by a blank line.
The referenced file is specified using a file: URI and all of its
contents are incorporated as if they were part of the original
LDIF file. As above, other URI schemes may be supported. For example: