improve JSON rendering+solution

The first major chunk of work (creating the object_renderer) is largely done.  

The biggest design needs:

1. what does the data look like?
2. how do we handle custom formatting?

We're putting ideas for the data in +examples below.

As for custom formatting, there are at least three options:

1. Client side
2. Server side 1: custom views
3. Server side 2: custom actions

For client side, I think we should have very strong default options so that folks can get all the data that they need for cases where the client will be able to do significant data manipulation.

That said, there will also be cases where it really should come out cleanly right from Wagn, and I would think that option #2 is the right way to go.  Views are for all different ways to see the same data.  Actions are for data events that trigger some internal or external state change.  There may be some such triggers that involve JSON, but I would think that any server-side arrangement of data should happen in the views.