Planet KMR
December 16th, 2007This blog has been replaced by “Planet KMR“, a feed aggregator containing the personal blogs of most of the KMR group’s members.
This blog has been replaced by “Planet KMR“, a feed aggregator containing the personal blogs of most of the KMR group’s members.
We just released our concept browser Conzilla in version 2.1 together with our collaboration server Collaborilla 1.0. Both applications are open source and have been licensed under the GPL.
The biggest changes from the last version (2.0) are:
Conzilla 2.1 requires a Java Runtime Environment in version 1.4.2 or newer.
Our paper “Collaborative Construction of Artifacts” got accepted at the 4th Conference on Professional Knowledge Management “Experiences and Visions”. We are going to present it at the Workshop for Collaborative Knowledge Management (CoKM2007).
Reference
Ebner, H., Palmér, M., Naeve, A., (2007), Collaborative Construction of Artifacts, Proceedings of the 4th Conference on Professional Knowledge Management, Workshop Collaborative Knowledge Management (CoKM2007), Potsdam, Germany, 28-30 March 2007.
Conzilla2 has been available as an applet for some time. Unfortunately it has been quite big because of its dependent libraries. I have now managed to reduce it from 11MB to 4MB.
Read the rest of this entry »
Eventually the SHAME web is restructured as a wiki. Additionally:
Finally Conzilla2.0 is released, named Lime after the new Lime-ish background color.
See the download page for more information.
After wrestling with JLDAP I finished (and tested) a first implementation of straight-forward access to the LDAP directory.
After wrestling with slapd (the OpenLDAP daemon) for a while I finally created a custom schema with an own ObjectClass and attribute definitions. I will shortly describe the possible fields and how they are supposed to work together.
After digging deeper into the topic LDAP I discovered that it was not really designed to keep several versions of a single node. To make this possible anyway I decided about a special structure.
LDAP is the most reasonable storage technology for the resolver and referrer service. Standarized ObjectClasses, small overhead and fast read access to entries. Updates will not occur in a dimension that would make a fast RDBMS necessary, so we do not care much about the writing speed of LDAP.