LDAPschema.md

-Reference could be:
+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:
+
 `
 example:
 	'username'	=> 'uid',
@@ -31,3 +34,10 @@ example:
 	'enabled'	=> new \GO\Ldapauth\Mapping\FunctionMapping('custom_ldap_mapping_function_enabled'),
 	'exclude'	=> new \GO\Ldapauth\Mapping\FunctionMapping('custom_ldap_mapping_function_exclude'),
 `
+
+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