Hi, I've spent some hours implementing the rendering of resources attributes as defined in JSON spec and, finally, I think it can _not_ be done that way because its ambiguous. Let me give an example: let the following json document: { "attributes": { "com": { "example": { "default": { "type": "string" } } } } } Parsing this document, one can not say if this defines: - an attribute "com.example" with default value '{ "type": "string" }' - an attribute "com.example.default" with type "string" Given the interest of the community in JSON rendering and their implementations, I think we should quickly solve this issue and agree on a right syntax. Cheers, -- Jean Parpaillon Open Source Consultant Phone: +33 6 30 10 92 86 im: jean.parpaillon@gmail.com skype: jean.parpaillon linkedin: http://www.linkedin.com/in/jeanparpaillon/en