Actually the only thing we
don't have consensus on is whether or not to follow the leaders (Google, Microsoft, IBM) in adopting Atom, and I've already given up on the idea of using it across the board anyway (for better or worse).
It's now 3am where I am and I've been on and off the phone all night with Andy getting ourselves in sync (we are, after all, doing the lion's share of the work). We've come to the conclusion that a simple key-value format originally proposed by ElasticHosts is feasible if supported by HTTP (for individual resources) and/or Atom (for collections of resources) for the meta-model. This is basically illustrated
in the wiki and is a significant simplification/improvement on what I had previously proposed - at least all the extra discussion has been useful.
As it's key-value (links, categories, etc. are delegated to the underlying protocol(s)) we have a further optimisation of being able to use HTML forms directly - so a client need not even understand the OCCI representation(s) if it knows how to submit a form. It really doesn't get any easier than that and we get the ability to submit e.g. OVF/OVA files for free - I'm guessing (hoping) the ElasticHosts guys will be happy when they get back from their long weekend as it was their feedback that primarily drove the revision.