Zetta Browser should render objects

[landlessness]

In the text-to-speech example below, I had to change my API in order to have the Zetta browser work.

The Zetta browser ought to render the object without disrupting API design.

Here is the original API with domain specific terms like 'locale' that can be used by API clients:

{
  "example": "Hello, my name is Moira. I am an Irish-English voice.",
  "locale": "en_IE",
  "name": "Moira",
}

Here is the API modified to work with Zetta browser including a concat'ed text field, a duplicated name / value field and an example field that gets ignored:

{
  "example": "Hello, my name is Moira. I am an Irish-English voice.",
  "locale": "en_IE",
  "name": "Moira",
  "text": "Moira | en_IE",
  "value": "Moira"
}

this is related to: #23