Currently the entire tool is predicated on a language having one canonical way to implement a schema. However, many frameworks exist which beg to differ. In JS alone, you may define an object as a plain function, a Backbone model, a Hotcake model, or something else. It may be difficult to integrate JS generated code into frameworks (without shim functions that translate one to the next), so a strategy should be laid-down that allows for language and framework to be specified to the tool.
Currently the entire tool is predicated on a language having one canonical way to implement a schema. However, many frameworks exist which beg to differ. In JS alone, you may define an object as a plain function, a Backbone model, a Hotcake model, or something else. It may be difficult to integrate JS generated code into frameworks (without shim functions that translate one to the next), so a strategy should be laid-down that allows for language and framework to be specified to the tool.