LDAPschema.md

 TODO: figure out how to really integrate GO with LDAP via the LDAPauth plugin.
 
-According to
-https://www.group-office.com/wiki/IMAP_or_LDAP_authentication
-the mappings from GO fields to LDAP attributes are as follows:
+According to https://www.group-office.com/wiki/IMAP_or_LDAP_authentication the mappings from GO fields to LDAP attributes are as follows:
 
-`
-example:
+`example:
 	'username'	=> 'uid',
 	'password'	=> 'userpassword',
 	'first_name'	=> 'givenname',
@@ -37,7 +34,7 @@ example:
 
 The interesting attributes are the go-prefixed (gocurrency, gomaxrowslist, ...) which do not exist in standard schemas.
 The following questions follow:
-Does OpenLDAP/Keycloak/WSO2 enforce/validate LDAP Schemes when creating/updating entries via SCIM/KC-REST-API?
-In case it is optional? Should we enforce validity?
-Is there a standard GO-Schema file we can use?
-Should we develop our own and contribute it to GO?
\ No newline at end of file
+* Does OpenLDAP/Keycloak/WSO2 enforce/validate LDAP Schemes when creating/updating entries via SCIM/KC-REST-API?
+* In case it is optional? Should we enforce validity?
+* Is there a standard GO-Schema file we can use?
+* Should we develop our own and contribute it to GO?
\ No newline at end of file