- several files don't have version identifiers; a simple $Id in the
   comment would help in finding packaging bugs. (Also recommended for
   the documentation files)
 - Most makefiles and stylesheets miss a copyright header. 

Documentation:
 - There is no reference to the gnucomo website in the manifest, design,
   README.

Web Interface: 
 - A page with notification (independent of object) (with sort capabilities
   and grouping per urgency).  (PR 7)
 - With an object one should be able to indicate what OS is being used
 - Webpages should look more 'sexy'
 - Draw graphs of DYNAMIC properties.
 - Use XML/XSLT technology for the web interface.
 - Create valid XHTML.
 - Edit the range of DYNAMIC properties for each parameter.

  Whish (future):

 - Linking database users to objects (only certain objects can be shown to certain users)
   (PR 3)

GCM_INPUT:
 - Make a proper master daemon for the Gnucomo server. This daemon handles
   authorization of clients, scheduling and dispatching.
 - The input filename for gcm_input can be a command argument. (PR 9)
 - When gcm_input can not make a connection to the database, its input
   message will be lost. In such a case, gcm_input should store the
   message in a spool directory for a retry later on. (PR 10)
 - Indicate to gcm_input what type of data is delivered (PR 11)
 - Update statistics in the object table when a new parameter is entered
 - Update statistics in the object table when a new notification is entered


GCM_DAEMON:
 - Build IP-database on the basis of whois
 - Create mechanism for starting and ending the daemon.
 - Performance check on the gnucomo-database
 - Detect traces of log entries and use these traces to create notifications.
 - Trend analysis of DYNAMIC properties.