The two fields are:
attributetype ( 1.3.6.1.4.1.8506.1.2.11
NAME ( 'birthDate' 'dob' )
EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{128} )
attributetype ( 1.3.6.1.4.1.8506.1.2.12
NAME 'anniversary'
EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{128} )
Zhang Weiwu wrote:
>Recently we decide to deploy a LDAP database and decided to use
>evolutionPerson schema because in our business requirement we must have
>birthday and annervisary attribute, and evolutionPerson already contain the
>two, so better not create one schema by ourselves.
>
>the problem is how our application should be written to format the date? I
>am a little bit surprised in evolutionPerson schema 'birthday' attribut is
>of syntax 'Directory String'. What format should our application write in
>this Directory String?
>
>Considering some user may in the future use other tools to access this LDAP
>server (not only though the web interface we designed, but might also use
>Evolution or Lotus Notes), we better make the birthday format as compatible
>as possible. E.g. I wish to take a look at an evolution LDIF export file to
>check the format (impossible now because I don't have evolution running).
>
>Any Hint?
>
>--
>Zhang Weiwu Real Softservice
>International business: http://www.realss.com
>International sales: 0086 10 84606011
>Inland business: http://www.realss.cn
>Inland sales call: 0086 592 2099987
> Sent from Pine: http://www.washington.edu/pine/
>
>---
>You are currently subscribed to [email protected] as: [EMAIL PROTECTED]
>To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as
>the SUBJECT of the message.
>
>
---
You are currently subscribed to [email protected] as: [EMAIL PROTECTED]
To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the
SUBJECT of the message.
