title: what does it mean to build LDAP V3 compliant application?
body: <p>I have a requirement to build build a few REST api that interface with an LDAP V3 compliant server such as open LDAP/ AD. My primary question is if a server is LDAP v3 compliant, does it have its attributes defined per a standard L[as opposed to something like samAccount in AD]? that way it is possible to build a single integration code that integrates with all LDAP V3 severs. so if I have to create/query a user on any LDAP V3 server, I use that same code using standard LDAP attributes and not use vendor specific attributes such as "samaaccount ", or "memberOf". Is this possible at all [just like if I were to write JPA compliant code I could use both hibernate, eclipselink as ORM providers]? or have I misinterpreted LDAP v3 compliance?</p>