Also something that might be considered for the JSON spec is this IETF draft spec "JSON Home" [1]. More generally, we should strongly consider support for URI templates [2], a proposed standard from IETF. This would allow for more flexible URIs within the Category's location attribute and allow for sub-resources of resource e.g. /compute/123-123-123/console Andy [1] http://tools.ietf.org/html/draft-nottingham-json-home-00 [2] http://tools.ietf.org/html/rfc6570 Andy Edmonds Senior Researcher Institute of Information Technology Zurich University of Applied Sciences http://andy.edmonds.be, @dizz On 16/05/2012 16:48, "Edmonds Andrew (edmo)" <edmo@zhaw.ch> wrote:
First, Great work!
Here are some editorial comments: - Please ensure line breaks at col 80 - The pdf build is broken. There is a missing dependency of "! LaTeX Error: File `json_rendering.out.pyg' not found." Please fix with a README with directions on installing the dependency. - In all tables, 'name resources' doesn't make sense. Possibly should be 'named resources'? If so I can make the edits or it's at your pleasure :-) - 'Necessity' in all tables. This is some what out of step with existing specs. Can it be aligned along 'Mutability' and 'Multiplicity' as in the existing OCCI specification series? - I've made and committed some minor changes. Review at your leisure.
HTH, Andy
Andy Edmonds Senior Researcher Institute of Information Technology Zurich University of Applied Sciences http://andy.edmonds.be, @dizz