History of LDAPContactsPackage
Version 9 | Current version | |
---|---|---|
Eating my own dog food re System Development Life Cycle - SDLC and Package Maintainer Teams - wolff_borg Feasibility StudyThere have been requests for an LDAP compatible Contacts address book, which was started by lsces. I've provided an overview of LDAPCompatibility here.Analysis and Specifications v1.0 - due 17 July 2005Requirements for v1.0 are:
Analysis and Specifications v1.1 - TBA
ResourcesThis is an interesting interview that talks about LDAP vs XML, and the use of XML for CMS systems
Design, Documentation and Quality AssuranceFrom initial talks, data will flow in a sequence as shown below:XMLData will be store in LibertyContent data field in XML format{CODE()}<?xml version="1.0"?><contact><cn>Stephan Borg</cn><givenname>Stephan</givenname><sn>Borg</sn><mobile>1234 567 890</mobile><uid>wolff_borg</uid><o>Bitweaver</o><mail>me@home.com</mail><mail>me@home.com</mail><calfburl>http://bitweaver.org/fb/wolff_borg.ifb</calfburl></contact>{CODE}LDIF - LDAP Data Interchange FormatData coming from an LDAP server would look something like this:{CODE()}dn: cn=Stephan Borg,ou=people,o=bitweavercn: Stephan Borg givenName: Stephan sn: Borg mobile: 1234 567 890 uid: wolff_borg o: Bitweaver mail: me@home.com mail: me@home2.com calFBURL: http://bitweaver.org/fb/wolff_borg.ifb objectClass: top objectClass: inetOrgPerson objectClass: person objectClass: organizationalPerson objectClass: calEntry{CODE} LibertContentOnce imported into the class, the data would be stored in an array. I have tried to keep the format inline with the array format used by the LDAP PHP commands.{CODE()}array("cn" => "Stephan Borg", "givenName" => "Stephan", "sn" => "Borg", "mobile" => "1234 567 890", "uid" => "wolff_borg", "o" => "Bitweaver", "mail" => array( "me@home.com", "me@home2.com" ), "calFBURL" => "http://bitweaver.org/fb/wolff_borg.ifb", );{CODE} DevelopmentTODOSystems ImplementationTODOSystems MaintenanceTODO | ResourcesThis is an interesting interview that talks about LDAP vs XML, and the use of XML for CMS systemsThese talk about using XML with LDAP
DefinitionsNone as yetFeasibility StudyI have the requirement for an LDAP compatible Contacts address book. I've provided an overview of LDAPCompatibility here.Analysis and Specifications v1.0The initial design will be based upon LibertyForms - SDLC and will act as an add-on to provide the following.Requirements for v1.0 are:
Design, Documentation and Quality AssuranceTODOData ModelNot a very good diagram, but a start in understanding how this all fits together:{CODE()} UI Form -> LibertyContent (data/type array) -> LDAP server (LDIF - optional component){CODE}LDIF - LDAP Data Interchange FormatData coming from an LDAP server would look something like this:{CODE()}dn: cn=Stephan Borg,ou=people,o=bitweavercn: Stephan Borg givenName: Stephan sn: Borg mobile: 1234 567 890 uid: wolff_borg o: Bitweaver mail: me@home.com mail: me@home2.com calFBURL: http://bitweaver.org/fb/wolff_borg.ifb objectClass: top objectClass: inetOrgPerson objectClass: person objectClass: organizationalPerson objectClass: calEntry{CODE} LibertContentOnce imported into the class, the data would be stored in an array. I have tried to keep the format inline with the array format used by the LDAP PHP commands.{CODE()}array("cn" => "Stephan Borg", "givenName" => "Stephan", "sn" => "Borg", "mobile" => "1234 567 890", "uid" => "wolff_borg", "o" => "Bitweaver", "mail" => array( "me@home.com", "me@home2.com" ), "calFBURL" => "http://bitweaver.org/fb/wolff_borg.ifb", );{CODE} DevelopmentTODOSystems ImplementationTODOSystems MaintenancePackage Maintainer TeamSee Package Maintainer Teams for details and requirements of each of the roles.
|