Kategorie: Tim’s Weblog
-
Rules-based programming
Jon Udell: „Tools for Rules: Rules-based programming will either help us out or create a different kind of mess“ http://www.infoworld.com/article/03/05/16/20OPstrategic_1.html „Rules engine/debugger as system service?: I like to imagine new OS system services. Yesterday, it struck me that a rules engine, logger, and debugger would be an appropriate bundle of stuff to generalize as a…
-
Mambo Content Management Server
Open Source variant of a commercial CM system (PHP/MySQL): http://www.mamboserver.com/ Nice layout and other stuff: http://www.miro.com.au/
-
The Open Archives Initiative Protocol for Metadata Harvesting
Interesting? http://www.openarchives.org/OAI/openarchivesprotocol.html
-
Intuit QuickBase
Web-based information system, reminds me of Intrexx – beautiful interface! http://www.quickbase.com/
-
haystack – the universal information client
Incredible – an RDF based Java application with a very generic architecture, drag&drop, e-mail and IM integration, customizable, … Very very high and specific system requirements, unfortunately. http://haystack.lcs.mit.edu/ http://www.xulplanet.com/cgi-bin/ndeakin/homeN.cgi?min=1&dd=02062003
-
topically
Mozilla Gecko based Semantic Web RDF client: http://topicalla.mozdev.org/ http://www.xulplanet.com/ndeakin/arts/elorapre.html http://www.xulplanet.com/ndeakin/arts/actorsearch.html
-
Data Structures and RDF
„There are four general ways of storing information: 1. A list, in which one has a number of items, which may or not be related to one another. 2. A table, in which one has a number of items (records), each with a distinct set of properties or columns. 3. A tree, in which one…
-
Phrame
MVC (Model, View, Controller) / Model2-Framework for PHP – sounds good, but I couldn’t get it to work: http://phrame.sourceforge.net/ https://www.phparch.com/issuedata/2003/jun/sample.php
-
JavaBeans conventions
A ZDNet article describes the conventions JavaBeans classes must conform to: class->getProperty class->setProperty class->isBoolProperty class->addEventListener class->removeEventListener Makes sense. That’s similar to what I’m already doing in my PHP classes.