There's a Durham specification on the way, it's just not fully baked yet. I'm no writer, and it's hard to organize a two (at least) dimensional architecture into one literary dimension in a way that makes sense. I hope to get a draft done by the end of the week and it will be posted to the AudioMan-dev Google Group. Go ahead and join up, it's quick.

The main thing I had to get organized in my head was Durham's role and how it played out. Durham should not be an object persistence layer though it could easily tie into one. The main focus of Durham I think should be to offer object to file metadata synchronization.

This kind of automatic synchronization makes metadata look like objects to end user apps, and those objects are always the most up to date because Durham handles the file I/O automagically at lower layers. That -- and the metadata objects and API -- could be Durham's small and targetted focus. Seems more managable when I look at it that way.

Another spec will have to be written for AudioMan2 ... but that's later. :)