Thanks for sharing your ideas Markus - this is really appreciated and I encourage everyone else to do the same. This is what makes up a real community, getting different input, discussing ideas and finally implementing them :)
I would like to comment on some of these ideas in combination: > 1) Intermediate render format > 2) Security > - Validation > - Property filters I think this could be done with my descriptive rendering idea I briefly mentioned in my talk. I'm currently about to write a prototype but I'm still a little bit undecided what's the best way to tackle this. So I could imagine having some descriptor file for a resource type, this file lists the properties to be rendered, maybe their types (if they can't be derived) and validation rules. This could be used for creating html, json, xml etc. for viewing, but also html for editing and on a post the input could be validated. The current json rendering implementation for example is based on the ValueMap. One idea would be to extend the json get servlet to look for such a descriptor file for the given resource type and then use this for json rendering. If none is found, the whole map is rendered. The same with xml output etc. For html we need some new stuff The same for the post servlet, if it nows the resource type, it can look for the descriptor file and validate the input. This sounds easy to be done, though we would have to come up with a clever format. Regards Carsten -- Carsten Ziegeler [email protected]
