[Opensync-commits] r5626 - plugins/ldap-sync

[<svn...@op...>]

Author: scriptor
Date: Sun Apr 26 22:23:33 2009
New Revision: 5626
URL: http://www.opensync.org/changeset/5626

Log:
Added a file about issues or bugs.

Added:
   plugins/ldap-sync/BUGS

Added: plugins/ldap-sync/BUGS
==============================================================================
--- /dev/null	00:00:00 1970	(empty, because file is newly added)
+++ plugins/ldap-sync/BUGS	Sun Apr 26 22:23:33 2009	(r5626)
@@ -0,0 +1,42 @@
+These bugs are known to me:
+
+A. Implementation: 
+
+I. The format mapping is not 100 % correct.
+
+This concerns the ldap-format plugin.  It means, that the transformation
+from any xmlformat-... format to an LDAP specific format and vice versa
+is either incomplete or wrong.  The ldap-format plugin does not fully
+comply with the requirements, yet, as laid out by 
+
+/usr/local/share/libopensync1/schemas/xmlformat-*.xsd.
+
+
+
+B. Design:
+
+I. Storage scheme on the LDAP server:
+
+I am not really happy with the way the data is stored on the LDAP server.
+Only the object type "contact" maps to LDAP schemata that are already known
+and used outside of the opensync project: 
+
+	evolutionperson.schema
+	inetorgperson.schema
+
+All the other three object types are mapped in a way that robs
+the LDAP attributes of their original meaning.  Just to get
+a typical name-value pair stored.
+
+And even with the "contact" object type there is currently almost
+no support for the situation that a particular XML element occurs
+more than just once.  The *.xsd files allow for such multiple 
+occurrences.
+
+Maybe I should create opensync specific LDAP schemata? Don't know.
+I would have preferred using schemata that are already existing and
+used by other people...
+
+
+
+