• is namespace a hashmaps of data structures or functions to resolve URIs?
• whiteboard - a memory database for sharing serialized objects between threads
• is a resource a superclass or a wrapper for a serialized obj on the whiteboard (like an in-memory file)?
• is a resource both a directory and a file?
• how to structure a tree of resources - or maybe we don't - it is just flat?
• fand services are config data objects mounted into whiteboard, then spawn threads via some callback
• fand specifies the URI mapping functions? or maybe done on startup via service specific configuration?

We've nailed down the following semi-final decisions:

1. Everything in the namespace implements the Resource mixin
2. fand and ORM objects implement the Resource mixin directly (they aren't boxed inside a Resource)
3. Resources always know their server absolute URI which determines identity
4. fand is just tree of serialized services - so we serialize whole tree together
5. however when we make "copy" of a service for mem database, we don't serialize children - maybe pass Func into writeObj options
6. sys::MemResource is the key super class for Service