Re: importing multi line fields

["Douglas E. Wegscheid" <wegscd@whirlpool.com>]

At 08:46 AM 1/8/99 +0000, Chris Ridd wrote:
>The $ separator used in the Postal Address LDAP string format has 
>nothing to do with carriage returns or line feeds. Postal Address is 
>not a "multiline field", it is a value which contains up to 6 strings, 
>which is an important distinction to make.
>
>If you put $ signs in a value of Directory String syntax (for example) 
>they will remain just that, $ signs. (This is a good thing!)
>
>If you wanted a particular string component of a postal address to 
>contain a CRLF, you would have to encode it over the wire as follows:
>
>1st line of 1st string\0d\0a2nd line of 1st string$2nd string$3rd string
>
>This is described in RFC 1778 and RFC 2252, which you should read.

historically, $ is used as a separator in postaladdress (and actually
stored in the directory). The clients had to know to do the encoding and
decoding. I also recall seeing some proposed schema with examples that used
this schema, the Howes & Smith LDAP book uses it, and RFC 1778 section 2.23
has the BNF for "Values of type PostalAddress" as:

<postal-address> ::= <t61string> | <t61string> '$' <postal-address>

Am I misinterpreting or misusing the RFC information?
-
Douglas E. Wegscheid
working for, but not expressing the position of, Whirlpool Corporation
wegscd@whirlpool.com
-
A wrong note played hesitatingly is a wrong note. A wrong note played with
conviction is interpretation.