I take a lot of notes. I jot them down anywhere that's handy, creating a plethoric field of URIs, dates, todos, recipies, chords, quotes, diarizations, ideas, WikiNames, birthdays, phone numbers, authors, email addresses, ISBN numbers, man pages, bash commands, Python code snippets, incomprehensible scribbles, phenomicizations, and shopping lists.
Sometimes there are patterns between these things. They mainly get lost. It's all just content management, and there are thousands heaped on thousands of approaches to dealing with it. There's the Web, for one.
But I feel that I should be able to do better than what's out there at the moment, and so for months I've been working on approaches to dealing with such information; from input to processing to exposition. Ironically, of course, whilst I've been doing it I've actually not used any more complex a note taking program than a date-stamping echo, or a basic run-of-the-mill text editor. But the aim is to provide something which is as usable as possible.
It's a complex area which has baffled me at times, and delighted me at others, and I think I ought to start sharing some of the fruits of what I've been doing.
The first two notes programs that I created were called b and n. Not particularly thrilling names, but there you go. First came b, which was a very simple notes structure with some date handling features and so forth, and next came n which was similar but based on RDF, and way too complicated. Note (heh) that both of there were in the proto-stage of my research and deevlopment in this area, and so they're quite primitive.
The b documentation and b source code, and the n documentation and n source code are available on the Web for your perusal. They have such short names since they were designed to be used from the command line. At the moment, I favor an HTML forms interface, since it's something which will work on practically any computer, and can be used over a network.