Hypermedia controls, long control names, meta information and embedded schemas takes up bandwith - how can we reduce the size of a Mason document?
Use a combination of CURIEs, the "prefer" header and linked schemas instead of embedded - or simply ZIP the whole payload.
Mason does not include any user interface information - how can clients then create dynamic user interfaces?
1) Use the JSON schema information to generate UI (using for instance tools like XX and YY).
2) Include layout information as normal API data (using a custom way of describing the layout).
3) Include a reference to some sort of external user interface template (a’la XML stylesheets) (using a custom way of describing the layout).